Move Exclusion Zones with Iterative Alignments

If you use exclusion zones (Insert | Move | Exclusion Zone) with iterative alignments, PC-DMIS automatically computes the starting and ending lines of the measurement routine that are to be re-executed. This means that PC-DMIS ends execution at the last feature used as part of the iterative alignment. This could prevent an arm from releasing the exclusion zone to the other arm, which thereby stops the measurement routine.

To resolve this, insert a start label for the iterative alignment. PC-DMIS executes from the label to the command just in front of the iterative alignment, which causes the arms to release the exclusion zone.

Example of a Stopped Measurement Routine:

In this example, PNT3 is assigned to ARM 2, all other commands are assigned to ARM 1.

Explanation: Even though point PNT3 is located after the PNT1 and PNT2 and before CIR1 and CIR2, due to PC-DMIS's internal logic and the presence of the exclusion zone, PC-DMIS might measure PNT1, PNT2, CIR1, and CIR2 before PNT3. Because of this, the exclusion zone after CIR2 is not released and blocks the PNT3 ARM 2 measurement.

If you use a start label at the start of your alignment features and then have your iterative alignment command block use that start label, you can get around this problem, like this:

Example of a Working Measurement Routine:

For information on how to use a start label with iterative alignments, see "Start Label" under "Description of the Iterative Alignment Dialog Box".