(moved to create its own post)
I'm currently trying to get a disk probe to calibrate. Searching the forums for info for me past the point of a A0B0 calibration (locate the sphere with the master probe and then do MAN+DCC and selecting NO for sphere movement) No problems there and it can even scan diameters.
Now trying to add A90B0 things were going great... Located the X-Minus sphere with the master probe (at A0B0 which is how we do it for everything) then proceed to swap the disk probe and run calibration which also works just fine (again MAN+DCC and selecting NO for sphere movement)
The calibration finishes and tells me the deviation is too high. Which I am ok with, but as soon as you click ok and try to move the probe again it almost immediately starts taking phantom hits, giving excessive deflection errors, and sometimes probe oscillation errors. Seems the only fix was to disable the probe on the job box, then clear all the errors and rotate back to A0B0.
My setup is as follows.
DEA Slant
PH10MQ
SP25M
SM25-4
SH25-4
30mm x 1.55 ceramic disk
PC-DMIS 2020R2
I originally had a 100mm extension there making it a 300mm probe, but after reading on the Renishaw website removed the extension thinking that was the problem. However still having the same issue now the length is within spec.
We never scan with it and this is my first machine with scanning capabilities so I am trying to learn as time allows.
Anyone have any ideas on how to not have the machine freak out once calibration finishes?
The only thought from the team is that maybe its staying in scan mode after the calibration finishes so its extra sensitive to movements? Maybe the module is going bad?
