Ensure that SCADAPack x70 Names Match Following a Rename
The SCADAPack x70 database items in the Geo SCADA Expert database have two names, a name that identifies the item in the Geo SCADA Expert database and a name that is specific to SCADAPack x70. When you import a configuration file from RemoteConnect, or upload the configuration from a SCADAPack x70 device, then the existing database items in the Geo SCADA Expert database are matched against the imported/uploaded configuration using their SCADAPack x70 names, except for Modbus Scanners which don't have a SCADAPack x70 name. These names are case insensitive. In the Geo SCADA Expert database, the SCADAPack x70 names comprise the following properties:
| Type of Database Item | Property |
|---|---|
| Analog, Digital, or Counter Configuration Item | Name |
| I/O Module | I/O Module Name |
| Modbus Server Device | Device Name |
| Modbus Scanner | (see Modbus Scanner Mismatch section below) |
| DNP3 Remote Device | Device Name |
| Object Browser | Browser Name |
If no match is found in the Geo SCADA Expert database during the import or upload process, then a new database item is automatically created in the database. If there are extra database items in the Geo SCADA Expert database for which corresponding items do not exist in the imported or uploaded configuration, the selected Mode determines the activity that occurs. For example, those additional database items might be automatically taken out of service; this is by design as it is assumed that those database items are no longer required.
Ensure that if you have renamed an item in the Geo SCADA Expert database, that you have also renamed the corresponding item in RemoteConnect, and vice-versa. This will help to keep both databases aligned and help to ensure that when you next import or upload the configuration, the configuration is updated without any unintended results.
To prevent a SCADAPack x70 database item from being taken out of service and a new database item being created in its place, do the following:
- Rename the existing item in the Geo SCADA Expert database to match the name of the object in the configuration file, before importing or uploading it to Geo SCADA Expert. You do this by changing the wording of the item's SCADAPack x70 name in the Geo SCADA Expert database (see the table above for the property that you should edit). This is the recommended method.
If an import or upload has resulted in unintended changes to the Geo SCADA Expert database:
- Move any associated protocol-specific points from the old database item to the newly created database item.
- Delete the old database item from the database (the old database item is the item that has been taken out of service) (see The 'In Service' Check Box and Items Taken Out of Service).
If you have renamed any SCADAPack x70 database items in Geo SCADA Expert so that they do not match the objects in RemoteConnect, do not attempt to import or upload the configuration. If you import or upload such configuration, the renamed database item(s) will be automatically taken out of service and new database items will be created with the old names (to correspond to the objects that exist in RemoteConnect).
If in the Geo SCADA Expert database, there is an Analog Configuration item with the name 'Pump Analog', and if the same object in the imported/uploaded file exists with the name 'Pump Value', the 'Pump Analog' is automatically taken out of service and a new 'Pump Value' Configuration item is created in the Geo SCADA Expert database. If you have renamed the object in RemoteConnect, then in Geo SCADA Expert, you move any associated protocol-specific point from the old 'Pump Analog' Configuration item to the new 'Pump Value' Configuration item, and then delete the old 'Pump Analog' item.
Modbus Scanner Mismatch
Modbus Scanners do not have a SCADAPack x70 name and if the imported/uploaded configuration contain Modbus Scanners, the Modbus Scanners are matched based on the following properties:
- The Modbus Server Device that is associated with the Modbus Scanner
- The Modbus Data Type
- The Modbus Register Start Address.
For more information about the Modbus Data Type and Modbus Register Start Address properties, see Configure the Modbus Point Scanner Configuration. For information about the Modbus Server Device property, see Define the General Modbus Point Scanner Properties.
If the Modbus Data Type and Modbus Register Start Address properties in RemoteConnect do not match the properties on the Modbus Scanner in Geo SCADA Expert, when importing/uploading the configuration to Geo SCADA Expert:
- The Modbus Scanner in the Geo SCADA Expert database is automatically taken out of service
- A new Modbus Scanner is created.
To prevent a Modbus Scanner from being taken out of service and a new Modbus Scanner being created in its place, do the following:
- Change the Modbus Data Type and Modbus Register Start Address properties in Geo SCADA Expert to match with the Modbus Scanner properties in RemoteConnect, before importing or uploading the configuration to Geo SCADA Expert.
If an import or upload has resulted in unintended changes to the Geo SCADA Expert database:
- Delete the old Modbus Scanner from the database (the old Modbus Scanner is the one that has been taken out of service) (see The 'In Service' Check Box and Items Taken Out of Service).
If you have changed the properties of a Modbus Scanner in Geo SCADA Expert so that they do not match the Modbus Scanner in RemoteConnect, do not attempt to import or upload the configuration. If you import or upload such configuration, the Modbus Scanner that has the changes will be automatically taken out of service in the Geo SCADA Expert database and a new Modbus Scanner will be created with the old name.