Basic Information:
Printer Model: Voron 2.4
MCU / Printerboard: Octopus v1.1 (STM32F446) and SB2040 (RP2040)
DataLink: Canbus (via CanBoot from Arksine)
Usefull files:
klippy.log (545 Bytes)
moonraker.log (42.0 KB)
My issue:
Hi,
I updated Raspbian 10 (buster) to Raspbian 11 (bullseye), for crowsnest compatibilities issues. But now Klipper is unable to connect to can MCUs. I mean, the RPI detect their UUID so they are online and reachable, but Moonraker can’t connect to Klipper.
pi@voron24:~ $ ifconfig
can0: flags=193<UP,RUNNING,NOARP> mtu 16 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1024
pi@voron24:~/canboot/scripts $ python3 flash_can.py -i can0 -q
Resetting all bootloader node IDs...
Checking for canboot nodes...
Detected UUID: 3f56a5b6c36c, Application: Klipper
Detected UUID: 2d70e57a001c, Application: Klipper
Query Complete
pi@voron24:~ $ apt-cache policy udev
udev:
Installed: 252.5-2~bpo11+1
Candidate: 252.5-2~bpo11+1
Version table:
*** 252.5-2~bpo11+1 100
100 /var/lib/dpkg/status
247.3-7+rpi1+deb11u2 500
500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
Everything is up-to-date in the mainsail update manager or in kiauh. machine.cfg is included in printer.cfg and containt both mcu parameters and adresses. But mainsail still can’t connect to klipper.
I even tryed to reflash canboot on the octopus board. No success.
In my “machine.cfg” file (included in printer.cfg) I registered my mcu UUIDs:
[mcu]
canbus_uuid: 3f56a5b6c36c
[mcu sb2040]
canbus_uuid: 2d70e57a001c
and in printer.cfg :
[include machine.cfg]
If I missed something, surely someone else will too. So, thank you for your help.
Mainsail config and errors :
)