Printer Model:Creality K1 Max
MCU / Printerboard: Creality K1 Max Mainboard (Stock) + BTT Eddy (USB/RP2040)
Host / SBC: Creality OS (Internal Embedded Linux)
klippy.log klippy.log (169.9 KB)
Describe your issue:
Hello,
I am using a Creality K1 Max with the Simple AF (Guilouz) script environment. I have integrated a BTT Eddy (USB version) but I am getting a persistent “MCU Protocol Error”.
The specific error message is: mcu 'eddy': Unknown command: i2c_write
My host Klipper is version v0.13.0-169-g02a55be6, while my eddy MCU is reported as version v0.13.0-575-g51ceda9ed. There is a clear command mismatch regarding the i2c_write function between the host and the Eddy firmware.
Since I am running the Simple AF setup on a K1 Max, what is the correct way to compile and flash the matching firmware for the BTT Eddy (RP2040) to resolve this protocol error? I’ve been stuck on this for a long time and really need some help.
I have attached my klippy.log for further details. Thank you!
Even though you have rooted your machine, it’s still running Creality’s version of Klipper and Linux, so the help we can give will be limited. The typical fix for this error is recompiling and flashing new firmware, but Creality’s modded systems may have a different process than legit Klipper.
Has it worked previously?
If not, go into the config file for the eddy and make sure the serial path is correct.
I believe its in the docs somewhere, but you do get that error if the eddy is not detected rather than the mcu not connected error you would expect - likely something to do with Creality modifications
Beyond that, your eddy mcu version is newer than the version of klipper software running, that may cause issues as theres been a few changes recently to the eddy mcu code.
you should be able to compile and flash the firmware from the k1, so that the eddy has a matching firmware version
