Can you make a program continue after it misses?

[[An...]]

I have a part with a small ridge that I probe with a 0.6 x39mm stylus. 90% of the time it works fine but sometimes it will miss due to the ridge being to small.

I would like for the program to continue after missing the ridge, so it saves points and spits out a report for the operator. Is this possible? I have messed with "material missing" in the editor menu but that had no effect.

[[Mi...]]

Yup in the same place you found the Material Detection, there is one called "Continue at missing probing"

Turn it on for the feature(s) in question. Obviously you have to be careful where you use this.

[[An...]]

That did not work for some reason. it just missed the ridge and went to green light.

Does it matter that it is a line? Sensitive probing? search distances?

[[An...]]

I also do not have PCM if that matters

[[Mi...]]

I believe you need to set both Material Detection to any number thats not 0 ( this will be how far it searches), AND have continue at missing probing turned on.

[[Ke...]]

You may also need to adjust your Search After Nominal value as well, to set how far it will continue past the nominal point before registering as having missed

[[No...]]

The help file says missed probing doesn't work with scanning. Did you scan the ridge?

Another option would be to use material detection. This one is said to produce no errors regardless of the result. But it only works with a point feature. If it hits the point within the search distance, it fills in the actual coordinates, if not it fills in 9999/9999/9999. If you don't have PCM you might be able to query the status with a condition, but as conditions can only be put on characteristics, I 'm not sure how to actually make this work. Anyway, the formula to use is getActual("Point_XYZ").materialDetected The return value is 'true' or 'false' and '9999' in case of an error.

[[An...]]

I have tried both suggestions with no success.

I have before and after search distances at 0.06(1.5mm). I tried material detection at both 0.04(1mm) and 0.08(2mm) to see if either side of search distance would matter. Every time it misses and alarms out.

This is a line feature with a 2 point strategy.

[[Ke...]]

Is it missing on the first point or the second?

[[An...]]

Kevin - It hits the first point fine and misses the second point.

I was wondering if that was the issue so I modified another feature to intentionally miss and that also did not work, It alarmed out once it missed. That was a circle that scanned

[[An...]]

To be more specificm the error is - "23 Nominal probing point with Pos or Step command not within search path" CNC disabled

[[Mi...]]

I have only used these settings with Points.

So without knowing the measurement requirement you have, instead of a 2d Line measured with 2 points, can you just measure 2 point features, both with the material detection settings set, then recall into a line for whatever evaluation you need to do?

[[Ke...]]

I have not tested this specific case, but my expectation is that it will red light. The continuation is for if it misses a feature entirely(the original idea is if the feature does not exist at all), which it only needs the first point for. In your case it finds the feature, but then once it is found fails to measure. This would create an issue as you would have a line with only one point, which would error in calculation anyway and red light.

Michael's suggestion of doing 2 single points and recalling into a line may be a workaround, but I would not be surprised if it continues to red light when it has an error calculating a line from only 1 point

[[An...]]

The single point did indeed work!

[[Mi...]]

Please sign in to view this quote.

Harold is correct though, if the points miss and therefore do not record data. The recalled line will likely fail on calculation with an error.

So hopefully whatever evaluation you're doing you can just use the points.

[[No...]]

Please sign in to view this quote.

That's why I was suggesting a condition. The idea was to make one or more point features that are only used for detection purposes, but not for the actual result calculation. Then, if the detection points come out ok, measure the ridge seperately, otherwise skip it. The only flaw with this is that I don't know how to actually do it with a condition, since they can only be put on characteristics.

[[An...]]

The program continuing after missing works great, the issue I am now facing is that when it misses the feature does not store any actual measurements resulting in the characteristic being skipped over in the report. I was expecting it show up red or orange, some indication that something is wrong.

Is there something I can do differently so that when it misses features it flags it in the report? Or is this the way it was intended to run?

Thanks in advance!

[[Ke...]]

Any characteristics associated with the missed points should fail to calculate, which should show both in its normal position on the report as well as in a "failed to calculate" section at the end of the report

Edit to add-Totally forgot that we were using continue at missing probing for a minute there, which does not show the failures to calculate.

[[Je...]]

Please sign in to view this quote.

This isn't true for "continue at missing probing" features such as points and bore missing circles.

You could use a condition on a Result Element. "getActual("featureName").z > 1" or something similar to indicate that the characteristic was skipped. You may have to experiment with the values to get proper boolean in relation to your nominal values.