Current Help System: Tutor Translator (View Core Help)

### Theoretical value management:

While PC-DMIS features contain both theoretical and actual values (X,Y,Z,I,J,K,. . .) Tutor features don’t have associated theoretical values.

When Tutor needs to compare an evaluated (measure or constructed) feature, it searches in the Output format table (once for each feature type) for feature fields that are required (X,Y,Z, CX, CY,CZ ,. . . . ). If the fields are required, then they are compared with theoretical values. If comparison is required, Tutor uses values stored in the theoretical table (a single table for all types of feature). The fields involved in the evaluation are normally filled with the appropriate values before the feature evaluation. Feature evaluation can be made immediately after the measure or deferred to a second time.
During translation there is no way to be sure to have all theoretical values of a feature. This is true for several reasons:

- Field(s) values are not set yet.

- The Field value is not meaningful for the evaluation.

- Field(s) value could be defined inside a called procedure.

The adopted solution provides that when a measurement command is encountered Tutor translator looks for a measurement Path or MoveTf (hit) commands and adds them in the PC-DMIS measurement command as HIT/BASIC&ldots;. THEO=NO.

When the Measurement command is completed the DmisFeatCmd.CalculateNominals function is called.

Nevertheless this method does not guarantee the accuracy of nominal values because of differences in hits and probes.

Measurement hits and move commands

The main differences in measurement hits and move commands are:

1. Tutor moveTf (hit) coordinates are the probe center ball while PC-DMIS HIT/BASIC coordinates are the measure point (on the part).

2. Tutor moveTf don’t have the measurement direction.

3. Tutor measured points can be supplied in two ways:

1. Using a path associated to the measure. This is very close to a PC-DMIS measured command.

2. Executing a proper number of moveTf commands after the measured command. In this case Translator tries to find these commands and add them in the PC-DMIS measurement command. Nevertheless it easy to find Tutor part programs that use FOR or LOOP commands to measure a feature. Because PC-DMIS does not have this capability, this kind of measurement is not translated.