lathe tool sensor setup , who's done it ?

has anyone actually made a working lathe tool sensor, a x- x+ z- z+ for setting tools ? if so, how did you implement it ? I tried googlefu, came up empty, and I was considering a hal component, not sure how I would implement the offsets though. but I am investigating it. 

Do you mean something like this : www.haascnc.com/video/tips/s4xeo5gcxhk.html
 

yes, 4 sided tool setting sensor. I'm working through the variables of a hal component for this. mostly trying to figure out how to send the events and store them. thinking a macro with tool position, via halui.

kinda complicated, setting tools manually is obviously les complicated and i intend to start from there.

the sensor measure's tools a specific distance z- z+ x- x+, and those offsets need to be associated when the sensor is triggered. 

it would also be nice to have a homing type routine to measure the tool once it's close. long term, be able to enter a approximate tool length and have lcnc handle the entire transaction, that's more complicated however.

but for now, triggering a tool offset measurement in a touch off, that's a start.

Yes, I set up the tool probe on my Cincinnati. You will need to create an input for the probe signal in Hal.
You then need a macro to measure the tools based on their orientation.
I wrote the macro as a custom M code. and. assigned positions based on tool orientation and clock direction. To touch off an od turning tool:
Type in MDI
M275 P12, as the top button of the probe is at 12 o’clock.

You have to measure the distance from spindle center to the probe and add it to the probed value, then write it to the tool table using G10.
I can share the Macro. You will have to write some plc code to put the probe up and down.

maybe we can collaborate here, I'll write a hal component, for the mechanics, please share the macro, I'd like to see it

I am not a lathe user and have never worked with those sensors. However, it appears to me that they create a trigger signal all the same. I thus fail to see the difference to a normal probe input. As JR1050 writes, I would expect to handle the entire tool probing in a GCode macro, potentially triggering and reading external actors or sensors using M6x commands. I fail to see the need for a hal comp, thinking this makes it even more complex.The mechanics look like it is triggered through one or maybe a few inputs. Should not require anything but M6x commands.