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 OpLnk ML605EX1 block provides support for sharing the I/O lines of one Opal-RT ML605 card from multiple subsystems of the same model..

The OpLnk ML605EX1 block does not initialize or program the ML605 card, it only enables binding of Send/Recv and I/O blocks to an ML605 card defined by its board index and bitstream file. Programming, initialization and synchronization of the card must be controlled by an OpCtrl ML605EX1 block placed in another subsystem of the model.

Parameters

Controller NameThis parameter enables the binding between this OpLnk ML605EX1 block and functionality blocks that must be associated to the same ML605 card. This string must be unique among all OpLnk and 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 0 to 31. If the ML605 is not connected to an adapter board, the value is 0.
Bitstream FileNameThis 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. The bitstream name is used to check that the ML605 card specified by its board index is programmed with the expected bitstream. The OpLnk ML605EX1 block does not trigger reprogramming of the card.
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 inputs.

Outputs

This block has two outputs:

  • The Error outport returns the following error codes:
ValueDescription
0No error.
-1Card not detected.
-5Status flag indicating that the binding between the ML605 and the OpLnk block is working properly.
-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 slot of the carrier backplane, one for section A and one for section B of the carrier.
  • For example, if an analog carrier OP5220 is installed in slot 1 of the carrier backplane connected to the ML605, and if one OP5330 module installed in slot A of this carrier and one OP5340 module installed in slot 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 an OP5251 digital I/O carrier. 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