docs(loader): record live-values verification + 396/1036 explanation for company overlay
This commit is contained in:
@@ -132,9 +132,18 @@ deploy** endpoint.
|
||||
```bash
|
||||
./.venv/bin/python otopcua_uns.py populate-equipment # 3 areas / 8 lines / 40 equipment / 1036 VirtualTags
|
||||
curl -s -X POST http://localhost:9200/api/deployments -H 'X-Api-Key: docker-dev-deploy-key' # headless deploy
|
||||
./.venv/bin/python otopcua_uns.py verify-equipment --expect 1036 --require-good 1036 --wait --wait-seconds 300 # structure + live values
|
||||
./.venv/bin/python otopcua_uns.py verify-equipment --expect 1036 --require-good 396 --wait --wait-seconds 300 # structure + live values
|
||||
```
|
||||
|
||||
> **Verified live 2026-06-07** (OtOpcUa `feat/equipment-namespace-live-values`): galaxy mirror
|
||||
> **396/396 Good**, company overlay **396 Good** on `opc.tcp://localhost:4840`, `VERIFY-EQUIPMENT: PASS`.
|
||||
> Why 396 of 1036? The shipped `company-uns.json` invents **1036 distinct** `ctx.GetTag` refs, but only
|
||||
> **396** of them match a real galaxy-mirror tag — so 396 signals are backed by a live source (and all 396
|
||||
> go Good); the other 640 cite synthetic refs with no galaxy tag (`BadNodeIdUnknown`). That ratio is a
|
||||
> property of the company model, not the streaming path — **every signal with a resolvable live source
|
||||
> streams Good.** So `--require-good 396` is the meaningful gate for the current model. Survives a node
|
||||
> restart with no re-deploy (the bootstrap-restore path re-materialises + re-applies the VirtualTags).
|
||||
|
||||
UNS folders carry the friendly **DisplayName** (`filling`); the BrowseName/NodeId
|
||||
stay the stable logical Id (`nw-area-filling`) — standard OPC UA. **No driver:** the
|
||||
company signals are VirtualTags (which link to Equipment + a Script, not a driver); a
|
||||
|
||||
Reference in New Issue
Block a user