Block

Mask

Description

The OpConfigSync block is used to specify the source of the hardware synchronization signal when several possible sources, such as OP5110, OP5130 and OP6000 boards, are present in the model.

All these devices are capable of producing a synchronization signal which can be propagated to other devices via the RTSI connectors, thus becoming the 'master' of the synchronization signal. Alternatively, they can also be configured as 'slave' devices which receive the synchronization signal on their RTSI connector.

Since only one device in the system can control the calculation time of the model, if several synchronization-capable devices are found in the model, it is left to the user to determine which device will actually become the 'master' device. The OpConfigSync block placed in each subsystem using synchronization-capable devices and allows the user to specify which device to use. Synchronization-capable devices not selected as the synchronization source are automatically setup as 'slave' devices during initialization.

The block also allows the user to specify the sample time of the 'master' device. This feature is used to setup multi-rate models, where the'slave' devices run slower than the 'master' device, whose rate is the fastest of the system.

The synchronization source popup of the OpConfigSync block makes the distinction only between SignalWire ports and OP5110 cards. This is because OP5130 and OP6000 cards are remote SignalWire nodes connected to SignalWire ports of an OP5110 card, and all remote nodes of one SignalWire link obey the following synchronization rules: If a SignalWire port is used as the synchronization source, the last node on that port (node with larger node number) is set up as the 'master' device, and all other nodes are 'slave' devices. In all cases, all nodes connected to the same SignalWire link must execute at the same sample time.

When the OP5110 is selected as the synchronization source, one OP5110-5120OpSync block must be inserted in the model; this block must be set up in 'master' mode, and must route its synchronization signal to the RTSI bus (see OP5110-5120 OpSync documentation for more details). The OP5110-5120 OpSync 'master' block may be located in a different subsystem than the other OP5110, OP5130 or OP6000 blocks controlling the 'slave' devices.

Notes:

The OpConfigSync block makes the former 'SW_SYNCHRONIZED'user variable become obsolete, and if this user variable is defined, its setting is ignored.
Proper connection of the RTSI cables is mandatory for the model to execute properly. Please refer to your system documentation for cabling issues.
For TestDrive classic application including Current Sensor application, this block is not required. Only the TestDrive controller and functionality blocks are required.
For TestDrive with external OP5130 (Resolver box), the OP5110-5120OpSync block to produce the synchronization signal and the OpConfigSync set to OP5110to let all blocks know who is the synchronization master are required.

Parameters

Synchronization source	Specifies which system component will be used for synchronization. It is possible to select between an OP5110 board or SignalWire port. If a OP5110 board is selected, the OP5110-5120 OpSync block will determine which OP5110 board to use, in case several OP5110 cards are installed in the system. If a SignalWire port is selected, supplementary fields are provided to specify which OP5110 card holds the port to be used.
SignalWire board	Specifies on which OP5110 board the SignalWire port to be used is located. It is possible to choose either the first encounteredOP5110 card on the PCI bus or, if several OP5110 cards are installed in the system, to choose one by specifying its Boardindex value in the Board index parameter.
Board index	Enter the board index of the selected OP5110 board (see board index limitations in the Characteristics section below).
Synchronization source sample time (s)	This field provides the sample time of the synchronization master. This information is provided to all synchronization-capable boards found in the subsystem,so they can properly configure themselves. Entering '-1' for inherited or '0' for continuous is accepted.

Inputs

This block has no inputs.

Outputs

This block has no outputs.

Characteristics and Limitations

Board Index Limitations

On the PCI boards (OP511x family), the board index is user-selectable in the range [12-15], via the jumpers JP8 on the board:

Direct Feedthrough	No
Discrete sample time	No
XHP support	Yes
Work offline	No

RT-LAB Documentation

Common OpConfigSync