Page Content

Why ?

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

How to try new I/O interfaces

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.

   Open

   

4. Follow the steps in the migration wizard.

   1. Data point tree and IO assignment:

      Open

      

   2. Connections overview:

   3. Migration impact:

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

Migrated project into Dashboards

Dashboards can be opened by 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:

• Data point tables

• Connecting data points

• Interfaces

Considerations

Once the project has been migrated to dashboards,

• Functionality of the Recorder remains the same.

• LabVIEW panels are still available.

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

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.

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

A migration report should content :

• Information about IO Interfaces

• Information about IO datapoints

• Information about connections between IO Interfaces and models

• Any error reported stop the migration process. It may be related to one of the previous sections, ie.

error on IO interface synchronization:

error on connections:

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.

Unresolved connections can be seen in the Configuration panel of RT-LAB 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.

Contrastingly, in the next image, all connections are resolved.

In the migration report, you will find datapoints of connections which cannot be resolved.

In case of DNP3 Slave the best things to do is

1. Export connections by using RT-LAB API

2. Separate exported files in 2 files

   1. One for DNP3 Slave connections

   2. One for the other connections

3. Remove all existing connections in the Project

4. Import files containing all connections except the one related to DNP3 Slave

5. Update and import DNP3 Slave connections

Path has change from ‘DNP3 Slave/Analog inputs/Analog input 0’ to 'DNP3 Slave/Slaves/Slave_1/Analog inputs/Analog input 0'

Update all path and use CreateConnection RtlabApi call to create connections with new path

Example:

• Content of connections_dnp3_slave_connections.csv

• New files generated dnp3_connections_path_updated.csv

Take 3rd column (Datapoint 1: Secondary ID)

Take 5th column (Datapoint 2: Primary ID)

Add in the column containing path of IOs Slaves/Slave_1 if your data points are related to Slave_1 of DNP3 Slave configurations

• Create new connections

From python command line in RT-LAB