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

HOMEAXIS zeroes position first, breaks with min_software_endstops #38

Closed
sparr opened this issue Dec 21, 2011 · 6 comments
Closed

HOMEAXIS zeroes position first, breaks with min_software_endstops #38

sparr opened this issue Dec 21, 2011 · 6 comments

Comments

@sparr
Copy link

sparr commented Dec 21, 2011

If min_software_endstops is enabled then homing (such as with G28) will not work because the HOMEAXIS macro sets the current position to zero before moving. This means it will "hit" the software endstop immediately and just do the little dance and end up right back where it started.

@bkubicek
Copy link
Contributor

hi!
In which case is that a problem? If you only have software-min endstops, you cannot home to them, because homeing requires physical switches, and in configuration you can define if homeing should be done with min or max physical endstops.
What should be the way to do it in your opinion?

@sparr
Copy link
Author

sparr commented Dec 22, 2011

If both hardware and software endstops are enabled, I would expect G28 to go to the hardware endstop.
If just software endstops are enabled, I would expect G28 to go to the currently defined zero.

@nothinman
Copy link
Contributor

(closing old issue)

rosenhouse pushed a commit to rosenhouse/Marlin that referenced this issue Feb 16, 2015
thinkyhead referenced this issue in thinkyhead/Marlin Dec 3, 2016
@thinkyhead thinkyhead reopened this Jul 2, 2020
@github-actions
Copy link

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.

2 similar comments
@github-actions
Copy link

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.

@github-actions
Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants