Rockwell Automation FactoryTalk Historian SE 3.0 H2H Interface User Guide - Manual (Page 131)

FactoryTalk Historian To Historian Interface User Guide 125
received a new value within the Stale Period then the point will move from the Good count to
the Stale count. Only points that are Good can become Stale. If the point is in the In Error
count then it will remain in the In Error count until the error clears. As stated above, the total
count of Points Good, Points In Error and Points Stale will match the Point Count for the
interface.
“Points Stale 30(min)” (.Points_Stale_30min)
The .Points_Stale_30min Performance Counters Point indicates the number of points that
have not received a new value in the last 30 minutes. For a point to be in the Stale 30 minute
count it must also be a part of the Stale 10 minute count.
“Points Stale 60(min)” (.Points_Stale_60min)
The .Points_Stale_30min Performance Counters Point indicates the number of points that
have not received a new value in the last 60 minutes. For a point to be in the Stale 60 minute
count it must also be a part of the Stale 10 minute and 30 minute count.
“Points Stale 240(min)” (.Points_Stale_240min)
The .Points_Stale_240min Performance Counters Point indicates the number of points that
have not received a new value in the last 240 minutes. For a point to be in the Stale 240
minute count it must also be a part of the Stale 10 minute, 30 minute and 60 minute count.
Performance Counters for (Scan Class x) only
“Device Scan Time (milliseconds)” (.Device_Scan_Time)
A .Device_Scan_Time Performance Counter Point is available for each Scan Class of this
Interface.
The .Device_Scan_Time Performance Counters Point indicates the number of milliseconds
the interface takes to read the data from the foreign device and package the data to send to
Historian. This counter does not include the amount of time to send the data to Historian.
This point is similar to the [UI_SCINDEVSCANTIME] Health Point.
The ICU uses a naming convention such that the tag containing “(Scan Class 1)” (for
example, “
sy.perf.etamp390.E1 (Scan Class 1).device_scan _time ” refers to
Scan Class 1, “(Scan Class 2) refers to Scan Class 2, and so on.
“Scan Time (milliseconds)” (.scan_time)
A .scan_time Performance Counter Point is available for each Scan Class of this Interface.
The .scan_time Performance Counter Point indicates the number of milliseconds the interface
takes to both read the data from the device and send the data to Historian.
This point is
similar to the [UI_SCINSCANTIME] Health Point.
The ICU uses a naming convention such that the tag containing “(Scan Class 1)” (for
example, “
sy.perf.etamp390.E1(Scan Class 1).scan_time” refers to Scan Class 1,
“(Scan Class 2)” refers to Scan Class 2, and so on.