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:
Joseph Doherty
2026-03-17 18:25:39 -04:00
parent adc1af9f16
commit 775cb8084f
6 changed files with 76 additions and 6 deletions

View File

@@ -54,7 +54,7 @@ Additional protocols can be added by implementing this interface.
### Common Value Type
Both protocols produce the same value tuple consumed by Instance Actors:
Both protocols produce the same value tuple consumed by Instance Actors. Before the first value update arrives from the DCL, data-sourced attributes are held at **uncertain** quality by the Instance Actor (see Site Runtime — Initialization):
| Concept | ScadaLink Design | LmxProxy SDK (`Vtq`) |
|---|---|---|