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.
Executing Models
- 1 Executing models
- 1.1 Target Platform
- 2 Simulation Mode
- 2.1 Standard Mode
- 2.2 eXtreme High Performance (XHP) mode
- 2.3 Communication type
- 2.4 UDP/IP
- 2.5 Dolphin
- 3 Executing steps
- 3.1 Compilation
- 3.1.1 Execution
- 3.1.2 Additional files
- 3.2 User script files
- 3.3 Using Local User Scripts
- 3.4 Using Global User Scripts
- 3.1 Compilation
- 4 Debugging: Installing Debugger on a Target
- 4.1 OPAL-RTLinux
- 5 Setting RT-LAB configuration
- 6 Debugging the Model: Debugging Locally on Target OPAL-RTLinux (x86-based)
Executing models
This chapter describes the simulation types available with RT-LAB, explains how to build and execute a model.
Target Platform
RT-LAB supports three different target platforms:
Windows versions | For pure simulation or pseudo-real-time execution. |
---|---|
OPAL-RTLinux | For pure simulation or real-time execution for targets with an Intel x86 processor. |
Simulation Mode
Standard Mode
Simulation | Free-run, as-fast-as-possible simulation on target. In this mode, no synchronization is done. Target nodes in a distributed simulation are synchronized with the communication link. The data exchanged depends on the model’s data flow. |
---|---|
Simulation in low priority (Windows target only) | Same as a simulation but the computation subsystem runs in lower priority. It is useful when the simulation runs on the command station; it will let CPU resources be used by other applications. |
Software synchronized | The model runs in real-time. In this mode, the model is synchronized on the internal RTOS timer. Only one computation node is synchronized when executing a distributed simulation. Other subsystems are synchronized with the communication link. The data exchanged depends on the model’s data flow. |
Hardware synchronized | The model runs in real-time. In this mode, the model is synchronized on an external hardware timer. A specific block is required to be inserted in the model to specify and configure where the external clock is located. Only one computation node is synchronized when executing a distributed simulation. Other subsystems are synchronized with the communication link. The data exchanged depends on the model’s data flow. |
eXtreme High Performance (XHP) mode
The XHP mode is a mean for the real-time operating system to disable interrupts. This is done on a per-subsystem (thus per-core) basis. Not allowing interrupts prevents process switching which removes latencies time for additional computation in the same time slice.
The XHP mode is aimed at real-time applications of a given base sample time that cause overruns (overflow their allowed time-step for computation) while running in RT-LAB in the standard mode.
In XHP mode, the model waits in an empty loop for its next scheduled computation step. The next model step is then computed.
In this mode, we use the CPU counter as our