Page Content
| Table of Contents | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Then, the following setting panel will open:
...
Logo | Name | Description | Value |
|---|---|---|---|
 | 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 OrchestraFramework configuration. | 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 OpInput and OpOutput .
...