Well, how do I modify it? Like I say, pressing Probe Z momentarily starts an ngc.
My best guess is the probe input needs to AND with "isAuto", does that sound right? I don't think I saw the probe trip during g-code running (which would be weird if it's to protect the probe). Danny On 9/7/2016 7:52 AM, John Kasunich wrote: > > On Wed, Sep 7, 2016, at 02:43 AM, Danny Miller wrote: >> I have a wireless toolsetting probe here. It's nice, but it's naturally >> sensitive. Even when you're not using it, very easy to trip, and >> LinuxCNC generates a "Probe triggering during jog" error. Just bump the >> table. The probe doesn't even have a physical hard switch, just the plate. >> >> Hmm. I don't know why it was coded to do this, but it's a problem. >> Basically it should be ignoring Probe-in if it's not probing. > You wouldn't think that if you ever ran the business end of a $500 > probe into the side of a vise while jogging.... > > The normal behavior is to protect sensitive and expensive equipment. > If you don't like that, you can modify it using HAL logic quite easily. > ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
