hexagon logo
Register Sign in
  • Replies 23 replies
  • Subscribers 225 subscribers
  • Views 351 views
  • Users 0 members are here
Options
Related

Auto calibrate question

Dark_Prince
I am building a program for our operators that specifically calibrates our probes. We use 3 different probes, using a probe changer rack. I am implementing the use of password protection due to the frequent "fat-finger" occurences. I need a way to let operators calibrate as easy as possible. The company i work for requires the operators to calibrate at the beginning of every shift and we run the machines 24/7 with 4 shifts of operators. I have the calibration program built. I just can't find an answer for the meaning of this:

AUTOCALIBRATE/PROBE, PARAMETER_SET=ALL-TIPS-WITH-DEFAULTS, QUALTOOL_MOVED=YES_DCC,
SHOW_SUMMARY=NO, OVERWRITE_RESULTSFILE=YES

the last statement is "OVERWRITE_RESULTSFILE=YES. I assume I want to say YES. However, even when I had NO selected i could see the results files updated when i ran the program. Does anyone know what choosing yes or no does in this situation?
Parents
  • I typically make my labeling convention avoid exact-matching terms that PCDMIS uses. MOVE is a pcdmis command. toss an _1 at the end and it becomes unique/non affiliated to any active code. I also try to avoid spaces at all costs (like the "8 MM Probe" should be 8_MM_PROBE).

    Any time you have a loadprobe command, you should define the active angle immediately afterwards, without anything in between them.

    Regarding the image:
    - When you have two if_goto statements with identical criteria, only the first goto will effectively ever happen, so nix the if_goto/std1>=0.01, goto = autocalibratemaster.
    - I would insert the MOVE_1 label just after MODE DCC, then move/increment, then loadprobe, then tip/t1a0b0, then you can create a "CALIBRATE ACTIVE TIP WITH FEAT_ID=" to calibrate just your master tip.
    -Then insert your auto-recalibration assignment check and if_goto loop just for that master probe at T1A0B0, (capitalize the T, A, and B in the assignment)
    -Insert autocalibrate all angles for the master probe tip at this point, repeat auto-recalibration assignment check if-goto loop for each of the applicable tips.
    this should fix the skipped move increment.
Reply
  • I typically make my labeling convention avoid exact-matching terms that PCDMIS uses. MOVE is a pcdmis command. toss an _1 at the end and it becomes unique/non affiliated to any active code. I also try to avoid spaces at all costs (like the "8 MM Probe" should be 8_MM_PROBE).

    Any time you have a loadprobe command, you should define the active angle immediately afterwards, without anything in between them.

    Regarding the image:
    - When you have two if_goto statements with identical criteria, only the first goto will effectively ever happen, so nix the if_goto/std1>=0.01, goto = autocalibratemaster.
    - I would insert the MOVE_1 label just after MODE DCC, then move/increment, then loadprobe, then tip/t1a0b0, then you can create a "CALIBRATE ACTIVE TIP WITH FEAT_ID=" to calibrate just your master tip.
    -Then insert your auto-recalibration assignment check and if_goto loop just for that master probe at T1A0B0, (capitalize the T, A, and B in the assignment)
    -Insert autocalibrate all angles for the master probe tip at this point, repeat auto-recalibration assignment check if-goto loop for each of the applicable tips.
    this should fix the skipped move increment.
Children
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement