docs(otopcua): record FixedTree-under-Equipment injection feature (design, plan, status)
This commit is contained in:
@@ -67,3 +67,16 @@ returning `Bad_WaitingForInitialData` until the rebuilt `ZB.MOM.WW.OtOpcUa.Drive
|
||||
self-contained host publish) is deployed to `E:\ApiInstall\OtOpcUa\` and `OtOpcUaHost` is restarted. Once
|
||||
redeployed, `parts-count`/`parts-required` should go Good (FixedTree + PMC/Parameter still pending the
|
||||
follow-on v3 command work).
|
||||
|
||||
## FixedTree under the Equipment node (feature built 2026-06-26)
|
||||
|
||||
The FOCAS **FixedTree** (Identity / Axes / Spindle / Program / Timers) now surfaces under the equipment as
|
||||
read-only value nodes, via a generic post-connect `ITagDiscovery` injection feature (branch
|
||||
`feat/focas-fixedtree-equipment-injection`; design + plan at
|
||||
[`docs/plans/2026-06-26-otopcua-fixedtree-equipment-injection-design.md`](../plans/2026-06-26-otopcua-fixedtree-equipment-injection-design.md)
|
||||
and [`…-injection.md`](../plans/2026-06-26-otopcua-fixedtree-equipment-injection.md)). After the driver
|
||||
connects and its `FixedTreeCache` populates (~0–2 s), nodes are grafted at e.g.
|
||||
`ns=2;s=EQ-3686c0272279/FOCAS/Identity/SeriesNumber` and `…/FOCAS/Axes/X/AbsolutePosition`, carrying live
|
||||
values through the same path as the authored `parts-count`/`parts-required` tags, and survive redeploys.
|
||||
**Offline-complete + end-to-end-green; live-validate on the next host deploy** by browsing
|
||||
`ns=2;s=EQ-3686c0272279/FOCAS/…`.
|
||||
|
||||
Reference in New Issue
Block a user