Best fit calculation errors 2024.1

Are these calculation errors coming from the auto-features or are they coming from constructions?  I've never seen that error message from an auto-feature.

These are coming from an auto feature. It happens both when the auto feature is used in a construction and when the auto feature is stand alone. It seems to be happening only to auto circles, not auto cylinders (all adaptive circle scans).

Yes - I just saw your previous edit.  What might be happening is that the scans are throwing away points.  This can happen if the holes are off location by an amount that is more than the probe offset force can handle.  Because the auto-feature scan strategies use defined scans, they aren't able to automatically adjust for that type of thing - they would really need to be relearn scans.  A potential way to avoid these types of problem would be to use relative measure.

I am having this exact same issue.  It appears that it is just filtering out points until it doesn't have enough data to be able to calculate a circle.  I'm also using an adaptive circle scan, and they error out randomly.  This seemed to work fine on a previous version of PC-Dmis, but started having problems when we switched to 2024.  I don't have any resolution at this point, but am trying to play with filter settings to see if that helps at all.  Curious if you were able to figure anything out.

double check your UPR on the filters tab then the Path Density on the path definition tab. why the defaults are not automatic is beyond me.

Hello Jgiff18, 

Recently after looking at similar issue routine, I would like to share my thoughts with you:

1. Circles measured by adaptive sacnning may be threaded holes. Use pitch input in such a case. For threaded holes, adaptive line strategy with cylinder may be better choice.  

2. The scan speed is very high. Point density used is low. In your case, it looks that point density you may be  4 pts per mm for 0.376 inch holes with problem. 

3. If you use very high speed then it can cause issue.  For 0.376 inch hole, perimeter would be about 30 mm. If you use speed of 20mm/s, the scan time will be about 1.5 sec. In this much time, you can collect  about 124 points with point density of 4. 

4. Not knowing any speed, point density and other parameters as well as hole is threaded or not and does it move a lot, as well as how big diameter devaitaion you expect, as well as location deviation you expect, I would suggest to lower your speed or optimize it for your need - position, form, diameter. 

5. It looks to me that this error occurs when numbe of points collected are less that 3 for circle. I can not be positve on this but bases on your description that when error happens there is only 1 point. It can be combination of high speed, hole position moved and diamter having bigger deviation.. just a thought. 

Hope this helps. Beyond this, you may want to capture debug file with this error and collect your routine, prb files, CAD file if possible and work with Tech support.  

Had some other issues with 2024.1 and no help from Hexagon after sending them debug files (as far as I know, they haven't looked at them yet and were sent over a month ago) so we rolled back to 2023.2. Just giving an update.

Adding the relative measure code line into my program fixed this issue for me. I had an auto circle scanning a feature on an injection molded part and during some process adjustments, it threw a circle feature outside of the deflection range of my scanning probe.

anp1994  did you use the "Legacy" or the "default" relative code? 

 

RMEAS/LEGACY (I,J,K, X,Y,Z)
            RMEAS/DEFAULT (I,J,K, T)