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.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Host PC (Windows)

Performance Requirements

Category

Minimum

Recommended

Operating System

Windows 10 or 11 (64-bit only)

Windows 10 or 11 (64-bit only)

Processor

 Any Intel or AMD x86-64 processor

Any Intel or AMD x86-64 processor

RAM

16 GB

32 GB

Disk

  • 8 GB of HDD space

  • additional toolboxes may require up to 6 GB more

An SSD is strongly recommended

Graphics

No minimum

No recommendation

For the below compatibility tables, the following legend applies:

  • (tick) : Supported.

  • (error) : Not supported.

  • (warning) : Partial support (read notes below table).

Microsoft Windows Compatibility

Windows 11

Windows 10

Windows Vista

Windows 7

Windows 8

RT-LAB 2023.3 and newer

(tick)

(tick)

(error)

(error)

(error)

RT-LAB 2023.2

(error)

(tick)

(error)

(error)

(error)

RT-LAB 2023.1 and older

(error)

(tick)

(tick)

(tick)

(tick)

Windows target node / MinGW compiler

In order to use the Windows command station as a target node, one compiler is available, the free and open-source MinGW compiler.

This compiler is installed during the setup of RT-LAB.

If for any reason it fails, you can start it manually, as it is located: <RT-LAB installation folder>/mingw_download.bat

RT-LAB enforces the use of a specific version of MinGW which has been verified as compatible with the software.

Real-Time Operating System Compatibility

RT-LAB targets run on OPAL-RTLinux (x86-64) and (x86-based) real-time operating systems. 

 

OPAL-RTLINUX 3.5.4

OPAL-RTLINUX 3.4.1

OPAL-RTLINUX (X86-BASED)

(red hat 5.2)

RT-LAB 2024.2 and newer

(tick)

(tick)

(error)

RT-LAB 2024.1

(tick)

(tick)

(tick)

RT-LAB 2023.3

(tick)

(tick)

(tick)

RT-LAB 2023.2

(tick)

(tick)

(tick)

RT-LAB 2023.1

(tick)

(tick)

(tick)

RT-LAB 2022.1 and older

(error)

(tick)

(tick)

RT-LAB no longer supports targets running on QNX real-time operating systems.

Red Hat 5.2 (build 2.6.29.6-opalrt-6.2.1)

End of support

This is for OPAL-RT 32 bits operating system. Note that after years of service, we have decided to phase out the support for our 32-bit Operating System, effective Q1 2024.

The last software that support the 32-bit OS is RT-LAB 2024.1. We will ensure full Technical Support until Q1 2027.

Permission Requirements

Process name

Usage

Ports

OpalDLoader 

Process responsible to start the simulation process on Windows

1987 

MetaController 

Manager of the Controller processes 

2002

OpTargetD:TCP

Process responsible to broadcast the target’s status towards RT-LAB

2525

RT-LAB

Process responsible to run the graphical user interface

33673

[47386 -> 57626]

Controller

Process that manages the simulation

[25250 -> 25349]

[47386 -> 57626]

Sshd:rtserver 

Deamon process to handle SSH communication 

51964 

51969

opald.sh/ OpalD 

Process responsible to start the simulation on OPAL-RTLinux 

58060

Opal One Database

PostgreSQL database service

60770

Opal One App Server

Unicon processes manager

60780

Unicon

Resources manager for OPAL-RT applications

Random available port (assigned by the App Server)

Maestro

Simulator management server

60781 (TCP/IP for shared socket)

60782 (gRPC)

opal-services-handler

Manage Maestro and App Server processes

n/a

The processes need to be authorized through the firewall.

OPAL-RT Chassis Compatibility

  • OPAL-RT chassis have reconfigurable FPGA boards for which the compatibility varies depending on the version of RT-LAB. It is important to note that the same OPAL-RT chassis (ex: OP5600) may be powered by different FPGA boards (ex: OP5142_1, OP5142_2, ML605_1, and ML605_2 or OP5143).

  • In the column header, the different possibilities of FPGA boards are under each OPAL-RT chassis. The FPGA boards are identified with their firmware filename prefix.

    • For example, the “MMPK7_1-EX-0001-2_2_2_4-RESOLVER_IO-02-01.bin” firmware file is for the “MMPK7_1” FPGA board in the “OP4500” OPAL-RT chassis.

  • The table below presents the compatibility between RT-LAB versions and OPAL-RT chassis that serve as target nodes. In other words, all these OPAL-RT chassis have processor power. The OP5031 chassis is the only one without an FPGA board and, without an I/O expansion box, has no I/O capability.

RT-LAB vs OPAL-RT Chassis (Target Nodes)

OP5031
(no FPGA
board)

OP5600
OP5142_1
OP5142_2
ML605_1
ML605_2

OP5707
VC707_2

OP4500
MMPK7_1
MMPK7_2

OP4510
TE0741_3
TE0741_4

OP5650
OP5143

OP4512

TE0741_4

OP4610XG

TE0741_4

OP5705XG

OP5143

OP5707XG

VC707_2

OP5033XG (no FPGA
board)

RT-LAB 2024.2 and newer

(error)

(error)

(error)

(error)

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

RT-LAB 2024.1 and older

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

RT-LAB vs OPAL-RT Chassis (I/O Expansion Boxes)

OP5607
VC707_2

OP7000
OP7160_1
OP7160_2
OP7161_1
OP7161_2

OP7020
VC707_1

OP4520
TE0741_2
TE0741_3
TE0741_4

OP7170

OP4810/OP4815

Versal

RT-LAB 2024.2 and newer

(tick)

(error)

(tick)

(tick)

(tick)

(tick)

RT-LAB 2024.1 and older

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

  • No labels