Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide - Manual (Page 45)

UniInt Interface User Manual 39
Interface Health Points
There are several different types of points that may be used to monitor the health of an
interface. The first type includes IO rate points, performance points, and Windows
Performance counters. These points represent the traditional older methods for monitoring
the health of an interface. IO rate and performance points are supported by UniInt based
interfaces. The Windows performance counters require the Historian-PerfMon interface in
order to get their values into Historian.
The second type of points is called Interface Health Points. The Interface Health points are
configured in a manner very similar to performance points. UniInt looks at several interface
startup parameters and Historian tag properties to determine if a point is to be loaded as an
Interface Health point. The table below lists the applicable tag attributes, the required value
and a description for each property. Any Historian Tag property not listed in the table is not
applicable to the operation of Interface Health points.
Tag Attribute Value Description
PointSource Equal to /PS from the
interface startup parameters The pointsource property for the tag is not case sensitive
Location1 Equal to /ID from the
interface startup parameters If there is no /ID found in the list of startup parameters,
Location1 must be 0.
Location2 0 Not Used
Location3 Equal to /UFO_ID or
/UHT_ID
from the
interface startup parameters
Only applicable if UniInt failover is being used or if the
/UHT_ID=#
is specified in the list of startup command
parameters. A point with every other property set correctly will
not be loaded by the interface if Location3 is not equal to the
/UFO_ID
parameter or /UHT_ID parameter.
Location4 Specifies the Scan Class to
which this point pertains. Only applicable to Scan Class points, all other Interface Health
points ignore this value.
For monitoring unsolicited IO Rate and Bad Value Rate, Total
Scans Missed or Total Scans Skipped; Location4 must be 0
Exdesc Must contain the proper Key
Word described below Key Word must be the first thing in the exdesc and is case
sensitive.