Filament change error with the new Python 3.x update #214
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Linux Distribution
..
What happened
After installing dual klipper with the new Kiauh 3.x future, i just had errors regarding filament change (M600) on both my printers.
It would throw a "unknown command: "Y147.2" (or different number) at the point the M600 triggered, then it will park, and when i resume, it travle a tiny bit around the print, then park again, and when resume again, it will throw "Unknown command: #FILAMENTCHANGE" and continiue the print like normal.
Tried all kinda M600, pause and resume codes, but nothing worked, so re-installed Klipper with Python 2.7, and then the same Gcode would print like normal straight away.
What did you expect to happen
Resume print like normal
How to reproduce
M600/Filament change
Additional information
No response
KIAUH has no influence on how Klipper processes macros installed with Python2 or Python3.