hexagon logo

Parameter Sets and Autocalibration

Myself and another colleague were working on some Operator programs, and we were trying to find faster ways to incorporate Autocalibrate commands instead of them using the "Calibrate Tips" option from the Marked Set Window.

We were playing around with parameter sets, and were trying to find ways to avoid having to make a set for each program, but a set for each probe build instead. We created a parameter set with no tips selected.
And selected the option "Used in Routine" for the "Tips to use if none explicitly selected". It worked, and let us create this set, and we put that Parameter Set in the Autocalibrate command. It worked with no issues, even between Load Probe commands.

Is there a risk or downside to us streamlining the process in this manner? Has anyone else tried to use an Empty Parameter set in this manner?
Parents
  • I don't understand the problem in the original post but I'm excited that some people think the solution is an amazing find. Can someone explain the main issue? I don't quite understand. I also don't use operator mode. I use protected mode.
  • It wasn't exactly about a problem, but more of an err on the side of caution. I'm still need to CMM programming, and I wanted to seek advice from veterans who have been doing this stuff enough to see the bigger picture. I wanted to make sure that I avoid any bad habits when it comes to programming.

    We have hundreds of programs that run in Operator mode, and we have moments where Inspectors completely skip the Calibration process. Either on accident, or of their own volition. We wanted to make a catch-all for anyone who would skip Calibration by including it within the program. So that if they don't calibrate tips, it will at least prompt them in the program to Calibrate.

    I'm sure there's better ways of programming, but I'm just a noob.
Reply
  • It wasn't exactly about a problem, but more of an err on the side of caution. I'm still need to CMM programming, and I wanted to seek advice from veterans who have been doing this stuff enough to see the bigger picture. I wanted to make sure that I avoid any bad habits when it comes to programming.

    We have hundreds of programs that run in Operator mode, and we have moments where Inspectors completely skip the Calibration process. Either on accident, or of their own volition. We wanted to make a catch-all for anyone who would skip Calibration by including it within the program. So that if they don't calibrate tips, it will at least prompt them in the program to Calibrate.

    I'm sure there's better ways of programming, but I'm just a noob.
Children
No Data