EBB SB2209 (RP2040) can bus with manta and CB1 problems

[Jduke]

I have an octopus pro board running a BTT SB2209 can toolhead and while it was not easy to setup, with the help of the esoterical guide it works.

I have another printer that Id like to use the Manta M5P with CB1 board (instead of Rpi) and I bought the EBB SB2209(RP2040) can tool head for it. This is the one with bigger connectors so easier to crimp, it also has a USB connection rather than the TX/RX of the other SB2209.

I can't seem to get it to communicate at all and I think I have narrowed it down to a question of what communication port and type the Manta board uses for can bus.
the Manta board has PD0 and PD1 as the RX and TX ports, right next to that is a USB port that seems like it would be the perfect place to plug in the USB port for the Can Bus bridge that comes with the SB2209(RP2040)
I have tried Serial coms as its USB so that makes sense, I have tried Serial to canbus.

using the lsusb command I can see the rp2040, can get it into boot mode and flash it, so on some level I am communicating with it, but after that when I check its UUID it comes back in Klipper mode not katapult.

on another note, esoterical's guide shows the RP2040 as Flash chip W25Q080 with CLKDIV 2 while the manual from BTT has a revision showing GENERIC_03 with CLKDIV 4
I have tried both, and neither seem to help the communication issue.

I am thinking about updating to the Rpi CM module rather than the CB1 but I doubt that is the source of the problem.

any leads or ideas would be much appreciated, Thank you in advance.

Duke

 

[OkieVet]

You likely will have to reflash the firmware to the Manta as a minimum because in all likely hood that is where the problem is and not the RP2040 as it's popping up in klipper mode indicating it has Klipper already on it. The Manta board is the USB to Can bridge. As I understand it, the USB port on the RP2040 is only for flashing firmware, I don't think it's configureable to use in lieu of the Canbus cable because it's limited in capacity for both voltage and amperage. You can either flash Katapult, then flash Klipper via Can0, or you could flash Klipper via the USB port but then you would lose the ability to flash Klipper updates over Can0. In order to power the RP 2040 you either hook up the USB cable after placing the jumper over the USB 5v pins above the RST button or you remove the jumper and it receives power over the Canbus cable.

While it's a bit of a hassle, what I finally did was to completely wipe everything off of the Pi including the OS and built everything back up from ground zero. Yes, it sucked, but it worked. If you decide to wipe everything, consider saving any UUIDs that you have since those are tied to the individual hardware kind of like a MAC id. I ended up saving those in a text file for later use. FWIW, I went somewhere between 'here, hold my beer' and Tim Taylor from Home Improvement with the Pi...
completely unncesssary and extreme overkill hardware wise and also with the OS - RP5 with an m.2 nvme ssd to drive the printer and a lite version of Debian Trixie which uses a newer network manager than previous releases so there are some slight differences with network configuration for Can0. Use what works and is recommended or else you may face unforseen and avoidable problems. In retrospect my problems were virtually all self-inflicted through a combination frustration, poor documentation on some things, conflicting information, and eventually changing things that I didn't fully understand at the time but I've finally managed to get to where it's running and I'm ready to do print tests.

From the Esoterical troubleshooting guide:
Once a UUID has been “grabbed” by klipper-on-pi then it won’t show up to a query. This is normal.

Note: If your board is meant to be in Katapult mode, and you have a blinking LED on the toolhead indicating the board is in katapult mode (if the status LED is supported) then the Klipper service on the pi won’t be grabbing the UUID. It will only grab application: klipper UUID’s

check the firmware of your toolhead. If you never saw the toolhead Katapult or klipper as a UUID at all then double check the Katapult/klipper firmware for incorrect settings. This could be any setting as even a single incorrect setting on this firmware will either stop the toolhead from booting at all (in which case you won’t see it on the network) or it boots but is looking at the wrong CAN pins/has the wrong CAN speed (in which case you also won’t see it on the network).

Some other things to check. Power everthing down completely, printer and Pi. Then do a continuity check to make sure that CanH and CanL are wired correctly, that the jumpers for the terminating resistors are set, and finally that you removed the 5v jumper from the RP2040. Finally, consider re-flashing both the Manta and the RP2040 and be careful to check that everything is set according to Esoterical's guide. Also, pay attention to upper/lower case when setting GPIO pins - GPIO is not the same as gpio, and PC3 is not the same as pc3. W25Q080 with CLKDIV 2 vs GENERIC_03 with CLKDIV 4 - I don't think it matters which one you use, it may be a performance thing, I tried both as well but used CLKDIV 2 when I last flashed it. If you're still messing with it and not getting it working properly, then it's probably time to wipe out everything including the OS and start over.

I went round and round with a similar problem with that tool head and an Octopus Pro 1.0. Not sure exactly where it went sideways, because I had managed to get things running at one point and was able to get all of the CAN IDs for the Octopus, SB2209, and Cartographer, and even start tuning. In the end, I had messed something up but had no idea what exactly I did and ended up in a black hole. I eventually checking all the wiring and went through multiple successful reflashing of Katapult onto the BTT SB2209/RP2040 only to be unable to find it in Klipper. I finally broke down and completely deleted everything including Linux and started from scratch, following the Esoterica guide and it worked.