Probe tripped during non-probe move deadlock
- djdelorie
- Away
- Junior Member
-
Less
More
- Posts: 28
- Thank you received: 4
30 Jul 2025 15:51 #332563
by djdelorie
Replied by djdelorie on topic Probe tripped during non-probe move deadlock
I had similar problems with my toolsetter, and initially used an AND gate - until the time I forgot to enable it (I used a manual signal, not motion.*) and crashed my toolsetter. Then I tried smoothing, which worked OK. It turns out the toolsetter is a good seismic monitor, and trips when I have issues with toolchanging 
However, my comment here is... have you considered using a dummy probe move to retract the probe?

However, my comment here is... have you considered using a dummy probe move to retract the probe?
Please Log in or Create an account to join the conversation.
- DauntlessA
- Offline
- Junior Member
-
Less
More
- Posts: 22
- Thank you received: 5
01 Aug 2025 02:56 #332616
by DauntlessA
Replied by DauntlessA on topic Probe tripped during non-probe move deadlock
Hi Andy,
I believe that the issue I'm describing is exactly the one here:
github.com/LinuxCNC/linuxcnc/issues/2926
The last comment from that issue was you asking about the motion.motion-type following motion.probe-input going high.
I've looked in the halscope and it does seem that motion.motion-type remains at a value of 5 (Probing) until deceleration is completed, at which point the motion-type goes directly to 0 (Idle). So the issue isn't that the motion type resets immediately when the probe input triggers.
I was probing using just the X axis/joint 0 when I tested this.
I'll try and find out a bit more if I can.
I believe that the issue I'm describing is exactly the one here:
github.com/LinuxCNC/linuxcnc/issues/2926
The last comment from that issue was you asking about the motion.motion-type following motion.probe-input going high.
I've looked in the halscope and it does seem that motion.motion-type remains at a value of 5 (Probing) until deceleration is completed, at which point the motion-type goes directly to 0 (Idle). So the issue isn't that the motion type resets immediately when the probe input triggers.
I was probing using just the X axis/joint 0 when I tested this.
I'll try and find out a bit more if I can.
Attachments:
Please Log in or Create an account to join the conversation.
Time to create page: 0.060 seconds