Inconsistent values from Versaprobe

In the ini, under Versaprobe there is Diameter. Maybe you can add below HEIGHT = nnn and use it as #<_ini[VERSA_TOOLSETTER]HEIGHT>
It could look like this:

I tried what you recommended, this time after the back-off touch, nothing happened and the spindle just sat there with no movement. Although no error.

For some crazy reason I also lost control of my WHB04B-4 MPG. Incredibly annoying!

As an FYI in versaprobe routine there is a BLOCKHEIGHT and PROBEHEIGHT which is what I suspect that you're eluding to here.

I'd like t o hear from ANYONE who's is successfully using VersaProbe successfully using the master.

Realistically, I simply want an error free manual tool change with minimal error margins.

Thanks @MaHa!

MaHa wrote:

Can you try to replace this 2 lines from

Code:

#<zworkoffset> = [#5063 + #[5203 + #5220 * 20] + #5213 * #5210] #<tool_length> = [#<zworkoffset> - #<_ini[VERSA_TOOLSETTER]Z_REF>]

to

Code:

#<zworkoffset> = [#5063 + #[5203 + [#5220 * 20]]] #<tool_length> = ABS[ABS[#<_ini[VERSA_TOOLSETTER]Z_REF>] - #<zworkoffset>]

 
point calculation before line calculation

here the square bracket was wrong, maybe that also leads to calculation errors
#<zworkoffset> = [#5063 + [#5203 + [#5220 * 20]]]

here the square bracket was wrong, maybe that also leads to calculation errors
#<zworkoffset> = [#5063 + [#5203 + [#5220 * 20]]]

You need to be careful with parameter index vs parameter value:
this will add the index offset of the currently active work offset system to the _value_ of parameter 5203 (which is what you do not want here):
while this will add the index offset to 5203 to get the parameter index of the z-offset for the currently active work offset system and thus will give the value of the currently active work offset system (which is what is needed here):

Did you ever get past reprobe? There is no backoff move, then is G43 called and at least G53 Z0, which makes no sense to call G43, while toolseter trigered. First i would cleanup this file with all commented lines and debug,  or do indentation, to make the executed code visible.
When the machine stalled, did it write toollength before?
For testing i always start from terminal. If necessary just close the terminal, and start new.
 

"When the machine stalled, did it write toollength before?"

No it did not.

I will check again shortly. Although, I'd realistically like to see someone's qt_auto_probe_tool.ngc file that
has the versaprobe routines successfully running.