Work with probe

I guessed you were saying you could just get it with sudo apt update now, and lookey, yep, it's working for me now!

Well, at least Precious learned alot, gollum, gollum.

It's very, very fine UI, but... where is the probe screen?

I guess I need to hit the books and/or videos... I'm guessing in my QTDragon startup file, I don't have the probe and toolsetter pins set.

just work your way through the documents and convert stuff from axis.
linuxcnc.org/docs/2.9/html/gui/qtdragon.html
and also the QTVCP docs (too many to link to)
2.13 tells you how to select the probing method in the ini file.

Yes, it's not that bad, just looks daunting from the start. I'd done enough to get it up, but not enough to get to probe, since it wasn't 5-axis capabale way back when -- ie, 2 weeks ago

I thought you could only have one postgui hal file?? Has that changed?

See section 2.17.

Or did that limit depend on the GUI?

I'm not sure. I just used my existing postgui and extended it as required.

It wasn't allowed, I think I hit it just a few weeks ago, but that was in axis... but the QTDragon doc insists that multiple are possible.

So I'm guessing it's a gui thing, ie, postgui depends on which gui.

Wow, they did a great job simplifying the probe screen: you toggle through the probe types: Inside, Outside, Skew, & Tool Probe.

It would be nice if those were tabs, not sequences...

which is the best threat to put that thought into?

@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