Page Content

Description

This document explains how to use the Data Interchange Layer (DIL) system to instantiate an Orchestra I/O in order to interact with other Orchestra I/O.

RT-LAB Orchestra instantiates a single co-simulation environment by allowing the integration and interoperability between heterogeneous models, written in different programming languages or generated by various tools. It is acting as a communication layer between RT-LAB and the external components:

Open

FIG 1: Orchestra diagram

For more information about orchestra, please, check:

• Orchestra , for general information and guidance on how to use it

• RT-LAB API | Orchestra , for information about the RT-LAB Orchestra Application Programming Interface (RTAPI)

Framework

The framework is the layer allowing the communication between RT-LAB and any internal or external model of the Orchestra system (FIG 1 - “ORCHESTRA” layer). It’s the part of the communication layer that is directly connected to RT-LAB.

One OrchestraFramework I/O interface should be created for every domain intended in the Orchestra system. Several I/O interfaces may be used by the same RT-LAB model.

Orchestra Framework gives more details about the creation, setup and use of an “OrchestraFramework” I/O interface.

Client

A client represents the interface with an internal or external model. It’s the part of the communication layer that is directly connected to the external element of the simulation.

Contrary to the OrchestraFramework I/O interface, the Orchestra client might be directly integrated within the external system (as C-code for example) and may not appear within RT-LAB. Thus, an OrchestraClient I/O interface may not be needed for every communication intended.

Particularly, an OrchestraClient I/O interface needs to be created when implementing a communication between two RT-LAB models.

Orchestra Client gives more details about the creation, setup and use of an “OrchestraClient” I/O interface.