Klipper: Always "move out of range" problem

Created on 2 Apr 2018  路  8Comments  路  Source: KevinOConnor/klipper

i use bed tile compensation, all settings are perfect but when it start to print, it print something and then the printer hangs. The terminal said "move out of range ". What is the range stands for?? The z-offset and stepper z endstop is same number.

Send: N74 G1 X143.333 Y128.999 E0.0085982
Recv: ok
Send: N75 G1 X55.635 Y128.959 E2.91685
111
Recv: !! Move out of range: 55.635 128.959 -0.136 [21.074]
Changing monitoring state from 'Printing' to 'Operational'
Send: M400
Send: M114
Recv: ok
Recv: ok
Recv: X:143.333 Y:128.999 Z:0.200 E:5.657
Send: M84
Send: M104 T0 S0
Send: M140 S0
Send: M106 S0

Most helpful comment

My guess this is happing if you have done BED_MESH_CALIBRATION ( my bed is not level at all).
somehow the calculation leads to a value of Z below zero.
Here is an example of a failure :
Move out of range: 165.313 85.200 -0.531
you can work around this by setting the following to negative value. I had set mine to almost minus one millimeter. Add the following to Z section e.g [stepper_z].
position_min: -0.99
my guess this can be done in the software ( taking the lowest value from the BED_MESH_CALIBRATION).

All 8 comments

when i restart the printer, and perform g28, the printer is normal, but after g28, i type g1 x20, it shows move out of range again, but g1 x30 is ok, what is the range stands for, how can i set the range, i have looked through the config file, there is no setting for range. Any bugs or script behind??

what did you set for position_endstop: ``position_max:?

For assistance with an issue, you must attach the klipper log file as described at:
https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md

I was succefully printing calibration cubes on my Delta printer and trying to adjust the arm_length parameter until i get the perfect 20x20 size, but after a few runs i started to have this problem too!

Here is a copy of the log, when the config started to fail, and with a rollback. In both cases the Z height move order is higher than one of the towers height! Resetting firmware and kippler does not solve this problem! I cannot print anymore xD

klippy.log

Here is the offending Gcode:

G28; Home
G1 X0 Y50 E10; FAILS HERE with Recv: !! Move out of range: 0.000 50.000 308.442 [10.000]

* EDIT *

Bug found, if the next Gcode line after G28 does not contain a Z height the move will fail!
This code works:

G28; Home
G1 X0 Y50 Z10 E10; Works!

@Nume1977 - that's by design. When you home a delta the nozzle is going to be at the top of the printer. You can't move the printer to Y50 at that Z height as attempting to make that move would cause carriages to crash into the top of the frame. One must move the nozzle to a lower Z height before moving the nozzle horizontally.

@KevinOConnor - you are correct, I had the DELTA_HOME_TO_SAFE_ZONE option enabled in Marlin and that is why it never failed and i never noticed the wrong startup GCODE!
But the bug described might be related to this situation

Closing this issue - post the log file if assistance is still needed.

My guess this is happing if you have done BED_MESH_CALIBRATION ( my bed is not level at all).
somehow the calculation leads to a value of Z below zero.
Here is an example of a failure :
Move out of range: 165.313 85.200 -0.531
you can work around this by setting the following to negative value. I had set mine to almost minus one millimeter. Add the following to Z section e.g [stepper_z].
position_min: -0.99
my guess this can be done in the software ( taking the lowest value from the BED_MESH_CALIBRATION).

Was this page helpful?
0 / 5 - 0 ratings

Related issues

aegelsky picture aegelsky  路  3Comments

smokez89 picture smokez89  路  4Comments

KevinOConnor picture KevinOConnor  路  6Comments

leungtech picture leungtech  路  4Comments

SergeyKrutyko picture SergeyKrutyko  路  6Comments