This example is included to illustrate stepped data. For the purposes of Historian 3 examples consider a source historian with the following data:
|
Timestamp |
Value |
StatusCode |
Notes |
|
12:00:00 |
- |
Bad_NoData |
First archive entry, Point created |
|
12:00:02 |
10 |
Raw, Good |
|
|
12:00:25 |
20 |
Raw, Good |
|
|
12:00:28 |
25 |
Raw, Good |
|
|
12:00:39 |
30 |
Raw, Good |
|
|
12:00:42 |
- |
Raw, Bad |
Bad quality data received, Bad data entered |
|
12:00:48 |
40 |
Raw, Good |
Received Good StatusCode value |
|
12:00:52 |
50 |
Raw, Good |
|
|
12:01:12 |
60 |
Raw, Good |
|
|
12:01:17 |
70 |
Raw, Uncertain |
Value is flagged as questionable |
|
12:01:23 |
70 |
Raw, Good |
|
|
12:01:26 |
80 |
Raw, Good |
|
|
12:01:30 |
90 |
Raw, Good |
|
|
|
- |
No Data |
No more entries, awaiting next Value |
Figure 8 – Example Data for Historian 3
For the purposes of all Historian 3 examples:
- TreatUncertainAsBad = True. Therefore Uncertain values are treated as Bad, and not included in the Aggregate call.
- Stepped Attribute = True. Therefore SteppedInterpolation is used between data points.
- UseSlopedExtrapolation = False. Therefore SteppedExtrapolation is used at end boundary conditions.
- PercentBad = 50, PercentGood = 50. Therefore data will be either Good or Bad quality. Uncertain should not happen since a value is either Good or Bad.