RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
807
Ctrl Command sync_slaves
Function sync_slaves is no longer necessary as of DLL 614, OUT 614, RBF 619.
Synchronizes all slave boards (connected in a master/slave chain with the slave connection
of the addressed RTC6 board) stably to the 10 µs clock cycle of the addressed RTC6 board.
Call
sync_slaves()
Comments • For usage of sync_slaves, see Chapter 6.6.3 ”Master/Slave Operation”, page 124.
• With RTC6 Software Package V1.5.2, the actions described below for RTC6 Software
Packages <V1.5.0 are no longer executed.
• RTC6 Software Packages <V1.5.0 (< RBF 619):
– SCANLAB recommends executing synchronization immediately after all boards have
been initialized by load_program_file and load_correction_file.
Otherwise, all involved boards (that is, the master board and the downstream slave
boards allocated to the user program) should already have been halted prior to the
call of sync_slaves. To avoid irregularities during execution of sync_slaves, you
should neither apply external stop signals to the boards nor trigger External Starts
(this is not automatically prevented).
– During the course of sync_slaves, a simulate_ext_stop is passed to the addressed
board. This halts the addressed board and all downstream slave boards in the
master/slave chain (including boards not allocated to the user program).
Users themselves are responsible to ensure that any running processes are not
disrupted by that.
– After execution of sync_slaves, the scan system axes of all involved boards are in
either the coordinate center position (0, 0 [,0]) or the HomeJump position (possibly
shifted by an offset set by set_offset, set_defocus or set_hi).
– sync_slaves (relating to synchronization) only affects RTC6 boards connected in a
master/slave chain to the Master connector of the addressed RTC6 board. It does not
affect the addressed board itself or any boards connected to the Slave connector of
the addressed board. Therefore, if all slave boards of a master/slave chain is to be
synchronized with the master board, then sync_slaves must address the master
board of the master/slave chain. sync_slaves has no effect, if no board is connected
to the Master connector of the addressed board.
– Synchronization of downstream slave boards by sync_slaves occurs even when the
boards’ BUSY list execution status or INTERNAL-BUSY list execution status is set (they
are automatically halted). Nevertheless, the only slave boards to get synchronized are
those allocated to the user program (allocation is not requested automatically). If the
user program possesses access rights for the addressed board but no further boards,
then sync_slaves has no effect.
– During the course of sync_slaves, all get_startstop_info error bits are cleared on all
boards (including upstream boards) allocated to the user program.
To Next Page
Loading...