Vision and Probe Calibration Offset

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.

Attached Files

NeilRyan over 4 years ago

Hi bfire85

I can confirm the AutoQual issue you mention has been fixed and will be in 2019 R2 SP4 when it is released. If you have any questions, please reach out to me at neil.ryan@hexagon.com
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
bfire85 over 4 years ago

Hi bfire85

I can confirm the AutoQual issue you mention has been fixed and will be in 2019 R2 SP4 when it is released. If you have any questions, please reach out to me at neil.ryan@hexagon.com

Hey Neil! Thanks to you and your team looking into this issue and resolving it for the next SP release.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vpt.se over 4 years ago

If possible, please don't let stuff like this out the door the next time. Include this check in the QA routines...

Fast and wrong are bad, slow and correct is good (release-wise).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
bfire85 over 4 years ago

Hi bfire85

I can confirm the AutoQual issue you mention has been fixed and will be in 2019 R2 SP4 when it is released. If you have any questions, please reach out to me at neil.ryan@hexagon.com

I can confirm that this is indeed fixed!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
sealevel over 4 years ago

Glad your issue was fixed Barry!. Perhaps some of mine have been fixed as well, but since our SMA expired on Halloween 2019 ?
NO more SP updates for 2018 R2, 2019 R1 & 2019 R2 releases (which obviously need their Hexmeds to get better..)
Que lastima::::::::::::........
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
bfire85 over 4 years ago

Glad your issue was fixed Barry!. Perhaps some of mine have been fixed as well, but since our SMA expired on Halloween 2019 ?
NO more SP updates for 2018 R2, 2019 R1 & 2019 R2 releases (which obviously need their Hexmeds to get better..)
Que lastima::::::::::::........

I think that change is not a good practice for Hexagon. Now, take it in my case, assuming I let my SMA lapse. If Hexagon broke calibration and they fixed it after my SMA lapsed, I am now stuck with a software that is broken? Nobody in their right mind buys a product that is broken and just accepts it. I think if that's the case, we need to push back....or talk to our rep to pull strings. If Hexagon is at fault, then they should fix it....like a vehicle recall.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
anthony.alfaro over 4 years ago in reply to bfire85

this has been a battle for ages.

generally speaking you can get hexagon to do what you want as long as you buy something.

we paid for an SMA a couple of years ago. I can't remember exactly what version but i think i have 2018R2 and it works for me and does everything i need it to do so i haven't updated since because i subscribe to the same theory of "why would i pay for something that barely works?"
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel