EasyManua.ls Logo

Scanlab RTC6 PCIe Board - Master_Slave_Config

Scanlab RTC6 PCIe Board
1004 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
543
innovators for industry
Ctrl Command master_slave_config
Function Sets settings for the master-slave interface of an RTC6 board.
Call
master_slave_config( Config )
Parameters
Config
As an unsigned 32-bit value.
Bit #0 Suppression of /Slave-START signals and /Slave-STOP signals.
= 0: /Slave-START and /Slave-STOP signals via the master-slave
interface are received and processed.
= 1: /Slave-START and /Slave-STOP signals received by this board
via the master-slave interface are ignored on this board, but
are forwarded to other boards of the master-slave interface.
Bit #1 /STOP in case of master-slave faults.
= 0: The board does not react explicitly to a fault in the
master-slave connection. Any effects are undefined.
= 1: Triggers a /STOP, if the connection to the master card is
interrupted. This occurs, for example, if load_program_file is
executed on a card of the already synchronized master-slave
chain, the master-slave cable is removed or the signal of the
master-slave interface is electromagnetically disturbed.
Bit #2 Forwarding /STOP in case of master-slave faults.
= 0: A /STOP is not forwarded to other boards.
= 1: If an error of the master-slave connection is detected and a
/STOP is triggered (see Bit #1), this /STOP is forwarded to all
still connected cards of the master-slave chain (also upwards
to a master card).
Comments For usage of master_slave_config, see Chapter 6.6.3 ”Master/Slave Operation”,
page 124.
The master-slave interface of a board should normally only be configured after
successful synchronization.
If Bit #0 is already set before sync_slaves, this board cannot be synchronized to a
master board with sync_slaves.
In certain other malfunction scenarios, fault-free operation may no longer be possible.
In this case, a /STOP is always performed on the affected board, even if Bit #1 = 0.
If the connection to a master-slave synchronized board is disturbed, this can also result
in further boards in the chain being disturbed, and thus execute a /STOP, even if Bit #2
is not set.
RTC4RTC6 New command.
RTC5RTC6 New command.
Version info Available as of DLL 609, OUT 609, RBF 613.
References sync_slaves

Table of Contents