PI Nexus+ / Reference
PI Point Issues
This reference lists the issues PI Nexus+ raises for PI Points and PointSources, the PI Point health states, and the rule defaults behind them. The User Guide chapters PI Points and Point Sources link here.
Overview
This reference lists the issues PI Nexus+ raises for PI Points and PointSources, the PI Point health states, and the rule defaults behind them. The User Guide chapters PI Points and Point Sources link here.
PI Point health states
| State | Meaning |
|---|---|
| Good | Every enabled check passed |
| Warning | At least one finding at Warning severity, none at Error |
| Bad | At least one finding at Error severity |
| Unknown | The rule checks quality, but the quality could not be determined (Unknown Quality), or the current value could not be read for a new point (Current Value Unavailable) |
| Not Evaluated | The point is inventoried, but its rule skips evaluation |
A failed value read is not treated as evidence: a point that already has health keeps it until a read succeeds.
The reason shown for Bad or Warning is the first finding in this order: attribute check at Error, bad value, stale, frozen, out of range, attribute check at Warning.
PI Point issues
All appear on the Issues page under the category PI Points (interface mapping issues: see PI Interface Issues and Runtime). Severities marked rule come from the matched PI Point Rule; see PI Point Rule defaults below.
| Issue | Severity | Raised when | Typical fix |
|---|---|---|---|
| PI Point With No Data | Rule (default Warning) | The current value is the system state No Data | Check the interface or adapter that feeds the point |
| Uninitialized PI Point | Rule (default Warning) | The current value is Pt Created: the point never received a first value | Start the data flow, or delete an unused point |
| Bad PI Point Value | Rule (default Error) | The current value has bad quality. Specific states get their own name: PI Point Collection Timeout (I/O or scan timeout), PI Point Access Denied, PI Point Source Shutdown, PI Point Requires Configuration, PI Point Calculation Failed, PI Point Calculation Disabled, PI Point Scanning Disabled, PI Point Scan State Warning | Check the source device, the interface and the point configuration |
| Stale PI Point | Rule (default off) | The newest value is older than the rule's stale threshold (default 30 days) | Check whether the source still writes; retire the point if not |
| Frozen PI Point | Rule (default off) | A numeric point (Float16, Float32, Float64, Int16, Int32) keeps receiving values, but none moved beyond the point's exception deviation for the frozen threshold (default 24 hours). Evaluated by health refresh scans and Check health, not by inventory scans | Check the sensor or field signal |
| PI Point Out of Range | Rule (default off) | A good numeric value is outside zero to zero + span | Correct zero and span, or check the instrument |
| Attribute check name, for example Compressing | Per check (default Warning) | A PI Point attribute does not meet a check defined in the rule | Correct the point attribute, or the rule |
| **Duplicate Source Mapping: PointSource - *InstrumentTag*** | Warning | More than one active point shares the same PointSource and InstrumentTag | Remove or correct the duplicate point |
| Multiple analysis writers | Error | More than one AF analysis is configured to write to the point | Keep one writing analysis |
| Conflicting PI Point writers | Error | A PI Interface or PI Adapter Collector writes the point, and an AF analysis or the other collector kind also writes it | Keep one writer; move the analysis output to its own point |
PointSource issue
| Issue | Severity | Raised when | Resolves when |
|---|---|---|---|
| PointSource Without Collector | Warning | A PointSource on an archive has active PI Points, and no PI Interface, PI Adapter Collector or inbound External System feeds it, and no purpose is declared | A feeder is found, or an administrator declares a purpose |
No warning is raised when the feeder is Feeder unknown: the archive's interface inventory is not available because Interface Tracking is off, has not run or failed.
Fed by values
| Value | Meaning |
|---|---|
| PI Interface / PI Adapter | An interface or Collector claims the PointSource. Both appear during a migration |
| External System | Every point on it belongs to a PI Point Rule linked to an inbound External System |
| Declared purpose | Manual / data entry, Analysis outputs, Custom application or Not used |
| No collector | Nothing found; raises PointSource Without Collector |
| Feeder unknown | Interface inventory not available for the archive |
PI Point Rule defaults
Set per rule by an administrator (PI Point Rules in the Administration Guide).
| Check | Enabled by default | Default severity | Threshold |
|---|---|---|---|
| Inventory | Yes | ||
| Quality: No Data | Yes | Warning | |
| Quality: Pt Created | Yes | Warning | |
| Quality: other bad values | Yes | Error | |
| Stale | No | Ignored | 30 days |
| Frozen | No | Ignored | 24 hours |
| Range (zero/span) | No | Ignored | |
| Attribute checks | Per check | Warning |
