Printer Model: Creality CR-10 Smart Pro
MCU / Printerboard: 2 X Creality CR-FDM-v2.5.S1_100 (one is “mcu”, the other is “auxmcu”) + Raspberry Pi Pico as mcu “pico”
Host / SBC: x86_64 PC 64bit Debian GNU/Linux 11 (bullseye), kernel version Linux 5.10.0-28-amd64 klippy.log (1.6 MB)
Describe your issue:
Unable to connect to mcu: “mcu” after April 4, 2024 Klipper update.
Unsuccessful actions taken:
Klipper restarts.
Firmware restarts.
Host restarts.
Checked all physical connections.
Disconnected all MCU’s and host from power for 30 minutes.
Updated all 3 MCU’s to the latest Klipper firmware as of April 4, 2024 - error persisted.
Successful actions taken:
Using KIAUH, rolled back Klipper to 1 commit prior to April 4, 2024 returned printer to normal function.
Also, attempting to update Klipper today to the latest commits dated April 5, 2024 produced the same issue and rolling Klipper back now 2 commits resolved the issue as before.
I seem not to be able to update Klipper past commits dated April 3, 2024 without this issue reoccurring.
You’ve got an i2c error in there that I don’t know what caused it, but you’ve also got the manual_stepper error I corrected in another post.
See here and follow the directions to drop the file in your ~klipper/klippy/extras…
@Sineos & @EddyMI3D - Don’t know if you want to let other people make sure my fix works and then maybe make a sticky? Manual_stepper.py is broke after the 4/4/23 update to Klipper if anyone has a [manual_stepper] defined.
I updated my Klipper and confirmed it does cause Mainsail to get stuck in an “Initialization” loop because the webhook doesn’t return a value from the status call to manual_stepper because the function had an error.
I bet there is going to be a lot of people asking why they can’t connect after the update (I’ve seen two so far).
I tagged Kevin in the linked post to give him the heads up.
