The older Ethernet IP Connector v2.1.0 is not a Connectivity Suite connector based on Databus (MQTT). The new Ethernet IP Connector (v3.0.0 or higher) is based on the Connectivity Suite interface (gRPC), which has exceptional performance compared with MQTT. To be compatible with Ethernet IP Connector v2.1.0, the new Ethernet IP Connector should cover all the functions (configuration parameters) defined by v2.1.0.
A seamless migration process is available so that the previously configured connections and data points can be migrated to the new connector.
Data Backup
Before upgrading, use the Backup function of Common Configurator to back up the connection and configuration. The backup file can be used after the upgrade to restore the connection and configuration.
Requirements
The migration process of the Ethernet IP Connector is dependent on the Registry Service app and Common Import Converter app. The required components are as follows:
| Component | Version | Remark |
|---|---|---|
| Common Configurator | V1.11 or later | An older version can be used but this has not been tested and is not recommended. |
| Common Import Converter | V2.1.0 or later | Imports tags or converts configuration files from V2.1.0 to V3.0.0. |
| Registry Service | V1.8.0 or later | Service management |
Procedure
To upgrade from an older version of the Ethernet IP Connector, install the latest version of the app according to the instructions in the section: Installing Ethernet IP Connector on the IED.
The Databus and acquisition cycle settings are lost during the upgrade and must therefore be specified again.
The following steps are executed during the upgrade:
- When Ethernet IP Connector is started, a check is made first for presence of the file FullDownloadData.json.tmp. If present, this means that FullDownloadData.json (the old configuration file) was successfully converted previously; the migration process is then canceled. Otherwise, step 2 is executed.
- A check is made for presence of FullDownloadData.json. If the file does not exist, the migration process is canceled. Otherwise, step 3 is executed.
- QueryRegisteredService is sent to the Registry Service to check for the presence of Common Import Converter and to obtain its service information. If the service information of Common Import Converter is available, step 4 is executed. Otherwise, step 3 is repeated three times. If all 3 attempts fail, the migration process is canceled.
- The file FullDownloadData.json is read and its content is sent to Common Import Converter.
- The content of the converted file (.json) from Common Import Converter is received. If the conversion fails, the migration process is canceled.
- The content of the converted file is written to the file cs_ethernetip_config.json, and the file FullDownloadData.json is copied to the folder FullDownloadData.json.tmp.
The migration process is now complete.
