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

G29 endstop handling #6

Closed

Conversation

Blue-Marlin
Copy link
Owner

No description provided.

AnHardt added 3 commits March 10, 2016 18:03
Shift the definition of `clean_up_after_endstop_move()` close to
`setup_for_endstop_move()` to make them easier to compare.
Remove `enable_endstops(true);` from `setup_for_endstop_move()`.
Insert `enable_endstops(true/false)` in `run_z_probe()` directly before
or next to the relevant moves like it is done in `homeaxis()`.
Add `static int8_t h_endstops_set = 0;` to remember if
`enable_endstops()` was set by M120 or M121.
Pimp up `clean_up_after_endstop_move()` to recognize it the endstops
where set by M120, M121.
Use `clean_up_after_endstop_move()` when G28 is ready instead of the
same literal code.
Sync planner before the actual moves in `run_z_probe()` are done, to
guarantee the move is only in z direction.
@AnHardt AnHardt force-pushed the G29-endstop-handling branch from 148bb34 to d02d4d8 Compare March 10, 2016 17:08
Blue-Marlin added a commit that referenced this pull request May 2, 2016
Fix for #6 3593, MarlinFirmware#3648
this time excludung 'DEL' instead of accidently '~'.
@AnHardt AnHardt closed this Nov 1, 2017
@AnHardt AnHardt deleted the G29-endstop-handling branch November 1, 2017 23:43
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

Successfully merging this pull request may close these issues.

2 participants