- Printer Model
- Voron 2.4
- Extruder Type
- Clockwork 2
- Cooling Type
- Stealthburner
Hello Experts
I am setting up a Voron 2.4 350 build and have the following electronics:
1. Raspberry Pi 4 with 8G mem
2. BTT Octopus v1.1
3. BTT SB2209
4. BTT U2C
I wanted to setup CAN on my printer to enable SB2209 to communicate with Pi through U2C using CAN. Following are the steps I performed:
1. Setup Mainsail OS on Pi, did a sudo apt update and sudo apt upgrade to pull in latest updates
2. Flashed Katapult and Klipper on Octopus (set communication to USB)
3. Reflashed firmware on U2C (since I read some of the U2C had bad firmware)
4. Setup pi for CAN communication by following guide on this url: https://canbus.esoterical.online/
4. Flashed Katapult on SB2209 in DFU mode and flashed Klipper using Canbus network
5. Ran the python script to search for Canbus devices and found the SB2209 mcu Canbus ID
6. Updated my printer.cfg (actually, I setup a seperate file EBBCan.cfg to setup SB2209 related configurations and included that file in the printer.cfg file).
When I try to bring up Klipper, it tries to communicate with SB2209 over can and fails. If I comment out the SB2209 configuration include line, Klipper comes up without issues. If I stop klipper and then run the python query to find the canbus devices, I get the UUID of SB2209.
Steps that I did to troubleshoot:
1. Reflashed and reprogrammed pi, U2C and SB2209.
2. Tried to setup Octopus in USB to CAN bridge mode, but the adapter I got for using the RJ11 port is kind of loose and I didn't want that to cause any issues, so reflahsed the Octopus back to use USB communication.
3. Tested CAN network is up and running by checking ip a and can see the CAN network.
4. If I restart the printer, and without bringing up klipper, I can query the CAN device and get the UUID
5. I read somewhere that the CAN umbilical wire that is sent along with SB2209 has the CAN L and CAN H wires interchanged (meaning the green may be CAN H and yellow CAN L). I am not sure if that's correct. Have any of you faced this situation before?
6. While setting up pi for CAN communication, as per the website I mentioned that I followed (), they use systemd-networkd and not the can file under /etc/network/interfaces.d. In fact, I don't see a folder under network called interfaces.d. Not sure if this matters or not
I have attached my printer.cfg, ebbcan.cfg and kipper.log file. Please let me know if you require additional logs or information to help troubleshoot why I am unable to bring up klipper when using can.
I am setting up a Voron 2.4 350 build and have the following electronics:
1. Raspberry Pi 4 with 8G mem
2. BTT Octopus v1.1
3. BTT SB2209
4. BTT U2C
I wanted to setup CAN on my printer to enable SB2209 to communicate with Pi through U2C using CAN. Following are the steps I performed:
1. Setup Mainsail OS on Pi, did a sudo apt update and sudo apt upgrade to pull in latest updates
2. Flashed Katapult and Klipper on Octopus (set communication to USB)
3. Reflashed firmware on U2C (since I read some of the U2C had bad firmware)
4. Setup pi for CAN communication by following guide on this url: https://canbus.esoterical.online/
4. Flashed Katapult on SB2209 in DFU mode and flashed Klipper using Canbus network
5. Ran the python script to search for Canbus devices and found the SB2209 mcu Canbus ID
6. Updated my printer.cfg (actually, I setup a seperate file EBBCan.cfg to setup SB2209 related configurations and included that file in the printer.cfg file).
When I try to bring up Klipper, it tries to communicate with SB2209 over can and fails. If I comment out the SB2209 configuration include line, Klipper comes up without issues. If I stop klipper and then run the python query to find the canbus devices, I get the UUID of SB2209.
Steps that I did to troubleshoot:
1. Reflashed and reprogrammed pi, U2C and SB2209.
2. Tried to setup Octopus in USB to CAN bridge mode, but the adapter I got for using the RJ11 port is kind of loose and I didn't want that to cause any issues, so reflahsed the Octopus back to use USB communication.
3. Tested CAN network is up and running by checking ip a and can see the CAN network.
4. If I restart the printer, and without bringing up klipper, I can query the CAN device and get the UUID
5. I read somewhere that the CAN umbilical wire that is sent along with SB2209 has the CAN L and CAN H wires interchanged (meaning the green may be CAN H and yellow CAN L). I am not sure if that's correct. Have any of you faced this situation before?
6. While setting up pi for CAN communication, as per the website I mentioned that I followed (), they use systemd-networkd and not the can file under /etc/network/interfaces.d. In fact, I don't see a folder under network called interfaces.d. Not sure if this matters or not
I have attached my printer.cfg, ebbcan.cfg and kipper.log file. Please let me know if you require additional logs or information to help troubleshoot why I am unable to bring up klipper when using can.
