Skip to content

[2.9] task: tighten AUTO read-ahead wait-clear to match MDI#3973

Draft
grandixximo wants to merge 1 commit intoLinuxCNC:2.9from
grandixximo:fix/3650-queue-not-empty-probe-2.9
Draft

[2.9] task: tighten AUTO read-ahead wait-clear to match MDI#3973
grandixximo wants to merge 1 commit intoLinuxCNC:2.9from
grandixximo:fix/3650-queue-not-empty-probe-2.9

Conversation

@grandixximo
Copy link
Copy Markdown

2.9 backport of #3971.

Cherry-pick of af6b5b7 with trivial conflict fixup for the pre-scoped-enum identifiers on 2.9 (EMC_TASK_EXEC_DONE, RCS_DONE).

Closes #3650, #662, #263.

Auto mode cleared the read-ahead wait on execState==DONE alone, so a
G38 issued just before an emcMotionUpdate snapshot could let the next
read fire while motion.traj.queue was still non-zero, tripping
NCE_QUEUE_IS_NOT_EMPTY_AFTER_PROBING. Add the queue==0 + io.status
==DONE conjuncts already used by mdi_execute_hook.

Closes LinuxCNC#3650, LinuxCNC#662, LinuxCNC#263.
@grandixximo
Copy link
Copy Markdown
Author

grandixximo commented Apr 28, 2026

Just here so users can do testing on 2.9 as well, for now

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.

1 participant