hexagon logo

Autocailbration losing sphere mid calibration

Where I work we have 6 CMM's. We use the same AutoCalibrate program on every machine. It works fine on 5 of them, but on one it will run for about an hour touching the sphere and calibrating the angles we have set. Then randomly it will go out in space and try to take a hit in the air. My boss (my companies actual CMM Programmer, I'm new and still learning Slight smile ) said she has never seen anything like this. We talked with Hexagon support and they us to not reset tips to theo before the calibration and that worked until the next time we calibrated and it lost the sphere mid calibration again. They then advised us to delete all the probe files and recreate them, which I did and the same thing happened. Worked that one time and the next time lost the sphere.

Maybe someone on here has experienced this or something like this because we don't know what else to do with this machine.

The code for this autocalibrate program is just some autocalibrate commands for each tip and move points to move above the sphere to change probes. I can post the code if needed. We are using version 2014.1.
Parents
  • Other than this standard calibration, do you see any information at the faulty workstation that someone is incorrectly qualifing a single or 2 angles? All angles are tethered to a single auto-cal proceedure? As in 1 tool, 1 prompt, all the angles you are trying to qualify? It may not be a bad idea to post the code excerpt... Look in your probe directory for the .results for that particular probe and see if it shows a different date set than the other stored data. Good luck! Rebuilding the probe and angle and parameter sets worked for me when similar happened a few years ago.
Reply
  • Other than this standard calibration, do you see any information at the faulty workstation that someone is incorrectly qualifing a single or 2 angles? All angles are tethered to a single auto-cal proceedure? As in 1 tool, 1 prompt, all the angles you are trying to qualify? It may not be a bad idea to post the code excerpt... Look in your probe directory for the .results for that particular probe and see if it shows a different date set than the other stored data. Good luck! Rebuilding the probe and angle and parameter sets worked for me when similar happened a few years ago.
Children