Documentation Home Page RT-LAB Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.

OpAsync 1553 Ctrl




This block controls the asynchronous process used to interface the model with one SBS MIL-STD-1553 board and defines general configuration settings of the board.

One controller block must be present in the model for each MIL-STD-1553 board in use. The Controller ID parameter of this block allows the user to link together all MIL-STD-1553 blocks required to define the various transactions to be performed by the board.

One typical asynchronous process is provided with the SBS MIL-STD-1553 Examples models of RT-LAB. The user can modify this asynchronous process, or specify a different one by changing the parameter Name of the executable.

For more information onMIL-1533 RT-LAB Applications, check the RT-LABMIL-1553 Manual.


Controller IDThis parameter is used to identify a Controller block. Each block must have a unique ID. Each Send/Receive block is attached to one controller through this specific parameter. An ID is a literal integer value in the range [0, 255].
PCI Index The PCI index (see definition) of the board to which the Controller block refers.
Board typeThis list allows the user to select the actual SBS or GE MIL-STD-1553 installed on the target. Some of the boards supported are IRIG capable, but the current implementation of the driver does not control the IRIG timer.
Enable BITat start-upThis parameter is used to force a Built-In-Test of the board before starting 1553 processing.
Interrupt queue lengthThis parameter determines the length of the interrupt queue of the MIL-STD-1553 device. This information is directly related to the amount of interrupt data that the card can store before processing. If the queue is undersized, interrupt data can be overwritten when successive interrupts occur close from each other in time. Larger values imply that this queue would consume more of the card's memory. This value must be adjusted depending on simulation conditions.
load custom FirmwareThis parameter allows the user to load a firmware file other than the default "f040m1.dat". When this checkbox is checked, the user must specify a valid filename in the Firmware filename mask parameter.
FirmwarefilenameThis parameter is used to specify the custom firmware filename. It is relevant only if the Load Custom Firmware box is checked.
Extended RT modeThis parameter allows the user to enable Extended RT mode on the board. In this mode, an additional timestamp value associated with each received message is returned to the model.
EnableNetwork controlThis parameter is used to enable the 'Network control' option for remote terminals. This option which is controlled by a parameter of the OpAsync_1553_RT_Recvblocks makes a specific SA acts as an echo address for the RT: it is used to monitor the 'alive state' of the remote terminal by issuing a 'ping' request to the specified SA.
Network control SA numberThe Sub-Address number that is used as a target for the 'network control' request (see above).
Status word response timeAmount of time that a remote terminal waits before transmitting a status response. Units are in microseconds and possible values range from 0.25 to 255.75 microseconds.
Bus controller reception timeoutThe maximum time a BC waits for an RT to provide a status response. Units are in microseconds and possible values range from 0.25 to 255.75 microseconds.
Name of the executableThis is the name of the Asynchronous Process that-LAB will attempt to launch during model initialization. If the executable is not present in the model directory, its full path name must be given.
Use Bus ListThis parameter must be checked if a bus list file is used to describe the BC chains to be programmed on the board. In this option is checked, a valid filename must be specified in the 'Bus ListFile Name' parameter. This feature is available only for one device-board.
Bus List File NameThe filename of the file which contains the information required for the initialization of BC bus list.
Use BC On/Off portChecking this parameter adds a block inport that is used to activate or deactivate theBus Controller feature. This option is relevant only if the model uses blocks which activate the BC feature on the board.


BCOn/OffThis optional input (see Use BC On/Off port parameter) controls the state of the bus controller. The size of this input is equal to the sub-device count of the card. If the card has two sub-devices, the first item of this input is to control the bus activity of the first device and the second item is to control the bus activity of the second device. A high value (>0.5)activates the bus controller while a low value (<0.5) stops the bus controller. When the bus controller is deactivated, model commands from BCblocks such as BC Recv and BC Send are ignored.


This block has no output.

Characteristics and Limitations

The timestamps returned by the reception blocks are asynchronous to the model. Whether the IRIG capable device is used or not, these return the raw time measured by the MIL-1553 board.

Direct FeedthroughNo
Discrete sample timeNo
XHP supportNo
Work offlineNo

OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | | +1 514-935-2323