Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Target platform: Chooses the target platform (or the operating system) on which to run the simulation (OPAL-RT Linux RTLinux (x86-based) or Windows).

Compiler/Linker settings section

...

Target platformChooses the target platform on which to run the simulation (OPALRT Linux (x86-based) or Windows system).
Real-Time simulation modeEnables the user to define how the model’s simulation can be executed on an OPAL-RT Linux RTLinux (x86-based) or Windows system.
SimulationIn this mode, the model is not synchronized; the model starts a new Simulation with low priority: this simulation mode can be used to run a simulation in the background while working with other applications on the same computer.

...

Software Synchronized

In this mode, real-time synchronization of the entire simulation is achieved by the OS, using the CPU clock as a reference.

Depending on the resolution available on the OS, some sampling times may not be obtained using this mode.

Hardware SynchronizedIn this mode, an I/O board clock is used to synchronize the entire simulation.
Real-Time communication link type

Sets the target cluster’s communication medium.

Here are the available choices for each target platform.
• Windows: UDP/IP.
• OPAL-RT Linux RTLinux (x86-based): UDP/IP or Dolphin

Time Factor

This value, when multiplied by the model’s basic calculation step (or fixed step size), supplies the final calculation step for the system.

The time factor can only be changed when the simulation execution is paused and is only available in Synchronized (hardware/software) mode.


Note: This parameter enables you to change the I/O acquisition speed. Because the model always uses the basic calculation step, changing the time factor for the I/O may give results that differ from the offline simulation.

  • This parameter should be used only to determine the simulation’s minimum calculation step.
  • Once this step is determined, this parameter must be brought back to a value of 1.
  • The model’s basic calculation step must be updated accordingly by setting the correct value in the Simulink model and by recompiling it.


Stop Time [s]This value (in seconds) specifies when the model stops. If the value is Infinity, the model executes forever. You don’t need to recompile the model to apply a new value.
Pause Time [s]This value (in seconds) specifies when the model pauses. If the value is Infinity, the model executes until a reset is done except if a stop time is specified.

...

NameModel’s subsystem names.
Assigned Node

Select the target node where the subsystem is executed from the list of available targets.

By default, the Assigned node is set to the development node. See Preferences->RT-LAB- >Simulation Tools->RT-LAB section.

PlatformType of platform of the selected target. (OPAL-RT Linux RTLinux (x86-based) or Windows systems).
XHPIf checked, the subsystem is executed in eXtreme High Performance (XHP) mode (available only on Linux targets).
DebugCheck the subsystems you want to debug. 
Cores

(For advanced users only)

CPU cores allocated (and optionally specified) for the subsystem and its worker threads.

The system will allocate cores and will assign subsystems using the following set of rules:

  • Single-core systems do not support XHP mode.
  • Assignation starts at CPU #1 on multiple core systems; CPU #0 is reserved.
  • Specified cores are allocated first.

Unspecified cores of XHP subsystems are allocated before unspecified cores of other subsystems.

  • XHP subsystems cannot share cores with any other subsystem.
  • Unspecified workers' threads are allocated last using a fair distribution until no cores are available.


Background Color
color#D3D3D3


Note: A system with N CPU has a maximum of N - 1 subsystems in XHP.



When the Advanced section is activated, select ... in the Cores column to display the core selection dialog. Then, select the number of cores and optionally, select specific cores.

...