new Component probefilter to handle "probe tripped ... errors"

rodw wrote:

Its good you have got your hands dirty early in your linuxcnc journey. As always, there are many approaches to solve this problem.

When I faced this, I modified my probing gcode routine to set a digital output true from gcode and false after probing.
Then you can and2 the probe output with the digital output before connecting to motion.probe-input.

Another robust component based approach would be to read motion.motion-type and only output a probe output when it equals 5. 

Code:

motion.motion-type OUT S32 These values are from src/emc/nml_intf/motion_types.h. 0: Idle (no motion) 1: Traverse 2: Linear feed 3: Arc feed 4: Tool change 5: Probing 6: Rotary unlock for traverse ref: http://linuxcnc.org/docs/2.9/html/man/man9/motion.9.html#MOTION%20PINS