Probe tripped during non-probe move deadlock

More
10 months 3 weeks ago #339853 by abs32

 without my M64/M65-flipflop solution, 

 
Please publish your solution in full, including function declarations such as loadrt + everything, everything, everything. So that I can repeat it.

Please Log in or Create an account to join the conversation.

More
10 months 3 weeks ago #339861 by andypugh

It kinda improved, but the „probe triggered“ fault is still happening.
I was not able to finish even shorter milling programs (<5 mins).
The updates in 2.9.7 fix (hopefully) a bug where the "probe triggered during non-probe move" error was raised when the machine was actually probing (due to probe contact bounce). 

If you are seeing the message when _not_ actually probing (and you refer to a 5 minute milling cycle, with no mention of probing) then that is a different issue. 
 

Please Log in or Create an account to join the conversation.

More
10 months 3 weeks ago #339862 by tommylight

The updates in 2.9.7 fix (hopefully) a bug where the "probe triggered during non-probe move" error was raised when the machine was actually probing (due to probe contact bounce). 
Am i understanding this correctly:
A software solution was implemented in LinuxCNC for a hardware problem/issue ?
It does seem like it, or what am i missing?

Please Log in or Create an account to join the conversation.

More
10 months 3 weeks ago - 10 months 3 weeks ago #339865 by abs32
Perhaps due to the language barrier, we are misunderstanding each other.
1. There was a bug in version 2.8.4, which was fixed in 2.9.7.
2. Instead of fixing the bug that was interfering with the operation, they created a new one for which there is no solution.

However! First, I used a steel probe (before electrical contact) as a probe. Then I bought a Chinese Probe sensor (a so-called center finder). It did not suit me for a number of reasons:
1. Unacceptably high operating force (“out of the box” 450 grams, with my processing “with a file” (and a hammer) about 220 grams.
2. speed of operation
In version 2.8.4, I got 50,000-80,000 continuous sequential measurements at a rate of 5,000-6,500 per hour. But in version 2.9.7, the usual error for 2.9.7 appeared

And the other day I made my own version of such a sensor. The actuation force is 15 grams. The operating speed is higher (to such an extent that during G0 movements, the vibration sensor is triggered). But in version 2.8.4, I haven't exceeded 10,000 continuous measurements yet. In version 2.9.7, I got up to 12,000 measurements per hour, and now (tests are being conducted right now) more than 13,000 measurements without errors.

Conclusions: it is quite possible that version 2.9.7 works adequately with high-quality sensors.
Last edit: 10 months 3 weeks ago by abs32.

Please Log in or Create an account to join the conversation.

More
10 months 3 weeks ago #339867 by abs32
I rejoiced too soon. After 17,000 measurements 2.9.7, the error forum.linuxcnc.org/38-general-linuxcnc-q...bing?start=10#338958

Please Log in or Create an account to join the conversation.

More
10 months 3 weeks ago #339872 by andypugh

Am i understanding this correctly:
A software solution was implemented in LinuxCNC for a hardware problem/issue ?
It does seem like it, or what am i missing?

Not really. The problem was that LinuxCNC was setting the status to "not probing" before the end of the deceleration stage of a probe move. In cases where the probe triggers more than once (as many will) this led to a "non probe move" error during a probe move. 
Discussion here:
github.com/LinuxCNC/linuxcnc/pull/3534
In response to this bug report:
github.com/LinuxCNC/linuxcnc/issues/2926

 
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

Time to create page: 0.476 seconds
Powered by Kunena Forum