hexagon logo

Travel Limits

Good morning all!

Here is a description of what I am working with.
Its a 2012 OPTIV Classic vision cmm with tp20 touch probes with a 3 station tool rack and PC-DMIS 2011 MR1.

Here is the issue-
I just had Hexagon come out and preform the yearly calibration on the machine. And I am now just getting back on the machine after a few weeks. I have made programs on this machine and have preformed calibrations of the camera and probes many times.
Since the calibration I cant get the probes to calibrate continuously. I can calibrate one probe tip at a time and it will calibrate Man+DCC. Until I get to a star probe with five tips, or try to calibrate all 3 probe in the probe rack in sequence (DCC+DCC) it picks up the probe and stops.

I get an error in the execution mode operations window.

it reads "Move commanded outside travel limits"
Move Absolute to X=-1.7249 Y=0 Z=3.2249

If I try to move the probe to that location. The probe would be way down below the glass. Also its of from the quall sphere in the X&Y

Is there a setting, or a file that the Service Tech needed to switch, or replace, for calibration that didn't get put back? Its like there is a clearance plane or boundary setting on.
It calibrates when I take a single hit on the quall sphere. But anything other it stops after picking up the probe.


Also none of my programs run.

I have reached out to the Service Tech a few times by phone and email and no replay.

So any ideas, help, or threads that could point me into a direction to resolve this would be greatly appreciated

Thank you in advance!

Parents
  • sealevel, and all! Well Hexagon Calibration Tech came back out and took an all day look at the machine. He was able to experience the problem all day. And left with no resolve and shaking his head. Then I had an applications engineer stop by. He had me preform 4-5 different quick checks. Just to show him the issue. The issue still showed its ugly head. The tech said huh. Just try running your program again.

    Now the program runs fine. We both look at each other in disbelief. And nothing was changed. What the heck.
    So I have no answers to what was wrong, and what was fixed.

    After the program ran all the way through. I did have to change a go home, "out of the way move/point."
    I am now thinking something was change on the previous calibration. Then when this last calibration was preformed "by a different tech" the machine was put back to an original setting? Maybe?

    Sorry for not having any solutions that I can pass on.

    Again thank you everyone for your help, time, and input.
Reply
  • sealevel, and all! Well Hexagon Calibration Tech came back out and took an all day look at the machine. He was able to experience the problem all day. And left with no resolve and shaking his head. Then I had an applications engineer stop by. He had me preform 4-5 different quick checks. Just to show him the issue. The issue still showed its ugly head. The tech said huh. Just try running your program again.

    Now the program runs fine. We both look at each other in disbelief. And nothing was changed. What the heck.
    So I have no answers to what was wrong, and what was fixed.

    After the program ran all the way through. I did have to change a go home, "out of the way move/point."
    I am now thinking something was change on the previous calibration. Then when this last calibration was preformed "by a different tech" the machine was put back to an original setting? Maybe?

    Sorry for not having any solutions that I can pass on.

    Again thank you everyone for your help, time, and input.
Children
No Data