Skip to content

motion: probe start errors name only the G38 code that gets them - #4879

Merged
andypugh merged 1 commit into
LinuxCNC:2.9from
grandixximo:probe-start-msg
Nov 22, 2026
Merged

andypugh merged 1 commit into
LinuxCNC:2.9from
grandixximo:probe-start-msg

Conversation

@grandixximo

Copy link
Copy Markdown
Contributor

When the probe is already in the target state at the start of a probe move, motion reports "Probe is already tripped when starting G38.2 or G38.3 move" or "Probe is already clear when starting G38.4 or G38.5 move". Only G38.2 and G38.4 get these errors. G38.3 and G38.5 skip the check, trip at once at the start point and set #5070 to 1.

The messages made users, me included, think the no-error variants abort too (#4874, #4868). This drops G38.3 and G38.5 from them.

Checked in a sim on master, which has the same check: G38.2 and G38.4 abort with the probe already in the target state; G38.3 and G38.5 end at the start point with #5070 = 1.

The error for a probe already in the target state said "G38.2 or G38.3" and "G38.4 or G38.5", but only G38.2 and G38.4 get it. G38.3 and G38.5 skip the check, trip at once at the start point and set #5070 to 1. The message made users think the no-error variants abort too.
@andypugh
andypugh merged commit 96fc287 into LinuxCNC:2.9 Nov 22, 2026
14 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