You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{% set safe_z = printer.gcode_move.gcode_position.z|float %}
which is assigning the current Z position to overwrite the configured safe_z if the machine is already in a homed state without any consideration for whether the current z position is safe or not. This causes the toolhead to potentially crash if the user attempts to home the machine again when it is already homed but is currently at a Z height below safe_z such as after a small print or a failed print.
I have opened a PR #262 to only do this if the current Z position is greater than the configured safe_z however I am unsure if this is the correct approach or not since I am unsure if this line is needed at all given that in every other place i could find references to safe_z it is only used if current Z is below it.
The text was updated successfully, but these errors were encountered:
Just ran into the same issue here. When XYZ have not been homed it will do a safe z move and continue homing. However, after it has been homed, and you move the tool head below the safe_z height, it will not prevent a collision. I believe this collision only happens then your dock is in the homing path of the toolhead. I could move my dock out of the homing path, but instead I change line 654 to what @jmeier5261 is suggesting. Tested below safe_z height, moves bed down to prevent collision. Tested above safe_z height, bed did not move. Works great.
In the latest changes to klicky macros (ac98aef#diff-1d362a82153582bae3cbefb9848fdaf09f1b0aa250e3998dc6ef1e65bf38f63fR653) There was code added here:
Klicky-Probe/Klipper_macros/klicky-macros.cfg
Line 654 in c3366bb
I have opened a PR #262 to only do this if the current Z position is greater than the configured safe_z however I am unsure if this is the correct approach or not since I am unsure if this line is needed at all given that in every other place i could find references to safe_z it is only used if current Z is below it.
The text was updated successfully, but these errors were encountered: