Work with probe

verser,
thank you for updating your code.... I have used it for many years. It is great.
Are you going to push it to the master branch, and python 3 ???
Hope so.

This work will need to be done soon.

What is the value of the buttons (1) if the enable measurement is still pressed with an offset?
What does the ERR check mean (2)?
 

jcdammeyer wrote:

To make the the probe screen work with metric or imperial and respondent to the G20 G21 G-codes the same sort of operation must occur. 

There are two ways to do it, I chose the simpler one, which is to switch back to the machine base units before doing moves based on numbers in the INI file.
I did this because the probe screens call numerous G-code files and the alternative approach (multiplying all movements by a conversion factor) would have required many more changes, with no easy way to be sure that I had caught them all.
I based this partly on an assumption that any G-code run in non-base units would contain a units switch in the header lines.

Another question. The remap enable button has disappeared. I use a tool in a cone BT40 and every time there is no need to measure. What should I do?

Probe Screen v2.8.1  -  added sensitivity  to MDI commands G20, G21.

I ignored the fact that the screen was metric. Changed all the rates and distances to imperial and just use it that way. I don't think the version of the probe screen I'm using issues a G21. If it did I probably removed it.

JohnnyCNC,
Excellent work on this. But I'm puzzled.

Your updated document refers to measure_tools_inch.ngc which you included along with the date in the file name. (Actually the document refers to "measure_tools inch.ngc" Note missing underscore so that's a spot in the document that could be tweaked.)

But it also refers to measure_toolsetter_height.ngc which is not included.

Where is this file? None of the other zip files have a file with precisely this file name.
Thanks
John

Thanks. The date was added so that if I post a revised version it will be apparent which is the latest.  I'll fix my doc to correct the missing underscore.
Currently I am trying to get this to work with 2.9 and QTDragon_HD.  The issue is that the probing is now being done in Python and I haven't figured out how to update a numbered parameter from within Python.  I need to save the probed value with some math applied to parameter #4001.

Attached is the file.  This is used with no actual tool in the spindle.  It measures where the Z is when the nose of the spindle trips the tool setter.

 

Hmm, apparently the forum added the date and not me. Probably for the same reason. There was no date on the file that I selected to post.