Printer Model: K1 Max
MCU / Printerboard: Stock
Host / SBC: Mac Sonoma 14.5
klippy.log klippy.log (1.8 MB)
Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
Iam modding a K1 Max with the Linear Gantry and have replaced the motors, etc. I have connections and belts set. If I home XY through Klipper, all works as expected. But when I try to move the toolhead (either through Klipper, or using G1, or one the K1 Max panel) I receive the error
Thank you for your reply. I had some trouble downloading the log file through orca but switched to browser and was able to do it. It is attached now.
The most recent events were homing (correctly) and then trying to move the head with the resulting errors.
I have previously used M84 to stop the motors when I was moving the head to tune the sensorless homing values. But learned it discards the homing info so I am not using that command between homing and trying to move the head.
Creality and the K1 is using a modified Klipper version and the number of macros loaded in this config is beyond what anyone (at least I) will be willing to analyze to find any bug.
The best thing is to revert to Creality for support.
I’m sorry. I am confused. I have used the K1 Max as a platform for open source software. If this forum is for developers only, I apologize. Is there another for users of the software?
This forum is for users of the open source Klipper project, and does not provide support for Creality’s modified version. Please contact Creality support for questions about their software.
Unfortunately, Creality and Open Source are two things that do not really go well together. Creality is in constant violation of Klipper’s license and due to their heavy modifications of the Klipper code, Klipper’s behavior is massively changed.
For example, they have some hard-coded (at least last time I checked) start up routine with fixed temperatures. There is a thread here that discusses this behavior.
I think I understand and I appreciate your time. I’d like to echo back to make sure I got it.
The helper script I used (from Guilous) installs Fluidd, Moonraker, etc. But does not install a new (open source) version of Klipper and instead retains the Creality version and runs the other services on top so it’s more accessible. But it is still Creality version on the machine.
Correct. In fact, it is Creality themselves who are providing this “root” means and it is nothing more than pseudo freedom since you are still bound to “their” Klipper.
Thank you for helping me get it. If that point comes, are there supported MCU boards that I could use to replace the Creality board where the porting is already done? I’m a retired engineer so I cover basic changes.