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.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Block

Mask

Description

The OpCtrl ML605EX1 block provides an interface to the Opal-RT ML605 card via the PCIe bus. The ML605 card holds a Xilinx Spartan3 FPGA chip, and can control up to 256 I/O lines.

The ML605 is reconfigurable. Bitstreams for this card are produced using the Opal-RT RT-XSG product, version 1.3 or higher. The OpCtrl ML605EX1 block allows the user to specify which ML605 bitstream is required by the model. Programming of the flash memory of the card is performed accordingly before model loading, using the flash_update utility.

The OpCtrl ML605EX1 block controls the synchronization mode of the ML605. The ML605 synchronization unit is fully compatible with other Opal-RT hardware synchronized cards (OP5110, OP5130-XSG, etc.) and is supported by the OpConfigSync block for easy synchronization source specification in multi-cards models.

Data transfers to and from the card as well as data pre- and post- processing are not performed with the OpCtrl ML605EX1 block, but via a block set of functionality blocks. Raw data transfers are performed using the ML605EX1 DataIn Recv block (for data transfers from the card to the model) and ML605EX1 DataOut Send block (for data transfers from the model to the card). Other functionality blocks include data pre- and post-processing, and are used for exchanging data with ML605 Analog I/Os and Digital I/Os blocks supported in RT-XSG.

The OpCtrl ML605EX1 block is also used to set the simulation state on the Opal-RT ML605 card. During the simulation, an RT-LAB model with the ML605 card passes through 4 states: LOAD, PAUSE, EXECUTE and RESET. The OpCtrl ML605EX1 block sends the current state to the ML605 card through the PCIe bus. For more information, check the Model State Example

Only one OpCtrl ML605EX1 block must be found in one model for each ML605 card used in the model. In multi-subsystem models, use OpLnk ML605EX1 blocks in other subsystems sharing the same ML605 card.



Note: The OpCtrl ML605EX1 block requires that the model be run in Hardware Synchronized and XHP mode.


Parameters

Controller NameThis parameter enables the binding between this OpCtrl ML605EX1 block and functionality blocks that must be associated with the same ML605 card. This string must be unique among all OpCtrl blocks present in the same model.
Board IDThis parameter is the integer value represented by the board index dip-switch of the backplane adapter board to which the ML605 is connected. The value is in the range of 0 to 31. If the ML605 is not connected to an adapter board, the value is 0.
Bitstream FileName

This is the name of the bitstream to be programmed on the ML605 before the model is loaded. The bitstream must have been produced with RT-XSG and must be available in the model directory at load time.

Bitstream ConfigurationThis is the configuration of the bitstream to be programmed on the ML605 before the model is loaded. This parameter allows the user to use the same bitstream for several purposes.
Synchronization modeThis popup allows the selection of the Master, Slave or Master with external clock mode of hardware synchronization. Master mode must be used when the ML605 is selected as the synchronization source of the model. Slave mode can be used when the synchronization source of the model is another Opal-RT card such as ML605, OP5110, OP5130-XSG, etc. Master with external clock mode must be used when the OpCtrl block acts as the synchronization source but receives the RTSI signal from another device.
Generate External ClockNot yet supported.
Decimation factorThis parameter is available only when the Slave mode of synchronization is selected. Not yet supported.
Sample Time (s)

This parameter allows the user to specify the sample time for this block, in seconds. The default value is 0, which specifies a continuous sample time (note that the sample time is borrowed from the separated subsystem).

These synchronization rules must be respected in the model:

  • A controller block and its related functionality blocks must share the same sample time.
  • If an OpConfigSync block is used and does not specify the ML605 card as the synchronization source, the sample time must be an integer multiple of the synchronization source sample time specified in the OpConfigSync block.
  • If an OpConfigSync block is used and specifies the ML605 card as the synchronization source, its sample time must be the fastest rate in the model.

Inputs

This block has no input.

Outputs

This block has two outputs:

The Error outport returns the following error codes:

ValueDescription
0No error.
-1Card not detected.
-2Timeout waiting for synchronization signal. If the block is in Slave mode, verify that the RTSI synchronization signal is properly connected.
-3Overrun detected.
-10This value can be added to the above codes. It signals a hardware mismatch error.

The IDs outport returns the 8 hardware identification codes of the conditioning modules connected to the ML605 via the backplane adaptor board.

Two identification codes are returned for each group of the carrier backplane, one for section A and one for section B of the carrier. For example, if in group 1 an OP5330 module (Aout) is installed in section A and an OP5340 module (Ain) is installed in section B, the first two hardware IDs are 195 (or 'C3', in hexadecimal notation) and 193 (or 'C1'). Other typical IDs are 235 ('EB') for section A, and 234 ('EA') for section B of OP5353 (Din) and OP5354 (Dout) digital I/O modules. When no carrier is installed in one slot, both IDs are set to 255 ('FF').

The hardware mismatch error is set when the hardware installed in one slot does not match the hardware required by the ML605-XSG bitstream for that slot.

Characteristics and Limitations

This block must be run in Hardware Synchronized mode.

Only XHP-mode is presently supported.

Please refer to the RT-XSG documentation for hardware setup.

Direct FeedthroughNo
Discrete sample timeNo
XHP supportYes
Work offlineNo
  • No labels