Documentation PI Nexus+ Documentation

PI Nexus+ / User Guide

PI Adapters

This chapter shows how to check whether the AVEVA PI Adapters (OPC UA, DNP3, Modbus, MQTT and others) are collecting and delivering data.

Overview

This chapter shows how to check whether the AVEVA PI Adapters (OPC UA, DNP3, Modbus, MQTT and others) are collecting and delivering data.

PI Nexus+ does not connect to the adapters. It reads the health data the adapters already publish through OMF into an AF database. The page fills once an administrator has enabled monitoring for that AF database (see PI Adapter Monitoring in the Administration Guide).

Concepts

  • Each row is a Collector: the part of an adapter that reads one data source. Group by service keeps an adapter's Collectors together.
  • Configuration checks PI Nexus+'s own monitoring setup in AF, not the adapter's settings. Not Evaluated means PI Nexus+ does not recognize the AF structure.
  • Data Health rolls up the PI Points the Collector feeds. A point counts only when its OMF data source matches the Collector exactly, so coverage is always partial: Good means every associated point is healthy, not that every stream arrived.
  • Runtime is what the adapter itself publishes: device status and heartbeat, for collection and for each delivery (egress).

Check an adapter collector

Collector dialog with the health cards, a monitoring banner, the Service and Runtime tabs and Check health
  1. Open PI Adapters, click the Runtime or Data Health card to list the Collectors that need attention, and click a row. Read the four cards; the Runtime card names the reason.
  2. Read any banner below the tabs. Enabled; refresh pending means discovery or the first health read has not run yet; a stalled Collector shows Monitoring stalled.
  3. Open Service for the adapter service: version, restart loop or low storage problems, memory, free storage and uptime.
  4. Open Runtime: Collection (device status, heartbeat, I/O and error rate), one Delivery section per OMF egress, Signal details and the latest Runtime transitions.
  5. After a fix, choose Check health to read this Collector's signals once, without an AF inventory scan.

Connections lists the PI Points the Collector feeds; Issues shows its runtime issues and those of its points.

When the Runtime says Unknown

Unknown with Monitoring stalled means no health read succeeded for three poll intervals and at least ten minutes. That usually means the PI Nexus+ Scanner service is stopped or cannot read the AF database, not that the adapter failed. Ask an administrator to check the service and Test AF source.

A Collector whose monitoring is disabled keeps its last evidence and says so.

From a PI Point to its adapter

A PI Point fed by a Collector shows a Data source card on its Overview tab and a PI Adapter node in its Dependency Graph. Both open the Collector.

Reference: PI Adapter Issues and Runtime