-
-
Notifications
You must be signed in to change notification settings - Fork 19.1k
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
[FR] Home XY (if needed) before nozzle park #16307
Comments
You didn't include a zip with your config files, but you need to enable |
While in principle it makes sense, it seems prudent that is should be optional, simply because endstops are not always the most positionally-accurate things, and at the same time leaving steppers powered on tends to heat them up more than keeping them moving, so both not-homing and not-staying-powered are often a preferred combination. |
Thanks for the responses. I added the required files
It's weird how i missed this feature, thanks. I also added the files
I personally like the last option, not-homing and not-staying-powered, but this would't work during a print job. So not homing XY if position is unknown still looks like the best option here, imho. |
This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Cfg files.zip
Description
I don't consider this a bug, but there's definitely an issue with the filament change command "M600" combined with NOZZLE_PARK_FEATURE and ADVANCED_PAUSE_FEATURE when the motor drivers have been disabled and the axis moved manually (Position unknown). This will cause sometimes X and Y to hit their limits and bump creating noises and possibly breaking something.
I think it would be wise to add a feature to either home X and Y before parking the nozzle always or home X and Y only in case the XY position is unknown (motors disabled).
Steps to reproduce
Feature Workflow
The text was updated successfully, but these errors were encountered: