Manual tool change + tool lengh touch off

So no need for the tool table to populate?  I think I have it running correct now....I was able to have a long reference tool to establish a G54 offset, I called a TXM6 for a short tool, and with that short tool I called it back to G54 and it hit the z target correct.  As long as I know not to look for a tool in the tool table I think I good for this part unless you think I am missing anything?

On a side note, I have another switch wired up to set my z offset "my G54" that is mobile, meaning I can set it anywhere on the table to establish my initial z offset, but I don't know where to find the code or how to initiate the probing cycle to make that happen, can someone point me in a direction to make that happen?  

Thanks again for all the help!!!!!  I'm excited to get this thing working!!!!!!!
 

Is the "mobile" thing for setting the top of the workpiece?
This is often done manually, as only you know where the reference surface is.
If your touch-plate is wired into the probe input then you would jog to close to it, then MDI (G38,2) a probe move to it, and then touch-off in the GUI to the known thickness of the sensor.

You could automate this to an extent, assigning a macro to the probe move and the G10 command to set the height above the work.
(the GUI touch-off is generally an automated G10)

Hello Vector. I installed your auto tool setter ngc and it ran through all of the code until it hit line 185. I got this error: 185 duplicate O-word label - already defined in line 173: 'o510if [#5070 EQ 0]'. I went to line 185 and changed the o510 for lines 185, 187, and 188 to o520. I am not sure if this o code is used anywhere else but now the code runs all the way through the way i expect it.

Hopefully not a silly question if i got this tool change config to work could I use it with easyprobe with min effort? (Axis Gui) easy probe not yet installed but like the GUI AXIS/Easy probe very basic.

Thanks

Bumping an old thread. Does anyone know if the g37 & g37.x macros from Pathpilot  can be used in LinuxCNC and if the code is available?

For those with large, conventional autochangers and fixed tool holders running production parts, I can see how this workflow seems forgien. However,for everyone using a manual change spindle and adjustable tool holders/collets, probing a tool length setter after each M6 is common. It is quicker than running a single toolpath per job and reduces the risk of collision due to operator error, i.e forgetting to manually update your WCS Z zero for each tool.