hexagon logo

Best fit calculation errors 2024.1

Having an issue with all 3 of our CMMs. Today's example is a program I wrote yesterday. Program was written offline on 2024.1, is being ran on 2024.1 using a Global S 15.30.10 and all holes are being taken by adaptive circle scan. Part has 50-60 holes of varying sizes ranging from .251" to .594". On the smaller holes, I am getting occasional best fit calculation errors. What fixes it is F9 the feature, reselect the hole, and run again. I was running it with a 5mm probe but changed to a 3mm thinking it might fix the problem but it didn't. It is not happening on every hole. It'll run a few of one size then throw the error, I'll fix it, then it'll run a few more with no issues then throw the error again.

Also note that the part is completely clean and the probes used have a fresh calibration. My biggest gripe is that I have a backlog of programs I'm trying to get done but they want me to run this part too. I should be able to let this program run while I program (different computers) but I have to babysit the CMM to keep it going.

Why is this happening and has anyone else run into this issue?

EDIT: Something I noticed is that, before execution, the .376" holes show 48 hits, when it errors it shows one hit, and when it executes successfully it shows 124 hits. Not sure if it helps or not, I'm just passing along as much information as I can.

Parents Reply
  • 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.

Children
No Data