Probing - would like 2 hits instead of just 1

[exhaustgases]

I haven't read through all this, but.
Seems like #145=50 is at least one of the issues?
And
F#145 is a feed rate you don't want?

Then just give it a number you like.

Change F#145 to F10 or what ever, then who cares what is changing
#145 variable........

[txcncman]

My first question would be, if you probe at the fast feed rate and get a setting and then manually override feed rate to a slower feed rate and probe again, do you get a variation in the setting? If not, the feed rate change would only be to make you more comfortable and does not effect the performance.

As mentioned before, the 2 hit scenario probably does not save a value that effects the final output setting. It only gets a position to probe to at a slower feed rate. The slow feed rate probing actually captures the position for setting. In this case, see above.

If the 2 hit scenario is averaging, then it may be of value, if you do obtain a difference between the first hit and the second hit.

[angelw]

In the OP's particular Probe Program, there is no second hit. In the following blocks:

G01G91X[#33*#24]Y[#33*#25]Z[#33*#26]F#146 << This block just gets the Probe close to the feature, but is in fresh air when the block terminates.

G31G91X[#32*#24]Y[#32*#25]Z[#32*#26]F#145 << This block uses the G31 Skip Function to make contact with the Feature.


This type of Macro relies on the approximate position of the feature being known. The Macro that uses two hits is one where the Feature position is generally unknown. In this case, G31 would be used in both the above blocks, so that the first block would have the Probe head in the correct direction and find the Feature by basically running into it. The probe would when be moved away form the feature a short distance and a second touch made via the second block at a slower feed rate.

exhaustgases is correct in that the occurrences of F#145 could be replaced with a fixed feed rate, but it starts to erode the flexibility of the program. Its not Rocket Science to find where and why #145 is being changed. Step through the program once in single block would reveal all, and pwilson may have found the issue given that its been some time now since he last visited this Thread.

Regards,

Bill