Manage the Modbus TCP adapter

AVEVA adapters produce various types of health and diagnostics data. While most of the data is dynamic and created as streams or PI points, there are some static data that can be used to create a hierarchy on a PI AF Server.

For details around the different health and diagnostics data available to you, see the following:

• Health

• Diagnostics

Available health endpoints

Three OMF endpoints are currently supported for adapter health data:

• Edge Data Store 2023 SP1 and forward

• CONNECT data services

• PI Web API

There are a few differences in how these systems treat the associated health and diagnostics data.

1. Edge Data Store and CONNECT data services do not currently provide a way to store the static metadata. For these endpoints, only dynamic data is stored, and each value is its own stream with the timestamp property as the single index.

2. PI Web API parses the information and sends it to configured AVEVA PI Servers for the OMF endpoint. Dynamic health data is time-series data stored in PI points on a PI Data Archive. You can see it in the AF hierarchy as PI point data reference attributes. The static data is used to create a hierarchy on a PI AF server, similar to the AF structure example below.

AF structure

With a health endpoint configured to an AVEVA PI Server, you can use PI Server Explorer to view the health and diagnostics of an adapter. The element hierarchy is shown in the following image.

• The Elements root contains a link to an Adapters node. This is the root node for all adapter instances.

• Below Adapters, you will find one or more adapter nodes. Each node's title is defined by the node's corresponding computer name and service name in this format: {ComputerName}.{ServiceName}. For example, in the following image, ADPTRTSTWIN01 is the computer name and BACnetAdapter1 is the service name.

• To see the health and diagnostics values, select an adapter node and then select Attributes.