From The Bench: Episode 1 - Flashing a BTT Octopus Pro Primary MCU with CanBoot and Klipper
Вставка
- Опубліковано 15 жов 2024
- Thanks to Shelley at @bigtreetech5117 for inspiring me to start making the "From The Bench" video series. She approached me a short while ago asking me if I would be interested in making some content featuring some of their products, which they would send me for free.
For this first series, that product is the BTT EBB SB2240 CAN Bus Toolhead PCB. I walk you through the entire process to mod your printer for CAN Bus.
Links:
github.com/Eso...
github.com/big...
This is super helpful. Thanks for doing this. I'm upgrading an existing Trident. I have the Octopus connected to my 24V power supply and then have a USB connection from the Pi to the Octopus (I use the octopus to power the PI). I added the BootTo jumper. But I'm having trouble getting the Octopus into DFU mode. When I power-on, the Octopus lights up, but when I do lsusb, I don't see an STM device in any mode.
Have you made any progress? If not find me as OldGuyMeltsPlastic on Discord, or ask for help in the Voron Discord server's #can_bus_depot channel.
Just wondering , why did you flash canboot to the octo only to then over write it with the klipper firmware . You only have to flash canboot to the Octo if you ARE going to use Canbus bridge ? Otherwise you can just go straight to flashing it to the U2C ?
You are right, CanBoot/Katapult is optional, and even more so if you are using a CAN adaptor like a U2C. However, flashing it here gives me some flexibility for my testbench hardware, which I may want to reconfigure for bridge mode in another video.
This is not a correct statement. Kan boot is written to the first 32kb of memory, then the clipper is written with an offset. Very convenient to update the firmware
if i have an Octopus already running Klipper, and am using a U2C (so no bridge mode), do I need to reflash the Octopus? is canboot only used when using bridge mode?
There is no need to flash anything to the Octopus when you use a U2C. While you absolutely can flash CanBoot/Katapult to the Octopus in that configuration, there isn't a compelling reason to do so.
@@oldguymeltsplasticthanks for clarifying this
Okay,followed your directions to the T and the last instruction to flash klipper seems to have erased the /dev/serial directory from pi so that ls /dev/serial/by-id/ is no longer found. Damn, seemed to be going so well up until this point.
You are flashing Klipper to your primary MCU? Did you flash it in Bridge mode, or NOT in Bridge mode?
If you used Bridge mode settings, then yes, your primary MCU no longer will appear as a serial device in /dev/serial/by-id.
Instead it will appear with a CAN bus UUID when you issue this CAN bus query:
python3 ~/CanBoot/scripts/flash_can.py -i can0 -q
@@oldguymeltsplastic yup, must have done it in bridge mode, went back and looked at /klipper/menuconfig and sw I screwed up the last menuconfig with bridge vs non bridge. Okay so I have a UUID now, can I continue on with part 2 now because no way to get back to the serial directory?
@@brianguthrie9017 in Bridge mode, your primary MCU now also acts like a CAN adaptor/U2C, which makes the U2C from step 2 redundant.
If you want to use the U2C (I do on both of my printers), I would strongly recommend reflashing the primary MCU so that it doesn't run in Bridge mode.
@@oldguymeltsplastic I would love to do that but something updated and removed the/dev/serial directory so am unable to get the serial address that needs to be pasted in the next command. Seems to be a lot of chatter on this being a bug within the 60-serial.rules file. Will keep Hacking at it but seems like the bridge VS no bridge is far more important to get absolutely correct or risk corrupting your os.
@@brianguthrie9017 that's a different issue. Your board isn't showing up in /dev/serial because it now doesn't communicate over USB
I have a very simple question if anyone can answer.
Why is it that you are using an external USB to Canbus board to connect to SB2240 when your MCU (Octopus) already has an option for Canbus?
What is the benifit here? Why spend extra money here?
Four words: "Timer Too Close" errors.
@@oldguymeltsplastic Would you then suggest against using CanBoot from Octopus to EBB?
I was doing this for fun but this shit is more difficult to set up with a lot more issues.
I would just use a multi core cable instead.
@@S00rabh I started using CAN bus a year ago without a U2C, and it worked well for a few months without issues until one day, my first Timer Too Close error showed up. Three frustrating weeks of troubleshooting led me to try using a U2C, and the TTC errors disappeared immediately. I now have 3 printers with CAN bus all with U2Cs, and all run smoothly.
But I might be the outlier here, you should absolutely set it up how you want to.
@@oldguymeltsplastic
Thanks,
I just came to know that EBB36 can also be used with a USB cable connected directly to a pi.
It is just a 2nd MCU. Why not do that?
Canbus looks so overly complicated for something so little.
@@S00rabh if you have motion rated USB cable then go ahead and try it. I haven't myself, but with the correct wires, there's no reason I can think of why that wouldn't work. Still need to source 24V and GND from somewhere though
Been struggling with this for a month now, lol
Lots of helpful people on the Voron Discord server.
thank you..I got it connected after a 3rd reflash and a little help from a buddy. is run from a pie 4 to the U2C V2,1 to an EBB SB2209 with the Knomi display,
FYSETC 3D imput shaper on lineral rails on my now heavily modified Ender 3.
@@oldguymeltsplastic
Glad you got it working!