Search FAQs

{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}

Data Center Expert | Discovering a ModbusTCP device

Process to discover a Modbus TCP device into StruxureWare Data Center Expert.

Product Line
StruxureWare Data Center Expert (DCE)
- Basic Appliance (AP9465)
- Standard Appliance (AP9470)
- Enterprise Appliance (AP9475)
- Virtual Appliance (AP94VMACT)
StruxureWare Central (SWC)
InfraStruXure Central (ISXC)

StruxureWare Data Center Expert (all versions)
Third Party device supporting ModbusTCP
APC device only supporting ModbusTCP


See additional knowledge bases for discovering different other types of devices:
- APC Device: SNMPv1
- APC Device: SNMPv3
- NetBotz 200 Series
- NetBotz 300-500 Series
- NetBotz 700 Series
- Third Party devices using SNMP
- BACnet is currently not supported

1) Log into the DCE Desktop Client using an Administrator account.

2) Device menu > Add Devices...

3) Select Modbus TCP > Next.

4) Enter the IP Address of the Modbus TCP device.

5) Select a compatible Device Type from the list.
NOTE: If you device is not listed, you will need to obtain a Device Definition File (DDF) and add it to DCE before continuing.  For instructions see knowledge base FA290458.

6) Select the Server Address.
NOTE: This Server address is defined within the end-device.

7) Enter the Modbus TCP port and click Next.
NOTE: The default port is 502, but your device or security team may require the use of an alternative port.

8) Choose a device group to discover the device into and click Finish.

9) Navigate to the Monitoring Perspective and click on the device group that you discovered the device into.

10) Within the Device View pane, search for the IP Address of the device.

STOP! If the device is still trying to discover the Type will be "Modbus TCP Device" and the status will say "Initializing..."  Wait until the status changes to proceed to the next step.

11) Newly discovered Modbus TCP devices will show a status of Normal when first discovered.  You can verify the sensors that are being polled by right-click on the device within the Device View pane and select View Device Sensors...  If the device shows a status of Failure, proceed to the Troubleshooting Failed Modbus TCP Discovery section.

Troubleshooting Failed Modbus TCP Discovery

Failed device discoveries will have a status of failure, as shown within: Monitoring Perspective > Device View pane.  Follow the steps below to try to correct the discovery issues.

1) Verify the following information from the device side:
- IP Address
- Server Address
- Modbus TCP Port

2) Verify the information is entered correctly for the device within: DCE Desktop Client > Device menu > Modbus Device Communication Settings > Device Scan Settings > Check the box for the line that has the IP/Server Address of the discovered Device > Edit Device Scan Settings.  Click OK to save any changes.
NOTE: If you selected the wrong Device Type within DCE during discovery, you will need to delete the device and create a new discovery, ensuring to select the correct device type.

STOP! If any changes were made, perform the following: DCE Desktop Client > Monitoring Perspective > Select Device Group with discovered device > Device View pane > Right-click on the device > Request Device Scan.  Wait for 1 minute to see if the status changes to Normal.

3) Obtain the Modbus map from the device manufacturer.  The Modbus map displays the register values that DCE would need to be configured to poll using the DDF file.

4) Use the Schneider Electric Modbus Tester application to ensure that registers and values can be polled from the Modbus TCP device.  Application download and instructions for use can be found in knowledge base FA180037.
NOTE: This step is to ensure that the device is responding to requests with the proper settings.

5) If the Device responds to the register value requests using the application, the issue is either setting related or DDF related.  Since the Modbus TCP settings were re-verified in the previous steps, the issue is likely DDF related.  There may be alternative DDFs for the device manufacturer or specific device model. NOTE: There may be alternative DDFs depending on the devices firmware version.

For instructions on searching for and obtaining DDF files, see knowledge base FA290458.
NOTE: If you locate another DDF that you wish to try, you will need to add the DDF to DCE and then delete and rediscover the device using the new Device Type within the discovery screen.

6) If there is a specific DDF for your device model and it is not working, you can raise a question on the Community or contact local technical support.
If there is no specific DDF for your device model, follow the instructions in knowledge base FA290458 for submitting a DDF request.

APC Latvia

Did this answer your question?

Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.