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:
Ive been trying to determine why my printer returns the move out of range error every second print. If I turn the printer off and on again, it will print as usual, but when it ends and I try to print it again without turning it off and restarting the firmware, it will purge and at the end of the purge it ill return an error for the X axis movement. Why it doesnt happen in the first run never and on the second always?
Ya, it never happens during print, its always at the exact same time. Wich is at the end of the purge line.
I update it all the time in hope this ends.
There, I try to download the klippy file just after I send the second print and It return the error at the end of the purge line.
When I hit the update manager, it says i have it all updated. Actually I have this problem going on for several months already and I have already update klipper with the update manager many times.
I am wondering if the problem isn’t in your print end macro.
I saw that you swap between relative and absolute coordinates. Did you check if you’re not running out of bounds during print end macro?
An easy way to test that is to eliminate all X/Y movement commands and leave just the Zed movement so you can remove the print.
I also thought it was strange that you wait until the Hotend reaches 180 degrees before allowing the print to finish. It’s a bit of a shot in the dark but I’d try to test without that as well. I had issues with print end before and this is just a hunch, but I think it’s worth a shot.
I will try and see if it has to do with the end macro. I didnt think it had anything to do because I have tried to do a turn off motors, bed homing, moving arround the axis and all sort of things before the second print and nothing seems to make a difference.
The 180°C is because it was supposed to do a cold pull of the filament to “clean” the nozzle at the end of each print. It shold be 170 but I did not change the minimun nozzle operation temperature, so it was getting to 170 and not doing the pull.
I imagine there is some corrupted state after each print so I’d start making the print end as simple as possible. If it’s this is the case, you would still encounter problems after doing what you did.
I had a problem before that if I printed in sequence the print start Homing would not home correctly and the nozzle would be drifted (instead of starting from end stops) causing the probe to be out of the bed and consequently causing a crash.
I never figured out why (and only during this circumstance) the drift would happen. I made so many changes that eventually the problem disappeared.
I removed everything from my end macro. It didnt change. I noted that the start macro doesnt do what its supposed to in the second print. But why would it do what it needs on the first and not on the second? On the second time its supposed to move to the front of the bed, and it moves to the side for heating the nozzle. than it does prime the purge line, but ends with the error after that.
This is going to be an issue with your start print macro.
its going to be a case going through it carefully line by line to understand what its doing and in what order and what state the printer is left in before the print gcode takes over.
From past experience its most likely been caused by a mismatch between absolute and relative positioning.
may be worth checking your gcode file aswell to see if your slicer is expecting the printer to be left in absolute or relative mode after the macro ends.
