Page Content

...

What are the advantages?

Trying The new I/O interfaces allows enabling the visualization visualisation and editing new of IO connections within the new UI, offering improved scalability, performance, and an enhanced user experience.

How to

...

update old projects to new I/O interfaces

The Starting from RT-LAB 2025.1, the migration is carried out following these steps:

1. Compile your project if it has not been compiled previously.

2. Close your project.

3. Right-click on the project and select the "Try new I/O interfaces" option.

   Image Removed

4. Follow the steps in the migration wizard.

   1. Data point tree and IO assignment:

      Image Removed

   2. Connections overview:

      Image Removed

   3. Migration impact:

      Image Removed

There you have it; your project has been successfully migrated into Dashboards.

automatically when a project is opened.

1. Using your older RT-LAB version (2024.4 or older), make sure all models in the project are in a compiled/loadable state. If not, launch compilation and wait for its completion.

2. Close the older RT-LAB version and start using the newer RT-LAB version.

3. Open your Workspace

4. Open your project

5. Follow the migration wizard instructions

   Image AddedImage AddedImage Added

   
   Don’t worry, your project will be backed up in case you want to use with older RT-LAB versions
   

   Image Added

6. Your project now can be used with the new I/O Interfaces!
   

   Image Added

Migrated project into Dashboards

Dashboards can be opened by clicking on “Dashboards” or on “Configuration” in the RT-LAB Project Explorer.

...

For more information on how to configure connections of I/O Interfaces in Dashboards, please refer to the following documentation:

• Data point tables

• Connecting data points

• Interfaces /wiki/spaces/DASH/pages/18579610

• /wiki/spaces/DASH/pages/18580198

• /wiki/spaces/DASH/pages/454821101

Considerations

Once the project has been migrated to dashboardsDashboards,

• Functionality of the Recorder remains the same.

• Dynamic LabVIEW panels are still available for consultation, but do not interact with the simulation anymore. The Dashboards panels are now to be used instead of LabVIEW panels.

• Configuration view of IO Interfaces remains in RT-LAB.

• Aliases are no more supported.

• All RT-LAB API calls remain compatible.

  • GetConnectionsDescriptions GetConnectionsDescription return may differ

    • For IO data points:

      • Field name is no longer present.

      • Field alias has been added, it is the IO data point UI name.

    • For model data points:

      • Field level, alias and name are no more present.

• Connections configuration:

  • Can be done via Dashboards

  • Is no longer accessible via the Configuration panel of RT-LAB.

Migration failure

If the project migration fails, please read the <Project Path>/configurations/opalone/migration_report.log file and refer to the Known issues section.

...

1. The folder located at <Project Path>/configurations

2. The file located at <Project Path>/Controller.log

3. Opal Ones log files at C:/OPAL-RT/OpalOne/services/appserver/logs/appserver.log and C:/OPAL_RT/OpalOne/vX.Y.Z/server/logs/unicon.prod*.text.log

Migration report

The migration_report.log (under <Project Path>/configurations/opalone) should be generated no matter the migration failed or not.
If it’s not the case, it could be because the Controller.exe of the project was not properly closed before starting migration or if unicon.exe is not running.

...

ERR FAILED to create connections 'error message'

Known issues

Use of new I/O interfaces not possible because of unresolved connections

If in a project there are unresolved connections, the migration cannot be done.

...