B&S Excel 7-10-7, PC-DMIS 3.7MR3, PH10mq, TP20
This has happened yesterday and today. Haven't seen it before.
Both days, we started the machine up. Then, we went to calibrate the tips used in a program. Upon completion of the calibration we get the error about the std dev. exceeding limits.
Go to results file and the std. dev. is coming in around .0020 inches! So, yesterday, I tried a different probe and the same. Shut down, re-start and everything was fine (std. dev. .0001).
Today, I get the same initially (.0020) shut down, re-start and .0020 still, different probe - .0020. Different module (tp20) - .0020.
I checked to make sure the cal. sphere was defined properly - it was/is.
I created a new probe file - .0020.
Tried creating a new program - .0020.
I tried answering yes and no at various times to the sphere having been moved - .0020.
Suddenly, after switching back to original probe and original probe file - .0001. Now all seems to be good again.
Anybody got any suggestions to try next time this happens?
This has happened yesterday and today. Haven't seen it before.
Both days, we started the machine up. Then, we went to calibrate the tips used in a program. Upon completion of the calibration we get the error about the std dev. exceeding limits.
Go to results file and the std. dev. is coming in around .0020 inches! So, yesterday, I tried a different probe and the same. Shut down, re-start and everything was fine (std. dev. .0001).
Today, I get the same initially (.0020) shut down, re-start and .0020 still, different probe - .0020. Different module (tp20) - .0020.
I checked to make sure the cal. sphere was defined properly - it was/is.
I created a new probe file - .0020.
Tried creating a new program - .0020.
I tried answering yes and no at various times to the sphere having been moved - .0020.
Suddenly, after switching back to original probe and original probe file - .0001. Now all seems to be good again.
Anybody got any suggestions to try next time this happens?
Comment