PI AF structure for HART-IP data

The PI AF elements and attributes for PI Connector for HART-IP can be viewed using PI System Explorer.

There are two HART gateway and sub-device naming conventions that can be applied to the PI AF model created by the connector depending on the mode selected in the data source configuration. The default model, uses a combination of the device Long Tag and Unique Address. The second model uses just the device Long Tag. In the following examples, the each HART gateway is shown in the PI AF model.

HART gateway PI AF element

The following is the default naming convention showing the use of the Long Tag and Unique Address to name the Emerson1410-0674910 (264E 0D1B2A) HART gateway.

The following HART gateway PI AF model, shows the use of the Long Tag naming convention used to name the Emerson1410-0674886 HART gateway.

Regardless of the naming convention used, the PI AF element representing the HART gateway contains attributes received from Command 0 and Command 74 responses as well as real-time measurements related to dynamic and device variables.

An example of the HART gateway PI AF element is shown below.

Data quality for device statuses

The following is the default naming convention showing the use of the Long Tag and Unique Address to name the PT-5357-1 (2664 1E8EA2) HART sub-device. The HART sub-device is placed under the Rosemount 2051 Wireless sub-device type PI AF element. All HART sub-devices are placed under a PI AF element representing the device manufacturer and device type.

The following HART sub-device shows the use of the Long Tag naming convention used to name the 708 #4014 HART sub-device. The HART sub-device is placed under the Rosemount 70 Wireless Acoustic sub-device type PI AF element. As stated above, all HART sub-devices are placed under a PI AF element representing the device manufacturer and device type.

The PI AF element representing the HART sub-device contains attributes received from Command 0 and Command 84 responses as well as real-time measurements related to dynamic and device variables.

An example of the HART sub-device PI AF element is shown below.

All the device status are updated to provide data quality in particular scenarios. However, the measurements persist their last known value.

When data collection for the connector is stopped, the device statuses are updated to Not Connect.

Note: The dynamic and device variable measurements, such as PV, SV, TV, QV, Battery Life, and Percent Range, maintain the last sent value and are not updated with Not Connect.

When the connector determines that a device is not reachable, device statuses are updated to Comm Fail.

Note: The dynamic and device variable measurements, such as PV, SV, TV, QV, Battery Life, and Percent Range, maintain the last sent value and are not updated with Comm Fail.

Loop Current attributes

Loop current attributes are not collected for wireless devices, and for non-wireless devices that are not an Adapter Device Type.