Library
rtlab/Orchestra/Proxy
Block
This block allows a user to exchange data between an RT-LAB Orchestra framework and C External Components.
Orchestra_Proxy_C block
Mask
Description
This block acts as a bridge between the current model and an External Components. Refer to the RT-LAB Orchestra page of the RT-LAB user guide for more information about RT-LAB Orchestra.
Parameters
| XML file | Name of the file to be used to read data information. Click on the Configure button to start the DDF Configurator. |
|---|---|
| Sample time | Block sample time. Determines the rate to exchange data with the External Components. |
| Domain name | domain name to use in the DDF. |
| Work in Simulink mode | Enables/Disables the connexion to the RT-LAB Orchestra framework when running the model outside of an RT-LAB Orchestra co-simulation. |
| Create Goto/From subsystems | Click on this button to trigger the creation of the ‘Goto’ and ‘From’ blocks for all items described in the XML file under the FRAMEWORK_TO_CLIENT and CLIENT_TO_FRAMEWORK sections of the selected domain. |
Input (Wait-to-go)
The input is used to block the connection of the External Component to the framework. If the input is 1, the client will be blocked, when pass to 0 it will be unblock it. By letting it unconnected it will not block the External Component connection.
The default behavior would be there is no wait granted before publishing and subscribing, Otherwise there is a wait for the signal to start data exchanges.
This behavior is specifically designed for synchronous mode and by considering the domain name.
The wait-to-go input pin is used to hold the beginning of Publish/Subscribe of External Component until a falling edge.
By leaving it unconnected or having a constant set to 0 connected to it will provide the default behavior which is publish and subscribe upon connection.
This can be use to synchronize multiple Domain to start altogether.
If this input is actively used to synchronize RT-LAB based clients, it is important to disable the watchdog for the client models to prevent undesired simulation failures.
Warning: In synchronous mode, using this feature may block the framework causing overruns.
Outputs
| Output#1: ConnectionCount | Outputs the number of external components connected to the Framework. In case of synchronous use, This output is incremented before blocking, while waiting for wait-to-go input. Note that ConnectionCount output is neither the number of active connections nor the number of attempted ones. |
|---|---|
| Output#2: ConnectionIsActive | Outputs the status of the connection with an External Component. The value is 0 if there is no External Component connected to the framework otherwise the value is 1. |
Tip: It is possible to use the Connection Count pin of Proxy blocks and a Nand gate to control the Wait To Go input and therefore synchronise multiple Domain within the Framework.
Characteristics and Limitations
Direct Feedthrough | Yes |
|---|---|
Discrete sample time | Yes |
XHP support | Yes (Partial XHP only) |
Work offline | Yes |