This procedure documents how to add a single device or a group of devices to any type of Modbus network. For general device
manager information, refer to the Drivers Guide.
Prerequisites: You have address information for each device as well as its data configuration (coils, inputs, input registers,
and holding registers. The device vendor’s documentation is available.
- In the Nav tree or in the Driver Manager view, double-click the client network.
The appropriate device manager opens (Modbus Async Device Manager, Modbus Tcp Device Manager, or Modbus Tcp Gateway Device Manager).
NOTE: Device types are specific to a particular parent network type—for example, you cannot copy a ModbusSlaveDevice under a ModbusTcpSlaveNetwork, or a ModbusTcpSlaveDeviceunder a ModbusSlaveNetwork. This is not a problem when working in the device manager for either of the slave networks, as the New function (to add devices)
automatically selects the proper child device component.
- Click the New button.
The New window opens. The driver preselects the Type to Add based on the network type (ModbusAsyncDevice, ModbusTcpDevice, or ModbusTcpGatewayDevice).
- Enter for number to add:
1 (or more, if multiple) and click OK.
A second New window opens with additional properties to configure the Modbus. The default values should be sufficient at least to start
with, except that:
- Async, TCP/IP Gateway and slave devices require a unique Modbus address between 1-247. This address must be unique from any
other physical device on that network.
- TCP/IP devices require a unique IP address (the device’s Modbus address can remain at 1).
- TCP/IP devices that use a TCP port other than the standard 502 port require port definition.
You might leave these properties at their defaults, particularly if different devices use the same settings—in which case
you could adjust them (globally) at the network level.
- Enter the device address in the
Starting Address property, and click OK.
You should see the device(s) listed in the Modbus device manager view with a status of {ok} and enabled set to true.
If a device shows {down}, check the configuration of the network and/or the device addresses.
- To confirm or modify device properties, double-click the device row in the device manager view.
- After making any changes, click Save.
- Right-click the device row in the device manager and click
Receiving any response from the device, including an exception response, is considered proof of communication. If the system
reported that the device was previously
{down}, any ping response is good news.
The default ping address for a client Modbus device is for the first (40001 Modbus) holding register value (integer). Often
this address works well without an exception response. However, it is recommended that you confirm this ping address, and,
if necessary, change in the device’s property sheet.