Skip to content

docs: homing.dot: no HOME_DELAY before the final move - #4628

Merged
grandixximo merged 1 commit into
LinuxCNC:masterfrom
SyncTwin:synctwin/homing-dot-final-move
Oct 4, 2026
Merged

grandixximo merged 1 commit into
LinuxCNC:masterfrom
SyncTwin:synctwin/homing-dot-final-move

Conversation

@yurc

@yurc yurc commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

The developer-manual homing state diagram (docs/src/code/homing.dot, and the Spanish copy) shows HOME_FINAL_MOVE_START -> HOME_FINAL_MOVE_WAIT "after HOME_DELAY". The code has not done that since the 2022 state-machine rework: in src/emc/motion/homing.c the timer branch of HOME_FINAL_MOVE_START has no break, so the final move is planned as soon as the joint has stopped (for a negative HOME_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.

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.
@grandixximo
grandixximo merged commit 056f2fd into LinuxCNC:master Oct 4, 2026
17 checks passed
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