Points to Consider Before Importing the CSV File

This section includes important points to consider before importing the CSV file.

Multiple Modbus Interfaces Under Same Gateway

Screenshot of CSV with proper Slave Id configuration
Screenshot of CSV with proper Slave Id configuration
Screenshot of CSV with wrong Slave Id configuration.
Screenshot of CSV with wrong Slave Id configuration.

Effect of Duplicate Slave ID During an Import

Assume that you have imported the following CSV file. This file contains two interfaces with the same IP address, but different Slave Ids. The protocol interprets these to be devices under the same gateway.

This CSV file will be imported without errors, creating the corresponding instances in the system.

Two Interfaces with same IP Address but different Slave Id
Two Interfaces with same IP Address but different Slave Id

Assume the import was successful, and you try to import a CSV file with the same IP address and Slave Ids, but different Interface and Device names (highlighted below). The importer allows you to import this CSV as well.

Another set of two interfaces, with the combination of IP address and slave Id, similar to previous figure
Another set of two interfaces, with the combination of IP address and slave Id, similar to previous figure

Interface_1 from the previous CSV and Interface_11 from the following CSV now have the same IP address and Slave Id. Since they have the same IP address, it indicates they are under the same gateway; therefore, they cannot have a duplicate Slave Id. However, they have the same Slave Id of 1. As a result, during runtime, only one of these interfaces can connect to the driver, while the other remains disconnected.

Therefore, when importing new instances in the system, the same Slave Id must not be duplicated under the same gateway.