In the property sheet of the ModbusTcpSlaveNetwork (Figure 22), you review the default global values for Modbus device data, and specify other TCP connection settings.
Note the ModbusTcpSlaveNetwork has the standard collection of network components, such as for status, health, monitor, tuning policies, and poll scheduler. For more details, see “Common network components” in the Drivers Guide.
In addition, the following properties have special importance:
-
“Global” Modbus device defaults, which (as needed) can be overridden in the Modbus Config (server device level) slot of any child ModbusSlaveDevice:
-
Float Byte Order
Specifies the byte-order used to assemble or receive floating-point (32-bit) values in messages.
-
Long Byte Order
Specifies the byte-order used to assemble or receive long integer (32-bit) values in messages.
By default Niagara supports Modbus function codes 15 and 16 (Force Multiple Coils, Preset Multiple Registers), so you do not
see these selections like you do in a client Modbus network.
-
-
Port
Specifies the TCP port used by Modbus message transactions. 502 is the “standard” Modbus TCP port. Leave at the default (502) unless the Modbus TCP master uses another TCP port.
-
Socket Timeout In Millis
Default is 30000 (milliseconds, or 30 seconds—the minimum). You can adjust upwards if necessary.
-
Maximum Connections
Default is 5. You can adjust from 1 to 100 as needed.
Double-click the ModbusTcpSlaveNetwork for the default Modbus Tcp Slave Device Manager view, which you can use to add one or more ModbusTcpSlaveDevice children. For general information, see “About the Device Manager” in the Drivers Guide. See Modbus Tcp Slave Device Manager notes for additional details.