Jump to content
  • 0

canbus error after firmware update


DC67

Question

Hello folks
I'm getting even more gray hair because I'm trying to get Manta M8P v2 + SB2209/2040) + Cartographer to work together via Canbus. Manta Board runs in Canmode and is always found. Sb2209 is also found after flashing the catapult/clipper. Now comes what I don't understand. I connected Cartographer to Canbus via SB0000 board. But can't find a UUID. When I then use the Cartographer Firmware Flasher I see the UUID and can also flash the latest firmware. After I did that I saw all 3 UUIDs exactly once in the terminal. I had to stop and continued adjusting the config later. Here I kept getting the error that it couldn't find the MCU scanner.At some point I simply displayed can0 in the terminal. Here I suddenly only saw the Manta Board. What I found out today must be related to flashing the cartographer because I was able to repeat these errors. I flashed the Sb2209(2040) catapult/clipper again today and lo and behold there were 2 UUIDs in the terminal Manta and SB2209 Cartographer again.. Here I started the firmware flasher from Cartographer which found the UUID. I ran flash again, which “supposedly” worked. Then restarted and only the Manta Board was visible in the terminal again. Now I'm at a loss as to what's going wrong here. I placed the 120ohm jumper on the SB board. Sorry if some of my spelling sounds strange because that's exactly what I use Google Translate for.

I was wrong. What you see in the terminal is the Cartographer and the Mantaboard. The SB 2209 doesn't appear here, which confuses me.

Manta M8P v2 board
Canbus -- uuid: ec6b84790bf5

SB2209
Canbus -- uuid: 0784a2ab8f2b

Cartographer
Canbus -- uuid: 1107687e1772
These are the UUID that I wrote down at the beginning when flashing the boards.

 

 

cartographer.jpg

mant+sb2209.jpg

manta board.jpg

Edited by DC67
user error
Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

I'm having similar issues trying to get my Mellow Super 8 pro, EBB36, Cartographer up and running.

I think one of the problems is the 120r termination resistor.

If you are in Can Bridge mode and feed the Cartographer from the SB2209, in theory that should have the termination resistor on the mainboard and on the Cartographer and there should be no termination resistor on the SB2009. Some say that because of the short distance it doesn't matter. 

I found that if I have the mainboard as a simple USB board and if use a UTOC I get a UUID for the SHT36 and the Cartographer, but if I try using the mainboard in Can Bridge mode I get no UUIDs.  In Can Bridge mode there are three 120r termination resistors. If the UTOC is used there are only 2.

No matter which way I went if I used the SHT36 I never had success. The EBB36 worked straight away but only if I didn't use the Can Bridge mode.

If you have your mainboard in Can Bridge mode, try removing the termination resistor from the SB2009 - I'm not saying that it will work but...

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

  • 0

I have the motherboard running in USB to Can mode. I still found one error. I had an incorrect UUID for the cartographer in the config. I had already soldered the 120 ohm resistor on the Cartographer and pulled it onto the SB2209 so that the Mantaboard <-> Cartographer are at the end. Currently I see Manta and Sb2209 when I type " ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0 ". Shouldn't I see all the "participants" from Can0 here? Or is this only possible if Klipper has been stopped or all errors that I currently have due to the config change have been eliminated? I didn't want to completely recreate my config, I just wanted to change it. I followed the Esoterical guide. Some people also write here that you should create a file with the Can values. But if I understood and did it correctly, this is done at the beginning of the Esoterical even if you don't create a file here.

Link to comment
Share on other sites

  • 0
26 minutes ago, DC67 said:

I have the motherboard running in USB to Can mode. I still found one error. I had an incorrect UUID for the cartographer in the config. I had already soldered the 120 ohm resistor on the Cartographer and pulled it onto the SB2209 so that the Mantaboard <-> Cartographer are at the end. Currently I see Manta and Sb2209 when I type " ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0 ". Shouldn't I see all the "participants" from Can0 here? Or is this only possible if Klipper has been stopped or all errors that I currently have due to the config change have been eliminated? I didn't want to completely recreate my config, I just wanted to change it. I followed the Esoterical guide. Some people also write here that you should create a file with the Can values. But if I understood and did it correctly, this is done at the beginning of the Esoterical even if you don't create a file here.

You should see all participants.

I have just put my M8Pv2 / EBB36 on to my test bench and flashed the firmware as a USB to Can bus bridge, connected the only working Cartographer that I know have and with 3 jumpers I see all three participants.

image.png.f3f3de823508d89efe202e592945e503.png

But If I the Cartographer on my v2.4 (Mellow Super 8 pro / UTOC / EBB36 I get no candidates when I run the can query.

That's the first time that it's worked without having a UTOC connected.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...