Move out of range at start of print
Hi!
Since yesterday all of a sudden whenever I want to start a print it says "move out of range". This always happens after the primeline. Even with prime line or prime blob deactivated it still happens (after bed mesh, before starting the print).
However when having a look at the exact position where the printer was when this happens and comparing it with where it think it was something is off.
When looking at the toolhead section, the coordinates in the smaller font in grey (exact position) said: x [5,000] y [5,000]
However in white (where the printer thinks it is) it said: x [500,000] y [500,000]
However it was too fast for me to screenshot it.
I also changed the max x and y positions to 510 which resulted in the error displaying 510,051 instead of 500,050
I also rebooted the pi and restarted the firmware several times but both didn't help
Please see attached picture for the error message.
I hope this is a common fault and someone could help me with it.
Greetings,
Vince
16 Replies
With max positions set to 520 the error looks like this
I also noticed that the amount that the requested move is over the maximum range corresponds to the maximum position of the bed. The additional amount is always 1/10000th. For 500mm max in x it was 0.050 and for 520mm it was 0.052.
I wonder what could cause this. Maybe skew_correction? But then I only activate skew correction on start_print after primeline so that it theoretically shouldn't interfere with any parts printed around the edges of the bed.
In the meantime I also asked this at the Klipper reddit, however nobody seemed to have the same problem. Could that be something related to RatOS? @miklschmidt Its really a bummer as I just can not print because of this tiny error. Any help would be much appreciated!
How close to the edge of the bed are you printing?
The small gray coordinates are actual coordinates (that is, including gcode_offsets and transforms, such as skew, bed_mesh, z_thermal_adjust etc). The white/big ones are commanded position. It throws an error because it's commanded to move to a spot that is outside your defined min/max after gcode offsets and transforms. It's probably because you have a skew profile enabled and trying to print at the absolute edge.
But then I only activate skew correction on start_print after primeline so that it theoretically shouldn't interfere with any parts printed around the edges of the bed.Which is when it errors (right after primeline). If your skew profile is set in RatOS, RatOS manages the loading of that profile for you. You should not do anything manually. And it is most definitely your skew profile causing the error.
Not even close, the primeline is printed at where it is specified from within the macro (about 10mm in x ). The parts I want to print (tried with several prints, all failed with the same error) are in the center or a bit off the center of the bed...
If white is the commanded position I don't understand why it wants to print that far outside if my print is in the middle of the bed.
Inow copied the START_AFTER_HEATING_EXTRUDER macro (that includes loading of skew) into printer.cfg und commented out the loading of the profile. The error still occured. Any other suggestions?
As i said, because of gcode transforms, in this case your SKEW_PROFILE.
Skew profile modifies the commanded coordinates
Commanded position * skew correction = bad position in your case.
I understand, however the skew would have to be extremely high for something like this to happen or am I wrong?
Don't do this. Just comment out the profile you set in the RatOS variables. And get rid of the manual profile loading you had as well.
no it wouldn't, it's 0.052mm
Your slicer is asking the printer to move to 520,520
That turns into 520,520.052
Alright, will do that now and come back here to tell how it went. Thanks for your help so far!
That's the point, why would the slicer want to print this far out? The parts are placed in the middle of the bed.
I don't know, look at your slicer settings and custom gcode see if you can find anything.
Nothing in RatOS makes it go to X_MAX, Y_MAX, and everything after the prime_line is your slicer.
So figure out what you did in your slicer profile
The RatOS variables are set within the printer.cfg right?
yes in the macro's section
Thank you, will have a look at all this.
It is working now. I found the problem. I tinkered with the timelapse settings last week and accidentally set the time-lapse park position to right back. In combination with skew this led to the error when the first picture was to be taken.
It's all fixed now. Thanks a lot for your help!
sounds like you don't have the origin set correctly in your slicer
It might be that the offsets of the gantry are a bit off in the slicer
not to move it to 500 when you are printing in the middle of the bed\