Troubleshoot the Modbus TCP adapter

AVEVA Adapter for Modbus TCP provides troubleshooting features that enable you to verify adapter configuration, confirm connectivity, and view message logs. If you are unable to resolve issues with the adapter or need additional guidance, contact AVEVA Technical Support through the AVEVA Customer Portal.

Simulators

Download an online Modbus simulator as a data source to troubleshoot the adapter. For example, Mod_RSSim.

ASP .NET Core platform log

The ASP .NET Core platform log provides information from the Kestrel web server that hosts the application. The log could contain information that the adapter is overloaded with incoming data. Perform the following steps to spread the load among multiple adapters:

1. Decrease the scan frequency.

2. Lower the amount of data selection items.

Wireshark

Wireshark is a protocol-specific troubleshooting tool that supports all current adapter protocols. Perform the following steps if you want to use Wireshark to capture traffic from the data source to the adapter or from the adapter to the OMF destination.

1. Download Wireshark.

2. Familiarize yourself with the tool and read the Wireshark user guide.

Health and diagnostics egress to PI Web API

The adapter sends health and diagnostics data to PI Web API; in some cases, conflicts may occur that are due to changes or perceived changes in PI Web API. For example, a 409 - Conflict error message displays if you upgrade your adapter version and the PI points do not match in the upgraded version. However, data is continued to be sent as long as containers are created, so buffering only starts if no containers are created.

To resolve the conflict, perform the following steps:

1. Stop the adapter.

2. Delete the Health folder inside of the Buffers folder.

3. Stop PI Web API.

4. Delete the relevant adapter created AF structure.

5. Delete the associated health and diagnostics PI points on any or all PI Data Archives created by PI Web API.

6. Start PI Web API.

7. Start the adapter.