Below is an Ethernet interface configuration example:
type;ip;mask;gateway;dns1;dns2
LAN1;192.93.121.37;255.255.255.0;192.93.121.1;192.93.121.8;
LAN2;192.168.2.12;255.255.255.0;;;
In this example, the first network interface (LAN 1) is configured at IP address “192.93.121.37”,
with a subnet mask of “255.255.255.0” allowing it to access all machines connected using the
“193.93.121.xxx” address. This interface also uses a router at the “192.93.121.1” address to
communicate with external devices and a DNS server accessible at the “193.93.121.8”
address. DNS2 is not configured.
Similarly, a second network interface is left with its default configuration, namely an IP address
on “192.1682.12” and a subnet mask at “255.255.255.0”. All the other parameters are empty.
Ethernet interframe configuration:
The interframe time for serial ports is given directly in the configuration for each serial port.
For Ethernet devices, it is more complicated to determine the communication interface with
modbusTCP devices.
The interframe parameter for Ethernet is therefore global and is configured using the line:
tcpInterFrameMs;<value>
The operating principle is the same as for the serial ports. Each time a frame is sent in modbus
TCP, the concentrator will leave a silence corresponding to “tcpInterFrameMs” between the
device response and the next query to network devices.
The interframe parameter is global, meaning it applies to all modbusTCP
communications and can therefore result in the slowing down of data reading if it is
too high.
This parameter is to be used for certain specific modbusTCP devices. See “3.1.2.1.3.3 - Serial
port configuration“ for more details on how the inter frame time operates.
When editing this file using Excel, the following display is shown using the CSV format:
To Next Page
Loading...
