hexagon logo

Proven Program Erroring At Multiple Points

We are running a program for a part (64mm x 64mm). We received a program from our customer and have correlated numbers after our adjustments (increasing clear planes for comfort, changing probes to what was available). The program was run smoothly for an entire day and in operator mode on second shift. We have since received 3 separate error messages today at different points in the program (probe not hitting in probing limit, small deflections under .5mm). Fearing something may still have been changed, we reverberated back to the original program and re-made our minimal adjustments to no avail. The machine is still erroring out at various points. We can made some simple adjustments to correct one or two points, but it is still senselessly deflecting at others where previously were fine.

One of the corrections we made was simply shrinking the spread of points taken for a large plane. Adding avoidance points for inner diameters. The machine is still finding ways to shank out, deflect on parts we ran fine yesterday with the same program. I don't believe in ghosts. It seems like there should be a simple fix I am overlooking, it is practically a brand new machine. Any ideas?

The machine is a Brown&Sharpe Global Performance, running PC-DMIS CAD++ Version 2014.1

Thank you in advance.
Parents
  • It looks like the program had an auto-calibrate inserted when changing probes. We took initially deleted it and calibrated our probes accordingly. The adjustment from original program probes seemed to have our new probes still registered a tad longer, hence the deflection. We did re-home and re-calibrate probes, making sure the probes built were correct, etc. Seems to working okay for now, there was an itial rush to find solution and post in the mean-time. Thank you fro such a quick response.
Reply
  • It looks like the program had an auto-calibrate inserted when changing probes. We took initially deleted it and calibrated our probes accordingly. The adjustment from original program probes seemed to have our new probes still registered a tad longer, hence the deflection. We did re-home and re-calibrate probes, making sure the probes built were correct, etc. Seems to working okay for now, there was an itial rush to find solution and post in the mean-time. Thank you fro such a quick response.
Children
No Data