Spindle Inhibit while Probing.....

Chris. appologies for bring this up again.
I have notices a pin named 'qtversaprobe.enable'
what is it? and where does it come from?
it is an output of something......

Maybe this helps:
linuxcnc.org/docs/devel/html/gui/qtdragon.html

 

thanks for the reference. I had not noticed that.
BUT, I have tested probing, and qtversaprobe.enable never comes on.
and qtdragon.spindle-inhibit does not come on either.

I have some hal set up to inhibit the spindle when the probe is loaded. Neither .enable or .spindle-inhibit are used. they are both outputs.
Outputs of what?????? that's what I would like to know,

fyi. I am using a deb from Seb's buildbot2 for bookworm/master. about a week old.

I have some hal set up to inhibit the spindle when the probe is loaded. Neither .enable or .spindle-inhibit are used. they are both outputs.
Outputs of what?????? that's what I would like to know,

Probably what the docs say, you would connect .spindle-inhibit in hal to.:

 

.enable reflects the screen button state.

To add a liyttle more detail:

-> qtversaprobe.enable

reflects the state of the 'measure tool' button on the versa probe screen.
This is a manual selection button (to ignore auto probing)
It doesn't do anything unless the remap code utilizes it such as:

-> qtversaprobe.probe-loaded

true when the tool number equals the preference files entry:
ps_probe_tool = 1

It doesn't do anything unless connected to other logic such as spindle.0.inhibit.
If you have multiple signals to connect to spindle.0.inhibit, then you must use an OR logic component.