/
Migration to I/O Interfaces

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.

Migration to I/O Interfaces

Page Content

What are the advantages?

The new I/O interfaces allows enabling the visualization and editing 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

Starting from RT-LAB 2025.1, the migration is carried automatically when a project is opened.

  1. Open your project

  2. Follow the migration wizard instructions

    migrate_project_wiz1.png
    Migration wizard (window 1)
    migrate_project_wiz2.png
    Migration wizard (window 2)


    Please back up your project by keeping the corresponding checkbox selected.

  3. After clicking on the Finish button, the migration process is triggered. Next, depending on the outcome of the migration :

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

Compiling the model is essential to ensure that all information required for automatic migration is available within the workspace.

Your project is opened with limited access: you can only edit and build it to complete the migration on the next opening.

Once all your models are successfully build, you may close and reopen it to complete migration.

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

Compiling the model is essential to ensure that all information required for automatic migration is available within the workspace.

Your project is opened with limited access: you can only edit and build it to complete the migration on the next opening.

Once all your models are successfully build, you may close and reopen it to complete migration.

 

Migrated project into Dashboards

Dashboards can be opened by double-clicking on “Dashboards” 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:

Considerations

Once the project has been migrated to Dashboards,

  • 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.

    • 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.

    • Perform Autoconnections option is no more available in this version but can be used by API (for more details, please refer to Auto-Connection in RT-LAB)

Migration failure

If the project migration fails even after compiling your model(s), please read the <Project Path>/configurations/opalone/migration_report.log file.

If the issue persist please contact OPAL-RT support and provide the full project in a zip file or the following files

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

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

  3. The report generated by the diagnostic tool (which can be launched in RT-LAB via the menu Help > Run Diagnostic)

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 caused by an installation issue, please use the diagnostic tool (Help > Run Diagnostic) in this case and contact OPAL-RT support.

A migration report contains:

  • Information about IO Interfaces

MIG #### Start migration of IO interfaces #### MIG -- Start IO synchronization -- MIG IO Interface: Name: DNP3 Slave, Metadata: map[guid:D9F9CC87-4BDE-49F4-AA23-E8FA9636956E type:DNP3Slave]
  • Information about IO datapoints

MIG -- Synchronization of IO datapoints -- MIG Insert IO signal path=DNP3 Slave/Slaves/9FE36F43-E67A-407E-B047-38AD06272490/Analog inputs/656B6654-805D-478D-B74C-84C3B1CF553F name=Analog input 0 MIG Insert IO signal path=DNP3 Slave/Slaves/9FE36F43-E67A-407E-B047-38AD06272490/Analog inputs/FD876C62-3F56-41A7-9BFE-9EA57E5F551E name=Analog input 1 ... MIG New entries in database : 8 levels, 5 blocks, 0 parameters and 10 signals MIG -- End synchronization of IO datapoints --
  • Information about connections between IO Interfaces and models

MIG -- Synchronisation of connections -- MIG 10 connections found. MIG Connection between 'DNP3_Slave/sm_dnp3_slave/Analog_to_master/OpOutput/port1' and 'DNP3 Slave/Slaves/9FE36F43-E67A-407E-B047-38AD06272490/Analog inputs/656B6654-805D-478D-B74C-84C3B1CF553F' MIG Connection between 'DNP3_Slave/sm_dnp3_slave/Analog_from_master/In1/Value' and 'DNP3 Slave/Slaves/9FE36F43-E67A-407E-B047-38AD06272490/Analog outputs/8E8AEAA4-8ED8-4F16-87B3-8AA56D609090' ... MIG 10 connections to insert in database INF IO DNP3 Slave assigned to DNP3 Slave/sm_dnp3_slave MIG -- End synchronisation of connections --

 

  • Errors on connections may be reported but are not critical to complete migration.

They concern unresolved connections that can be observed in the Configuration panel in RT-LAB version prior to 2025.1 when the top-level connection count is inconsistent with the sum of the connections present at the data point level. The following image illustrates what unresolved connections may look like.

With the new IO interfaces, these connections cannot be restored but are logged in the migration report. You need to update your IO configuration and/or recreate these connections.

The connection paths concerned are listed at the end of the report:

 

  • Errors on datapoints may be reported but are not critical to complete migration, it should be the case if these datapoints are involved in invalid connections as mentioned above

 

  • Any kind of critical error may stop the migration process. In these special cases, you may try to rebuild your model(s) and reopen your project to relaunch migration. If the problem persists, please contact OPAL-RT support.

OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | opal-rt.com | +1 514-935-2323
Follow OPAL-RT: LinkedIn | Facebook | YouTube | X/Twitter