feat: data-sourced attributes start with uncertain quality before first DCL value
Attributes bound to data connections now initialize with "Uncertain" quality, distinguishing "never received a value" from "known good" or "connection lost." Quality is tracked per attribute and included in GetAttributeResponse.
This commit is contained in:
@@ -87,9 +87,10 @@ Deployment Manager Singleton (Cluster Singleton)
|
||||
|
||||
### Initialization
|
||||
1. Load all attribute values from the flattened configuration (static defaults).
|
||||
2. Register data source references with the Data Connection Layer for subscriptions.
|
||||
3. Create child Script Actors (one per script defined on the instance).
|
||||
4. Create child Alarm Actors (one per alarm defined on the instance).
|
||||
2. Set quality to **uncertain** for all attributes that have a data source reference. Static attributes (no data source reference) have quality **good**. The uncertain quality persists until the first value update arrives from the Data Connection Layer, distinguishing "not yet received" from "known good" or "connection lost."
|
||||
3. Register data source references with the Data Connection Layer for subscriptions.
|
||||
4. Create child Script Actors (one per script defined on the instance).
|
||||
5. Create child Alarm Actors (one per alarm defined on the instance).
|
||||
|
||||
### Attribute Value Updates
|
||||
- Receives tag value updates from the Data Connection Layer for attributes with data source references.
|
||||
|
||||
Reference in New Issue
Block a user