[BUG] G30 - Single Z-Probe doesn't respect HOME_AFTER_DEACTIVATE #27206
Labels
Comments
|
Please test the |
|
@DerAndere1 opened up a PR that may fix this: Please give that PR a try and report your findings there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Did you test the latest
bugfix-2.1.xcode?No, but I will test it now!
Bug Description
The command "G30" - Single Z-Probe doesn't appear to respect the HOME_AFTER_DEACTIVATE setting.
I have NO_MOTION_BEFORE_HOMING and HOME_AFTER_DEACTIVATE set in my config file, they work fine normally, enforcing the homing before motion, but then I created some Macros (in Pronterface) using G30 and they just move, even after a deactivation, without a homing.
Bug Timeline
Noticed 24/06/2024
Expected behavior
Expected not to move with an error, or to run a G28 automatically
Actual behavior
It just moves, even if it means it tries to take the axis beyond the maximum limits of the printer (I have no max physical end stops), causing motors to stall and possible damage.
Steps to Reproduce
Deactivate the motors
Run a G30 command
Version of Marlin Firmware
2.1.2.4
Printer model
Prusa I3
Electronics
RAMPS 1.4
LCD/Controller
Panelolu2
Other add-ons
No response
Bed Leveling
ABL Bilinear mesh
Your Slicer
Slic3r
Host Software
Pronterface
Don't forget to include
Configuration.handConfiguration_adv.h.Additional information & file uploads
Configuration.zip
The text was updated successfully, but these errors were encountered: