Work with probe

@rodw
Somehow I missed that I needed to build a component for it..

Which one are you running?  I picked the probe_screen_v2.X because I saw Andy working on it. 

It does seem that going to a component or similar would be the right way to get to a clean finished product. 

I use qtdragon-hd which just works

If anyone in QTDragon is watching this thread... I'm a little confused, and nervous, about the actual physical hal pin wiring.

I've got a mesa card, so the pins I have set before, which are signalling properly on the axis interface are:
[HMOT](CARD0).inm.00.input-05
[HMOT](CARD0).inm.00.input-06

which I set like this for use in the PSNG_V3 mentioned earlier in this thread:

Note, that PSNG_V3 hal code uses an "or2" to make a combined signal for probe routines.

But in the QTDragon documentation, in section 14.5 it says we need to do this:

Which leaves me two questions:
(a) which of my input pins? I think you mean the xyz probe ([HMOT](CARD0).inm.00.input-05 for me)
(b) what do I do with the other one? (The tool-setter probe)

I'm a newb (just finished building my first machine, and this is my last step before cutting) so if I'm on the wrong base, please straighten me out.

But it seems like both are useful:
the (a) xyz probe for finding the position of the tool-head relative to the stock being worked on, and
the (b) tool setter probe for either (b.1) detecting the precise length of the tool and using the tool offset workflow, or (b.2) having it go probe the tool length on each tool-change to calculate the offset. 

How do I set both in QTDragon?

(And I'm bone tired, so I could be very stupid right now, please forgive me.)

But as a note, 'cause this is what I'm wondering, are we talking about using some kind of hal setup like they did in PSNG_V3 to create a combined signal for either probe being detected? If so, the code alkabal created might be worth glancing at... my quick interpretation is that he's doing some debouncing and cleaning of the signal but ultimately combining both the xyz probe and the toolset probe into one signal called motion.probe-input ... so would I just lift this code, because it ends up with the signal mentioned above in the QTDragon docs: namely:
motion.probe-input  ?

I've attached that code with my pins.

You are probably better off asking questions in the QTVCP section.
There are some features in its version of versa probe for tool setters. check heading #14 in the qtd docs.
If you wanted to use 2 sensors for probing, you woulf use an or2 component and connect your pins to the its inputs and the out pin to motion.probe-input
Having said that, If you have TTS or some other repeatable holder, you could just probe all your tools for height and set the tool table heights.
I went this way.  tormach.com/tts-cnc-operator-set-with-tool-assist-32284.html

Cool, I think that tells me exactly what I need to know:

(a) yes, to use both probes, you need to set or2 in the hal file (my previous post has a sample of how to do that) and,
(b) consider using the tool table with pre-set tool heights if you can manage a tool bit holder,
(c) my own add... I plan on setting up the tool height probe semi-permanently, and having the or2 logic even though I'm also going to try and use the tool-table workflow: I'll use the tool height probe if I wear out a bit or otherwise have something appear to have drifted, because I'm working with ER16/ER11/ER8 collets, and I think those are not as repeatable as you grownups have with your heavy duty setups

For ease of use, I think the best place to start for someone hopping from this thread to go use tool or xyz probing over in the new gui, would be to go to the QTVCP > qtdragon probing issues thread.

Just my two cents, thanks to everyone.

Vector wrote:

For ease of use, I think the best place to start for someone hopping from this thread to go use tool or xyz probing over in the new gui, would be to go to the QTVCP > qtdragon probing issues thread.

Just my two cents, thanks to everyone.

FInally somebody has seen the light