If you look at the tool_touch_off subroutine, the tool touch-off position values appear to be stored as persistent variables in the .var file.
Specifically #5181, #5182, & #5183 (X/Y/Z).
I don't have a linux machine in front of me right now, so I can't open the UI and see
exactly how the 'set tool touch off position' button works, but I suspect it just writes the values of the three fields to the appropriate variable numbers without any super-complicated backstage stuff. It also (probably) reads those values at UI launch.
I'm not sure what the value is of using the INI file to store the location vs. just using the .vars file... but far be it from me to challenge someone wanting a 'peculiar' feature or change; I'm guilty of fiddling with all sorts of stuff like this.
If you want to store & retrieve the values from your INI file, I think you could do it like this:
Edit INI file:
Code:
[TOOL_SETTER] (or whatever you want)
TOOL_SETTER_X = 0.000
TOOL_SETTER_Y = 1.234
TOOL_SETTER_Z = 5.678
Edit tool_touch_off.ngc:
Code:
...
#<tool_touch_x_coords> = #<ini[TOOL_SETTER]TOOL_SETTER_X
#<tool_touch_y_coords> = #<ini[TOOL_SETTER]TOOL_SETTER_Y
#<tool_touch_z_coords> = #<ini[TOOL_SETTER]TOOL_SETTER_Z
...
I think that should work, but please be careful to test at
really low speeds. Note that this 'hack' has nothing to do with the on-screen tool touch-off locations which are managed through the GUI. You can still enter the location on-screen, but you've essentially hijacked the tool setter subroutine so it ignores the on-screen values (which are still stored are variables).
Further, if you update Probe Basic your 'hack' is likely to get overwritten and will need to be re-done. The subroutine will need to be edited again, and if you've made any changes to the UI those will also need to be re-added to the updated version.
Possibly you could create a new 'touch off location' display field and stick it in a new user tab - those shouldn't get over-written if you update PB.
I did something similar for my ATC sequence by using INI values for the Z-movement locations and speeds rather than the values hard-coded in the tool change subroutines.
