Scanlab RTC 5 PC Interface Board - Page 495

RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
495
innovators for industry
Comments • For aborting a measurement session via set_trigger( Period = 0) or
set_trigger4(
Period = 0), the values of Signal1 and Signal2 will be irrelevant as long
as they’re in the permitted value range.
• If you abort a measurement session with set_trigger(
Period = 0) or
set_trigger4(
Period = 0), then previously recorded measurement values will not be
lost and the measurement pointer will halt at its most recent value. This allows subse-
quent querying via measurement_status of the number of successful data entries. In
contrast, if a measurement session is newly started with set_trigger and
Period > 0 or
set_trigger4(
Period > 0), the measurement pointer will be reset and the measure-
ments obtained thus far will be overwritten. It is not possible to resume an explicitly or
automatically halted measurement session.
• The type of scan system being used determines which status signals will be generated
and returned via the status channels. Specific information can be found in your scan
system’s operating manual. The control_command command can be used with
iDRIVE
®
scan systems (intelliSCAN
®
, intelliSCAN
de
®
, intelliDRILL
®
, intellicube
®
,
intelliWELD
®
, varioSCAN
de
) to specify which information should be returned via the
status channels.
• If the scan system has only one status channel, then only the X measurement signal will
contain meaningful data.
• With 3D scan systems, the output and status values of the Z axis are transmitted over
the scan head connector’s channel to which the Z axis is attached (if correspondingly
configured via select_cor_table).
Example: If the Z axis is attached to the secondary scan head connector’s X channel
(select_cor_table( [1 or 2], 0 )), then its status signal can be queried via StatusBX
(
Signal1/2 = 4).
• The cartesian control values
Sample<X..Z> ( Signal1/2 = 7…9) take into account any
wobbel and Processing-on-the-fly corrections, but not image field corrections or coor-
dinate transformations. The RTC
®
5 calculates the “transformed” control values
Sample<AX..BZ>_Trans ( Signal1/2 = 25…30) from the cartesian control values
Sample<X..Z> while taking into account any coordinate transformations defined via
set_matrix, set_offset, set_scale or set_angle (or via the corresponding list
commands) and any Z coordinate offset defined via set_offset_xyz, set_offset_xyz_list
or any focal length offset defined via set_defocus or set_defocus_list. The RTC
®
5
calculates the “corrected“ control values
Sample<AX..BZ>_Corr ( Signal1/2 = 10…15)
from the transformed control values
Sample<X..Z>_Trans while taking into account
any loaded correction table. The effective output values
Sample<AX..BY>_Out
(
Signal1/2 = 20…23) transmitted by the RTC
®
5 to the scan system additionally take
into account any scanner offset and gain compensations for automatic self-calibration
of the scan system (if activated via auto_cal or set_hi, also see page 199).
• The signals 12 and 15 as well as 27 and 30 are identical, each:
SampleAZ_Corr = SampleBZ_Corr and SampleAZ_Trans = SampleBZ_Trans .
• The status signals Status<…> lag the control signals Sample<…> by a few clock cycles.
Delayed Short
List Command
set_trigger