hexagon logo

Machine lost orgin of all parts after probe change

Hi guys, this is kinda a continuation of my other thread
https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-for-cmms/535953-hexagon-wont-help-me-so-now-i-ask-you-for-help"

Where our tips wouldnt relate to eachother and have big deviation in XY.

I fixed this by deleting all our probe files and rebuilding them.
And when i rebuilt them i rebuilt them "correctly" because ver time we've made some changes to our probe system, but never actually updated the probe file, cos the changes were minimal. Ex:

1. Probehead from Tesastar-m to HH-AS8-T5 (Which Tech guy said is identical to the tesa)
2. Tp 1 in our rack (also master) used to be a ⌀2 ruby with 20mm/1⌀ stem + 10mm/3⌀ extension.
Now its a ⌀2ruby with 30mm/1.5⌀ stem.
3. Tip 2 changed from ⌀4 ruby with 20mm/2⌀ stem + 20mm/3⌀ extension
Now its a 4⌀ruby with a 40mm/⌀2mm extension.


So none of these changed affected our measurements/calibration.
Well anyway, so i rebuilt the probe files and calibrated the tips & got good results from calibration and also from our check program (which orgins on sphere with master and then measures the sphere with the rest of the tips and report XYZ-dev)

But when i ran our other check program (which measures a guage ring on the fixtureplate), it could find the center of the ring, but it crashed in Z as is would think the ring is much further down.
The same problem happend in all our part routines, where the machine would think the part is much lower in Z than it is.

Is this really right? shouldnt the probe find the part since we've defined our probes and calibrated them.
Or do we have to rerun the manual alignment on all our programs?

Parents
  • I think you need to call the Hexagon Service department for your region. It sounds like you have a problem with the machine mount point or mechanical offset. The 50mm difference you are seeing is due to those two head configurations being significantly different. This will not only affect all of your existing programs, it could also mean that the machine is/was using the wrong part of the error map.
Reply
  • I think you need to call the Hexagon Service department for your region. It sounds like you have a problem with the machine mount point or mechanical offset. The 50mm difference you are seeing is due to those two head configurations being significantly different. This will not only affect all of your existing programs, it could also mean that the machine is/was using the wrong part of the error map.
Children
No Data