Inconsistent values from Versaprobe

I noticed that the following code appears well into the SUB:

o300 if [#<_hal[qtversaprobe.enable]> EQ 0]
   (MSG, Auto Tool probe disabled )
    G43 ;turn back on tool offset mode before returning
o300 return [3] ; indicate no tool measurement
o300 endif

Actually, after the first M6 in the code. If I'm reading this correctly, the IF statement gets evaluated when TRUE.
If this is the case then why would it not be at the very top of the SUB? The reason I ask is because the line above this block is a 
call to G49 which cancels tool length compensation. Meaning why bother to even begin the sub if it's not enabled?

That said, this return code of 3 shows up as the abort parameter in both of the failures.

Any feedback or thoughts what-so-ever are encouraged.   image missing /media/kunena/emoticons/smile.png
 

Might be interesting to output the tool length offset of the current tool and check if it is the same as #<calculated_offset>. (Note the queue buster 'M66 E L0' that makes sure the DEBUG line is not executed prematurely by the read ahead)

I believe that I see what is going on.

There is a variable named MAXPROBE that is called from the INI as follows:  #<_ini[VERSA_TOOLSETTER]MAXPROBE>
There is also a variable that is read from the versaprobe screen saved in the qtdragon_hd.pref file as follows:  ps_probe_max_z_travel
The variable is also know as max_z_travel is some of the functions.
It appears as if both VARS are used for the same purpose. If I'm not mistaken the documentation indicates that the values are to be set and used in the INI file under VERSA_TOOLSETTER (brackets omitted).

I somewhat ignored the values in the qtdragon_hd.pref file which when I compared were NOT the same values. I know for a fact that my Z will travel more that 115mm which is what it was set at in the pref file. However, in my INI file I have set the value of 150mm which covers the length of all my tools.

Additionally I found a typo which I submitted a pull request a few hours ago.

I'll test this shortly and respond appropriately.

These changes didn't help but, what does work is clicking on the "Measure/Probe Current Tool" button.

I am attaching two DEBUG files. The first is a FAILURE and the second SUCCEEDED. Looks as if the G43 is the difference. The failure is G43 Offset zero and then it succeeds with the G43 Offset of one(1) after I click start for the second time; 

FAILURE
 

SUCCEEDS
 

Interesting. There is also a discrepancy between 'Selected' tool and 'Loaded' tool.

Fail:


Success: