Great guide. I just went through this on my own and it took a few hours of reading and cobbling together information from different sources. In 20 min you basically covered what I needed. Great job!
Thank you guys for posting this, ive been struggling with installing can boot from a guide made over a year ago, many of the guides and links fork, or hyperlink you to something else and then the guide becomes useless because it no longer has the same commands as what the updated gguides use. Wish this was the first video I watched on installing can bus, would have saved me many hours
Great Job making this simple. I did the steps awhile ago for an sb2240 and then just had to remind myself what was needed for an SB2209. Using these steps but substituting my commands from the BTT guide was super easy. The simplest of things is to know when your hooking up a USB or using the can cable which helps a lot.
@11:00 The blue Heatsink - so I've been told - goes onto the smaller TMC2209 Chip next to the Stepper Driver Connector - *_NOT_* the larger STM32 Chip 😁
hi, is the footage up for this? thanks for the amazing guide btw, just to let you know on your github the copy paste commands start with a capital letter, they should be all small, e.g. Sudo doesnt work but sudo does
Had to remove the cover of the Hotend and add a big heatsink too. 58c chamber temp was too much for the MCU. Now at 87c MCU temp if the reading is accurate. And did multiple longer prints. Seems to work now. I had to redirect the hot air from the chamber heater to go up to avoid raising the MCU hotend temp too.
The can board do no longer appers with ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0 from the moment klipper flashed over katapult. Should it be like this?
@@TheVoronModder Guy on discord said he has it working. I had bad experience with can and only interested it now because i want a toolchanger. U2C at time was not working. Going to try fly-sht boards
Hello! Help me please, I've been struggling with installing canbus for 2 days now. I have orange pi 5(Distributor ID: Debian Description: Armbian 24.2.1), bought an ebb36 board and a U2C module. At the very beginning, when creating the can0 file, it gave the error /etc/network/interfaces.d/can0 directory does not exist. I manually created the interfaces.d folder and the can0 file. With all further manipulations, I encountered the same problem: I did not see the device via can0. when I scanned the ip addr networks, I discovered that there was no can0 network. Maybe someone has encountered this problem. Thanks in advance!
The indentation of "/etc/network/interfaces.d/can0" seems wrong! The "iface can0 can static" line should not be indented, as it's the start of the interface definition. I'm surprised this has any effect for you at all...
You know what you should do.... Do a can update. So I am just updating klipper to .12 from .11 it broke many things, obviously. No one has a decent canbus update video, yet people struggle with it.
It would better your explanation that you reduce the resolution of the screen you are sharing. My eyes cannot distinguish what there appears in the screen. Letter and numbers are too small.
So a couple issues with this "tutorial". Your co creator had everything already installed and assumed everyone understood beforehand what all the options are and does. This is WRONG! He should have started from a fresh, clean build. Also, what about if my results aren't the expected results?? (which they were) How to diagnose and troubleshoot would have been good as well. I found some of this video helpful, but the things I listed above warrant it to be done again PROPERLY! You aren't helping the community with "staged" tutorials like this! We need real world results and problem solving.
the last command on the github should have a ~ instead of a - (-f ~/klipper/out/ instead of -f -/klipper/out/) near the end, also the file name is written as /flash_cany.py it should be /flash_can.py
I was running into issues at the very last step of flashing an SBB2209, this is what fixed the last command for me cd ~/katapult/scripts python3 flashtool.py -i can0 -f ~/klipper/out/klipper.bin -u 35a4416f355c
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Great guide. I just went through this on my own and it took a few hours of reading and cobbling together information from different sources. In 20 min you basically covered what I needed. Great job!
Thank you guys for posting this, ive been struggling with installing can boot from a guide made over a year ago, many of the guides and links fork, or hyperlink you to something else and then the guide becomes useless because it no longer has the same commands as what the updated gguides use. Wish this was the first video I watched on installing can bus, would have saved me many hours
Great Job making this simple. I did the steps awhile ago for an sb2240 and then just had to remind myself what was needed for an SB2209. Using these steps but substituting my commands from the BTT guide was super easy. The simplest of things is to know when your hooking up a USB or using the can cable which helps a lot.
Awesome, I’m gonna do can on my current build, and go back and add to my first. This should be very helpful.
There it is!!
Not all heroes wear capes.....
currently building my second v2.4 350 with canbus, then going to add it to my first v2.4 350
@11:00 The blue Heatsink - so I've been told - goes onto the smaller TMC2209 Chip next to the Stepper Driver Connector - *_NOT_* the larger STM32 Chip 😁
This is true. I have 2x on there fyi.
I do have footage that needs to be uploaded this week on printer.cfg configurations with the Can Network specifically the tool head.
hi, is the footage up for this? thanks for the amazing guide btw, just to let you know on your github the copy paste commands start with a capital letter, they should be all small, e.g. Sudo doesnt work but sudo does
@@Shamsher1 no I’ve been traveling for work. Hope to be back at it in 1 week. Thanks for the tip I’ll have to adjust the GitHub.
why have you installed the heatsink on the mcu and not the stepper driver where it is meant for?
I have 2 heat sinks on there just not in the video I didn’t notice that when uploading the video.
Had to remove the cover of the Hotend and add a big heatsink too. 58c chamber temp was too much for the MCU. Now at 87c MCU temp if the reading is accurate. And did multiple longer prints. Seems to work now.
I had to redirect the hot air from the chamber heater to go up to avoid raising the MCU hotend temp too.
The can board do no longer appers with ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0 from the moment klipper flashed over katapult. Should it be like this?
Can’t find the second pard what was mentioned at the end… Can someone post the link please? cheers
edit: Never mind, already done…
i have btt octopus, what cable do i need if i am skipping u2c board? Want to do can bridge mode
You know I’ve never ran canbus that way. I know it’s possible though. Might have to do a video on it.
@@TheVoronModder Guy on discord said he has it working. I had bad experience with can and only interested it now because i want a toolchanger. U2C at time was not working. Going to try fly-sht boards
Hello! Help me please, I've been struggling with installing canbus for 2 days now. I have orange pi 5(Distributor ID: Debian
Description: Armbian 24.2.1), bought an ebb36 board and a U2C module. At the very beginning, when creating the can0 file, it gave the error /etc/network/interfaces.d/can0 directory does not exist. I manually created the interfaces.d folder and the can0 file. With all further manipulations, I encountered the same problem: I did not see the device via can0. when I scanned the ip addr networks, I discovered that there was no can0 network. Maybe someone has encountered this problem. Thanks in advance!
Ahh I’ve never used a orange pi I’ve always purchased rasperry pi’s
My inability to crimp well makes me sad when I see canbus
superstars
The indentation of "/etc/network/interfaces.d/can0" seems wrong!
The "iface can0 can static" line should not be indented, as it's the start of the interface definition. I'm surprised this has any effect for you at all...
You know what you should do.... Do a can update. So I am just updating klipper to .12 from .11 it broke many things, obviously. No one has a decent canbus update video, yet people struggle with it.
This is a great idea! Thank you for that I’ll be sure to mention your user name this coming week when I make the video.
Good thing to note if using a MCU with onboard CAN and a CB1, Rate of 500K is max. CB1 will not sustain 1M.
Interesting. I just ordered a m8p and cb1 so this will be a great learning experience. I’m so use to using the octopus MCU and standalone RPi.
@@TheVoronModder I like to use M8P or other similar when I can to free up space using CB1/CM4. Like Micron or Pandora's Box.
It would better your explanation that you reduce the resolution of the screen you are sharing.
My eyes cannot distinguish what there appears in the screen.
Letter and numbers are too small.
So a couple issues with this "tutorial". Your co creator had everything already installed and assumed everyone understood beforehand what all the options are and does. This is WRONG! He should have started from a fresh, clean build. Also, what about if my results aren't the expected results?? (which they were) How to diagnose and troubleshoot would have been good as well. I found some of this video helpful, but the things I listed above warrant it to be done again PROPERLY! You aren't helping the community with "staged" tutorials like this! We need real world results and problem solving.
It's better than your tutorial boomer...
the last command on the github should have a ~ instead of a - (-f ~/klipper/out/ instead of -f -/klipper/out/) near the end, also the file name is written as /flash_cany.py it should be /flash_can.py
I was running into issues at the very last step of flashing an SBB2209, this is what fixed the last command for me cd ~/katapult/scripts
python3 flashtool.py -i can0 -f ~/klipper/out/klipper.bin -u 35a4416f355c