I perhaps have a little different perspective since we use probe moves with plasma systems where the "probe" is the torch tip and is either ohmic sensing or a switch mechanically activated when the torch is pressed against the metal.

2.7 does not ignore all spurious trips, because it will abort if probe is tripped during a jog or homing. I am using a patch I made which adds two INI settings to disable each of those behaviors, although we pretty much only ever disable probe aborting during homing for our setups.

I do think it should be "abort" instead of e-stop on spurious trips.

I like the idea of a HAL pin to disable the behavior because I think that might make it easier to do more complex disabling of probe aborts - such as ignoring probe trips while homing, or restoring the 2.7 behavior where spurious probe trips are ignored except while homing or jogging.

Moses

On 12/05/2017 03:28 PM, Sebastian Kuzminsky wrote:
<snip>
Les Newell's use case (where the "probe" is a tool length sensor permanently mounted to the table) shows the problem with my "what's in the spindle"-centric proposal.

I like part of Christian's proposal, where the user can configure HAL to enable/disable the "E-stop on unexpected probe trip" behavior.

I'm also sympathetic to Jon Elson's opinion that a spurious probe trip is essentially a misconfigured/glitchy machine, and it's the user's job to fix it somehow (possibly using some HAL logic to control the signal that Christian proposed).

So I propose this:

* Define a "probe trip" to be a positive edge on the motion.probe-input pin.

* A probe trip during G38 (ie, when motion.motion-type == 5) is handled just like now.

* A probe trip at any other time causes E-stop.

* A user with a glitchy probe can restore 2.7's behavior ("ignore probe trips when not probing") by setting up HAL logic like this:

     motion.probe-input = probe-input-pin AND (motion.motion-type == 5)


In brief, this is a proposal to change the behavior from 2.7's "ignore spurious trips" to a new "E-stop on spurious trips", and a suggestion of a simple user-level configuration work-around to restore the old behavior by masking the probe input.  Other HAL circuitry is of course possible too, depending on what the user wants.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to