dohertj2/scadaproj
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(history): correct vd03 Galaxy-ack note (no Galaxy driver deployed there)

Browse Source
This commit is contained in:
Joseph Doherty
2026-11-12 06:00:30 -05:00
parent 4735913cdc
commit 2e2ce62665
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/skills/sister-project-history/otopcua.md
+2 -2
View File
@@ -470,6 +470,6 @@ Owner-authorised WinRM. Preflight: every blocking check passed; snapshot-isolati
generated on the box; folder swap, ~11 s downtime. First Windows host on OPC UA SDK 2.0.1 (#782). **ScadaBridge-visible
on this box:** FOCAS `Spindle/S1/MaxRpm` → `BadNodeIdUnknown` (renamed `MotorSpeedPct`, tag not re-pointed); macro
`parts-count`/`parts-required` decoded at the right offset; spindle `Load` is a real percent (Float64); unreported program
fields read `BadNoData`. Galaxy acks against the upgraded mxaccessgw `2b13564e` are no longer blocked by the old
OtOpcUa build. The post-deploy AdminUI deploy (drift = re-serialisation only) is left to the owner. Record:
fields read `BadNoData`. (The vd03 ConfigDb has no Galaxy driver — 1 FOCAS driver only — so the earlier note that
its Galaxy acks fail against mxaccessgw `2b13564e` did not apply to this box's deployed config.) The post-deploy AdminUI deploy (drift = re-serialisation only) is left to the owner. Record:
`docs/deploy/vd03-upgrade-b8b4c18f-to-master.md` §(h).