docs: homing.dot: no HOME_DELAY before the final move - #4628
Merged
grandixximo merged 1 commit intoOct 4, 2026
Merged
Conversation
Since the 2022 homing state-machine rework the HOME_FINAL_MOVE_START state plans the final move as soon as the joint has stopped (and, for a negative HOME_SEQUENCE, the other joints of the sequence are ready); there is no HOME_DELAY pause before it (src/emc/motion/homing.c, the timer branch of this state has no break). The diagram still showed 'after HOME_DELAY' on that edge. Describe the actual behavior; no code change. See LinuxCNC#4621.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The developer-manual homing state diagram (
docs/src/code/homing.dot, and the Spanish copy) showsHOME_FINAL_MOVE_START -> HOME_FINAL_MOVE_WAIT"after HOME_DELAY". The code has not done that since the 2022 state-machine rework: insrc/emc/motion/homing.cthe timer branch ofHOME_FINAL_MOVE_STARThas nobreak, so the final move is planned as soon as the joint has stopped (for a negativeHOME_SEQUENCE, once the other joints of the sequence are ready). This was measured in sim in #4621: 2 servo periods in state 20, not 0.1 s.This PR only changes the label of that edge to match the code. No code change. Both files render with
dot -Tsvg(graphviz 2.42.4, Debian trixie).Follow-up to the discussion in #4621.