Don't break the calibration chain!
I am posting this in hopes to have it made into a sticky since I see this issue arise a lot in the Vision section. This document perfectly explains the calibration process for calibrating offset with a Vision primary system with TTP.
A confirmed bug by Hexagon in 2019 R2 (JIRA 180393), pertains to vision-to-tactile auto calibration. Program, as written, works in 2019 R1 and older releases, but does not work in 2019 R2.
From the awesome vision people in the UK:
"I am able to reproduce the issue you are seeing... once the vision probe completes the calibration the machine just stops moving.. the execution timer continues but nothing else happens. I will see if I can identify anything obvious but this looks like a bug introduced in 2019 R2."
"I actually made a second discovery today with this issue. After the machine stops (once the vision probe cal is complete ) I went ahead and stopped execution.
Pc-dmis appeared normal.. so I executed the routine again expecting it to perform the vision probe cal again, instead the machine moved over to the rack and picked up the tactile probe, it moved to the machine centre and then just stopped with the execution dialog counting…. Again cancel and execute.. this time it dropped the probe off, before picking it up again and pausing the machine."
I will double check that is issue is still valid in R2 SP2, but I have a feeling it will be.
A confirmed bug by Hexagon in 2019 R2 (JIRA 180393), pertains to vision-to-tactile auto calibration. Program, as written, works in 2019 R1 and older releases, but does not work in 2019 R2.
From the awesome vision people in the UK:
"I am able to reproduce the issue you are seeing... once the vision probe completes the calibration the machine just stops moving.. the execution timer continues but nothing else happens. I will see if I can identify anything obvious but this looks like a bug introduced in 2019 R2."
"I actually made a second discovery today with this issue. After the machine stops (once the vision probe cal is complete ) I went ahead and stopped execution.
Pc-dmis appeared normal.. so I executed the routine again expecting it to perform the vision probe cal again, instead the machine moved over to the rack and picked up the tactile probe, it moved to the machine centre and then just stopped with the execution dialog counting…. Again cancel and execute.. this time it dropped the probe off, before picking it up again and pausing the machine."
I will double check that is issue is still valid in R2 SP2, but I have a feeling it will be.
