[ISS Support Case] Archestra Modbus Connection
Last updated: October 17th, 2025Description
The customer is attempting to configure a Modbus TCP connection within AVEVA System Platform (2017 U2). They confirmed that communication with the controller works via an external Modbus scanner, but are unable to successfully read data into the IDE (Integrated Development Environment) using existing ModbusEnetBridge-based configuration. Customer reported that scan groups were configured, but object attributes in Object Viewer are showing bad quality. Customer indicated that their integrator mentioned this setup is based on an "older style" of Modbus communication, with plans to modernize the architecture within the next six months. They are currently troubleshooting within the IDE directly, not via the System Management Console (SMC) or using the more modern OI Server configuration. A follow-up session was scheduled to further investigate the system live and collect diagnostic information, including logs. Key Details: Customer can communicate with controller using a standalone Modbus scanner. Unsure how to replicate the same communication inside Wonderware IDE. Using "ModbusEnetBridge" object in the IDE (legacy communication structure). Unable to read data into Object Viewer quality shows bad or invalid. Scan groups are configured but not reading expected data. Communication and object configuration appear legacy; planned upgrade may affect architecture. As part of the initial troubleshooting efforts, a test was conducted using WWClient to validate communication with the Modbus server. Objective: To verify if data can be manually polled from the Modbus device using a known-good test client (WWClient), bypassing object configuration in the IDE. Procedure: WWClient was launched on the system where System Platform is installed. An attempt was made to connect to the device using the known Modbus address and tag syntax consistent with the ModbusEnetBridge configuration. A tag read request was issued targeting a known Modbus register expected to return live data. Outcome: The attempt was unsuccessful. WWClient returned a hexadecimal error code: 0x01D67028. This error indicates that the client was unable to complete the request successfully potentially due to: Incorrect syntax in the item name Communication layer issue between the client and the OI Server/Bridge Misconfiguration in the ModbusEnetBridge object or associated scan group IP/Port mismatch or port being blocked Notes: This result further confirms that the issue is not isolated to the IDE configuration but may be systemic to the communication path or ModbusEnetBridge setup.
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
| Product: DA OI Servers |
| Version: 4.0 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 05/30/2025 |
| Case: | 98017 |
Give feedback about this article
Recommended articles
[ISS Support Case] TI 500 - Disconnected Post CDP 2023 R2 P01
Upgraded to 2023 R2 P01 experienced a disconnect at 8am this morning. Describes loaded log file. Seems like this happened once before shrugged it off Firmware 1.27 South parkway WWTP
Read More[ISS Support Case] OI Gateway Servers disconnecting every 7 minutes
They stay offline for about 2 minutes then they reconnect. They don't see any reconnect scripts that could cause it. They are waiting to reboot until they have a good opportunity. System platform 2020R2 SP1 They recently migrated to a new server. Suggested it may be a firewall or security program interfering with the connection. They will check with the IT department about that. Not available until the afternoon on 9/6/2024
Read More[ISS Support Case] Professional license required
Were creating a new instance of the OI server the error, professional license required as displayed
Read More[ISS Support Case] Failure to Create Additional MBTCP Server Instance
Client reached out as when user was attempting to create additional MBTCP server instance they received the following error message: "Multi-Instance configuration is only supported with a professional level license or higher. Please upgrade the license to create additional instance's." Client also had the following error in the logger: "LicAPISvcProxy.NET failed to communicate with Aveva Enterprise License product service."
Read More