I am an idiot...3D Probe with Probe Basic

How to disable the on screen messages once a probed move has been made? I get tired of clearing 6 messages after a probing operation, since those measurements are being added to the UI, seems a bit redundant and a nuisance.

The max z is in all of z probe routines. You must use probing very differently than I do as I've never encountered that issue. Most of the routines require hints and you need to be fairly close on the starting position, something starting from tool change height makes quite difficult. That said, if you need to remove or adjust the calculations you can use an editor such as vscode, atom, sublime text etc.. and add the subroutine folder then do a search in the folder for max z to find all its locations. Or maybe add a if else statement if max z EQ 0 it skips the max z addition to the code.

The latest version removes the pop ups. 2.8.4 is no longer supported, so you would need to grab the updated macros from the latest git branch. Or update to Debian 12 and the latest probe basic.

So you are jogging down close to the workpiece then running the probe routine?

Correct, If you're just starting with probe routines in probe basic, it will become clear once you use them a bit why being near the work is important.

"Correct, If you're just starting with probe routines in probe basic, it will become clear once you use them a bit why being near the work is important."

Don't keep me in suspense, do tell....

Seems like waste of effort to HAVE TO jog down to the workpiece.

#<z> = #5422

It is getting the current z position every time, and if it Max Z is greater than the current position it gives the over-travel error. It needs to subtract current position from Max Z and check if it is in range, to work to my intents.

Also the macros in my version have the same date as the new work, so I am not sure how that would get rid of the messages. But I am not messing with a working install to get rid of them, I just need to know how to comment them out, and where to go to do so. Can it really be that hard, to tell someone how to comment out a line of code that calls a message. Forgive my lack of constraint, but I find trivial things to be over-complicated due to a lack of well thought out responses. Or perhaps either you do not know, or do not want to tell me.

If anyone knows anything at all, that is a real help, please chime in.

Seems like waste of effort to HAVE TO jog down to the workpiece.

you don't HAVE TOO, you can use which ever method works best for you.  But eyeballing corners or work rough centers for starting probe points within hints etc from 18 inches above the work piece for me isn't effective, maybe you are better at it and can find success there, I need to see the probe closer to the work.  doesn't mean either method is wrong, you just happen to be using a probe routine written by a person who does it that way (me..lol) so of course the routine will cater more to that method then the other.  you can change to suit and if you find it an improvement submit a pull request and we can review test and add it to the latest release.

It is getting the current z position every time, and if it Max Z is greater than the current position it gives the over-travel error. It needs to subtract current position from Max Z and check if it is in range, to work to my intents.

Again, this is to suit YOUR desires but does not conform to mine, i want finite control based on probing alone and not used as a z axis limit which is essentially what you would end up with by rewriting it to your method.  I use the max z when doing more unique probing such that i ensure i do not hit the probe body when near a ledges edge or similar.  if i were to incorporate your method this would no longer function this way.  i want to save the probe from a crash in the work and not just in the table at z full minus travel.  but again you can edit the probe macros as you desire that's why they were kept as an easy to work with RS274NGC language rather then using Python.  to make changing and editing them easier to suit individuals needs.  you can find a great reference here for the code used:

RS274NGC Reference Document

Also the macros in my version have the same date as the new work, so I am not sure how that would get rid of the messages.

I have an updated set of macros and will push them to the latest git, I checked and somehow they were overwritten by a previous change, correcting that now, should be up in a few minutes.  you can run a compare using meld or the like to see the changes that removed the debug message pop ups for the probed points.

Chris