Scanlab RTC6 PCIe Board - Page 433

RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
433
innovators for industry
Comments • For usage of get_sync_status, see Chapter 6.6.3 ”Master/Slave Operation”, page 124.
• If the addressed board has not been initialized previously by load_program_file, the
get_sync_status returns 0.
• As of RBF 619:
– Synchronization is automatic. sync_slaves is no longer required. The master/slave
synchronization state is measured automatically.
– The exact propagation time is returned by Bit #21…Bit #30, if Bit #31 does not
indicate an error.
• Up to RBF 618:
– Prior to get_sync_status, the boards of the master/slave chain should have been
synchronized by sync_slaves.
– To ensure that get_sync_status actually returns the current master/slave
synchronization status, you should first have already triggered an External Start for
the master board by an external start signal or by simulate_ext_start_ctrl, see
Section ”External Start”, page 290. For all slave boards for which External Starts and
External Stops are not suppressed (see master_slave_config), this start then triggers
a measurement of the time difference between the respective /Slave-START pulse and
respective 10 µs clock cycle. This time difference gets stored on each board as the
master/slave synchronization status (in units of 1/64 µs) and remains stored there
until the a new External Start is triggered for the master board. This gives you the
flexibility to query the synchronization status by get_sync_status even at a later
point in time.
– In the synchronized state, measured time differences are shorter than the transit
time difference for synchronization between the boards themselves, see
Chapter 6.6.3 ”Master/Slave Operation”, page 124: master/slave synchronization
status < 3.
– In a not-explicitly-synchronized state (prior to sync_slaves), the master/slave
synchronization status might coincidentally be < 3. If so, then the boards behave as
if synchronized.
– If Bit #12 or Bit #13 is set, the affected cards cannot be synchronized with
sync_slaves.
– If Bit #14 or Bit #15 is set, /Slave STARTs or /Slave STOPs may not have been
forwarded. In this case it is recommended to adjust master_slave_config and to
execute sync_slaves again.
– If one or more of Bit #12…Bit #15 are sporadically 1, this may indicate
electromagnetic disturbances that interfere with communication between the
boards.
RTC4RTC6 New command.
RTC5RTC6 Basically unchanged functionality. However, more details are available.
Version info Available as of DLL 600, OUT 600, RBF 600.
Last change DLL 614, OUT 614, RBF 619: internal improvements and additional results.
References sync_slaves, get_master_slave, master_slave
_config
Ctrl Command get_sync_status