Page Content

Description

This document describes the I/O interface “OrchestraClient”.

The Orchestra client represents the part of the Orchestra communication directly connected to the internal / external model.

As a consequence, an “OrchestraClient” I/O interface should be created only when an RT-LAB model is expected to be directly associated with it in a given Orchestra system.

Configuration

This is the main page where it is possible to customize the “OrchestraClient” I/O Interface.

It can be accessed from the target I/O interface in two ways:

• Double-clicking on it

• Right-clicking on it and selecting the “open” option

Then, the following setting panel will open:

Open

FIG 1: OrchestraClient configuration panel

Logo	Name	Description	Value

Logo	Name	Description	Value
Open	Configuration validator	Checks the validity of the general configuration of the selected I/O Interface.	None
	Help	Opens this document page from the UI.	None
	DDF Importer	Opens the file explorer and allows to import the target DDF.	None
	DDF file path	The path to the DDF file. Can be set up manually by modifying the field directly, or by using the DDF Importer.	String
	Domain name	The name of the domain, defined in the DDF file, which will be used by the “OrchestraFramework” I/O interface and the “OrchestraClient” I/O interface to exchange data (Shared memory).	String
	Client performs wait to go during start()	Defines if the wait-to-go feature is loaded during the load of the model, or during the start. For RT-LAB, it must ALWAYS be checked if the wait to go function is used.	Checked or Unchecked
	Flag polling delays (us)	Internal delay in microseconds between two consecutive attempts to lock the publish or subscribe memory space in each Orchestra data exchange. This is only used if the field 'Force domain synchronization in polling mode' is checked in the corresponding https://opal-rt.atlassian.net/wiki/spaces/PRD/pages/505446403/Orchestra+Framework#Configuration-%5BinlineExtension%5D	Int

RT-LAB model

Blocks

I/O interfaces allow defining datapoints that are handled outside the models themselves. In order to bring the data going through those datapoints inside the models, we need to use two specific blocs called https://opal-rt.atlassian.net/wiki/spaces/PRD/pages/143787291 and https://opal-rt.atlassian.net/wiki/spaces/PRD/pages/143492453 .

OpInput

The block gives the ability to create an input connection within the model. Thus, it may be connected to any output signal coming from any associated I/O interface.

In the case of the OrchestraClient I/O interface, output signals correspond to any item of the publish part of the DDF or the 'status' signal.

OpOutput

The block gives the ability to create an output connection within the model. Thus, it may be connected to any input signal coming out of any associated I/O interface.

In the case of the OrchestraClient I/O interface, input signals correspond to any item of the subscribe part of the DDF.

Example

To illustrate a bit more what a typical client model would look like, here is a simple example.

Let’s consider two models running separately and exchanging exactly one signal in both directions.

• The first model is the framework model: it will simply send back the exact same data it received

• The second model is the client model: it will send an incremented version of the received data

In such system, the client subscribes one signal and publishes one signal. The corresponding RT-LAB model would then simply look like what can be seen in figure FIG 4.

Performing the connections between the model datapoints delivered by the OpInputs/OpOutputs and the datapoints from the I/O interfaces is explained in the following page .