Inconsistent values from Versaprobe

Thanks for your reply!

Indeed there is something clearly incorrect. I'm not sure that it's in code or documentation or a combination of both.

I've tried numerous times to fix this without success. I think that it goes without saying that if it's not working properly,
it should probably be removed. It's very annoying.

I was reading the qr_auto_probe_tool.ngc code and this line:

#<calculated_offset> = [#<touch_result> - #<_hal[qtversaprobe.probeheight]> + #<_hal[qtversaprobe.blockheight]>]

Appears that the tool length, #<calculated_offset>, should equal the distance between the probe length and the loaded tool length. It is saved using

G10 L1 P#<tool> Z[#<calculated_offset>]

Which would indicate the length of the tool "should" be the difference between the probe length and the loaded tool length. We can assume the #<youch_result> as zero if we reprobe the probe...I think.

However, I get -70.(Something) For my probe length and -90.(something) For my tool length when the tool is shorter than the probe. At least in the tool table.

I think it would work better if the probe touched off and then, instead of "work piece height" which may or may not be G5? Z0, we should just be instructed to probe the Z0 point and set the offset between the tool setter and Z0 as a constant. Then just add that offset to the probe height and be done with it.

I believe the coding to include block height in every calculation is unnecessary and can cause errors. Plus, and I realize it's not Python, but the code could be more readable if there was a single constant offset then just amending the new tool length by that offset.

I may well be way off base here, because I am new and the code is different than what I am used to. But, I think the height setting could be simplified a bit. Just my opinion. Not trying to step on anyone's toes because it's obvious they put a lot of work into it already.