hexagon logo
Register Sign in
  • Replies 5 replies
  • Subscribers 222 subscribers
  • Views 172 views
  • Users 0 members are here
Options
Related

Autocalibration Calibration Sphere

HunterS1103
Hello All,

I'm not sure if this is a common thing but i have an auto calibration program I set up to calibrate all our angles at once with. We have multiple calibration spheres that we use, for example when one is out to be certified by a 3rd party we will switch to other one. etc. my question is because I noticed that PC-DMIS defaults to the most recent Calibration sphere used when running the program. Is there a piece of code i can add to the routine to tell it what sphere is being used so it doesn't use the incorrect shank vector or sphere diameter?

thanks in advanced
Parents
  • You would create a parameter set for saying yes the sphere has moved that you measure both spheres with auto calibrate statements.
    So Parameter set 1 for your gold probe would calibrate one sphere then parameter set 2 would calibrate the second sphere.
    Then you have 2 auto calibrate statements in your program referencing each of those parameter sets you created for them both saying yes the sphere has moved. Then the rest of the auto calibrate statements would use parameter sets that have the correct sphere selected inside them.
    Someone else will explain it better, I'm on site and cannot put a good example up.
Reply
  • You would create a parameter set for saying yes the sphere has moved that you measure both spheres with auto calibrate statements.
    So Parameter set 1 for your gold probe would calibrate one sphere then parameter set 2 would calibrate the second sphere.
    Then you have 2 auto calibrate statements in your program referencing each of those parameter sets you created for them both saying yes the sphere has moved. Then the rest of the auto calibrate statements would use parameter sets that have the correct sphere selected inside them.
    Someone else will explain it better, I'm on site and cannot put a good example up.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement