hexagon logo

Change in actual position vs theoretical

Just had our machine calibrated on 12/6 and I ran an automated probe calibration program late last week. Started crashing on programs that have a tight target window prior to alignment and notice that we have quite a bit of variance between actual hit points versus theoretical targets. X is +.0081, Y is + .00285 and Z is -.0304.
The technician did comment that our calibration sphere was loose and that it was ok to super glue it back into place. I did that this morning and reran the probe calibration probe with no change, still crashing.

Machine Brown & Sharpe one running PCDMIS 2020 R1

any ideas?
Thanks,
Mike
Parents
  • Is it ALL probes, or just 1 probefile for this issue? That can change your approach to finding a solution.

    Do you have a loose probe tip in a build? I've seen loose tips calibrate and pass for StdDev then give errored results. (How it passed I'll not know, but we did get seemingly crazy actuals by comparison to the theo targets)
    I realize that your description says you used the glue after, did any get on the qual sphere?
    Last thing to check, if you are using an L or other Starcluster configuration, have they rotated from their original setup? Calibration can correct to a point, but the mechanical application could result in shanking where you wouldn't have before.

    ^Just my thoughts when reading about your issue, hope you find your solution quick and easy!
  • I checked the probes. We only use 2 and they don't have any extensions.
    The machine was off prior to gluing the ball in place, I used minimal glue because my first attempt had too much and I couldn't get it seated.

    I just didn't know if the calibration routine would affect anything with the home position
Reply Children
No Data