search

Arksine / katapult

Configurable bootloader for Klipper
GNU General Public License v3.0
439 stars 81 forks source link

Klipper can't connect to mcu via canbus after Raspbian 11 (bullseye) update. #80

Open Flob74 opened 1 year ago

Flob74 commented 1 year ago

Hi,

I updated Raspbian 10 (buster) to Raspbian 11 (bullseye), for crowsnest compatibilities issues. But now Klipper is unable to connect to can mcu. I'am using a RPi 3B, an octopus v1.1 (STM32F446) and a SB2040 (RP2040). Each MCU is connected via canbus.

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

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. moonraker.log klippy.log.json.txt (I add ".txt" for uploading) machine.cfg.txt (which is imported in printer.cfg) printer.cfg.txt

If I missed something, surely someone else will too. So, thank you for your help.

Mainsail config and errors : image

Flob74 commented 1 year ago

Ok. I delete everything. I reflashed the Raspberry PI with MainsailOS on Raspbian 11 (bullseye). I manually reinstall every plugins I had. I reflashed my MCUs canboots. And everything works again. So I can't tell where the error came from.

Sorry for the inconvenience.

Surion79 commented 12 months ago

you could close your own issue ;)