Steve here is a MINOR bug, but it does cause some confusion for the "Probers"
The Screen designer, AND the Mach Config for inputs show a "Probe" input (at the very bottom).
The PROBE is not implemented in the Mach4 API, in the API, at the bottom, you would think you would find "ISIG_PROBE" that would follow the CP++ Jog (or maybe it was the CP--), that if it followed the pattern, the PROBE would be next, but the API has the Spindle is running, and spindle is stopped.
Not really sure, if it is worth upsetting the sequential nature of the API for signals, vs. just removing the Probing from the Config & screen designer, since Digitize does the job... and puts the touches in the Reg's.
Scott