RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
758
Comments
(cont’d)
General Comments (cont’d)
• An active measured value recording is terminated by
(no matter which of the following started it):
– set_trigger(
Period
= 0)
– set_trigger4(
Period
= 0)
– set_trigger8(
Period
= 0)
• If you abort a measurement session with set_trigger (
Period
= 0 ) or
set_trigger4(
Period
= 0 ), then previously recorded measurement values are not lost
and the measurement counter halts at its most recent value. This allows subsequent
querying by measurement_status of the number of data entries. In contrast, if a
measurement session is newly started with set_trigger (
Period
> 0 ) or
set_trigger4(
Period
> 0), the measurement counter is reset and the measurements
obtained thus far are overwritten. It is not possible to resume an explicitly or
automatically halted measurement session.
Comments on the Data
• The type of scan system being used determines which status signals are generated and
returned by the status channels. Specific information can be found in your
scan system’s operating manual. control_command can be used with iDRIVE
scan systems (see Glossary entry on page 27) to specify which information is returned
on the status channels.
• Only X measurement signals contain meaningful data with single-status channel
scan systems.
• 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 by select_cor_table).
Example: If the z axis is attached to the second scan head connector’s X channel
(select_cor_table(
HeadA
, 0 )), then its status signal can be queried by StatusBX
(
Signal1
/
Signal2
= 4).
• The signals 12 and 15 as well as 27 and 30 are identical, each:
SampleAZ_Corr
=
SampleBZ_Corr
and
SampleAZ_Trans
=
SampleBZ_Trans.
• Status signals
Status<…>
are a few 10 µs clock cycles later than control signals
Sample<…>
. See also Section ”Reading Out Data”, page 213.
•
Signal1
,
Signal2 =
0, 24, 31…42 and 47…51 enables logging of values that were
outputted during the previous clock cycle. Data recording of different signals is not
synchronous because of the internal processing chain. Depending on how the signals
are combined, you must later correct the data by a fixed time offset.
Delayed Short
List Command
set_trigg
er
To Next Page
Loading...