About buffered data and history
- Last UpdatedJul 26, 2024
- 1 minute read
When an ApplicationObject starts up, if configured to save historical data, it registers its configuration data with the Historian using a Historian supplied interface.
The following table describes buffered data-enabled history behavior.
|
History function |
Behavior |
|---|---|
|
Buffer Monitoring |
The ApplicationObject monitors and historizes the attribute value. If the attribute being historized has a buffer property, the ApplicationObject monitors the attribute’s buffer instead of its value, and historizes each VTQ in the buffer. |
|
Attribute Registration with the Historian |
Attributes that are buffer-enabled are registered with the Historian in the same manner as non-buffered attributes are registered. |
|
Push Attribute Changes to the Historian |
After successful registration of an attribute with the Historian, the buffer-enabled attribute pushes the data changes to the Historian. If the buffer-enabled attribute reads an empty buffer, and if this is the first scan cycle after the attribute was registered, it gets the attribute’s Value, Time, and Quality properties, and if Quality is Good, sends this VTQ to the Historian. If the buffer-enabled attribute reads an empty buffer, and if this is not the first scan cycle after the attribute was registered, it does nothing. For more information, see Configure historization. |