Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M91 in combination with restoring the state after the PRIME causes the XY to run in relative mode #89

Open
8Complex opened this issue Nov 9, 2022 · 1 comment

Comments

@8Complex
Copy link

8Complex commented Nov 9, 2022

I just managed to replicate the out-of-range motion -- I think what happened was that I did a manual move to max Z and accidentally went out-of-range while hitting the buttons. Once moved back up to the middle somewhere and starting the print, it seemed to start the print moved back in the Y and also hit the maximum Y position while beginning the print. Move out of range: 280.216 370.703 0.704 [1142.580]

I at least know how to avoid it now, but I'm guessing that last M91 in combination with restoring the state after the PRIME causes the XY to run in relative mode.

https://discord.com/channels/582187371529764864/843098069200666634/1039966075447672932

@miklschmidt
Copy link
Member

I've added an option in 2.0 to force G90 in START_PRINT.

[gcode_macro RatOS]
variable_force_absolute_position: True

It currently defaults to false. Once you make it to v2.0 try setting it to true and let me know if that fixes the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants