Use bracketless OPC UA node IDs for arrays

service_info.md

@@ -0,0 +1,51 @@
+# Service Update Summary
+
+Updated service instance: `C:\publish\lmxopcua\instance1`
+
+Update time: `2026-03-25 12:54-12:55 America/New_York`
+
+Backup created before deploy: `C:\publish\lmxopcua\backups\20260325-125444`
+
+Configuration preserved:
+- `C:\publish\lmxopcua\instance1\appsettings.json` was not overwritten.
+
+Deployed binary:
+- `C:\publish\lmxopcua\instance1\ZB.MOM.WW.LmxOpcUa.Host.exe`
+- Last write time: `2026-03-25 12:53:58`
+- Size: `143360`
+
+Windows service:
+- Name: `LmxOpcUa`
+- Display name: `LMX OPC UA Server`
+- Account: `LocalSystem`
+- Status after update: `Running`
+- Process ID after restart: `29236`
+
+Restart evidence:
+- Service log file: `C:\publish\lmxopcua\instance1\logs\lmxopcua-20260325_004.log`
+- Last startup line: `2026-03-25 12:55:08.619 -04:00 [INF] The LmxOpcUa service was started.`
+
+## CLI Verification
+
+Endpoint from deployed config:
+- `opc.tcp://localhost:4840/LmxOpcUa`
+
+CLI used:
+- `C:\Users\dohertj2\Desktop\lmxopcua\tools\opcuacli-dotnet\bin\Debug\net10.0\opcuacli-dotnet.exe`
+
+Commands run:
+
+```powershell
+opcuacli-dotnet.exe connect -u opc.tcp://localhost:4840/LmxOpcUa
+opcuacli-dotnet.exe read -u opc.tcp://localhost:4840/LmxOpcUa -n 'ns=1;s=MESReceiver_001.MoveInPartNumbers'
+opcuacli-dotnet.exe read -u opc.tcp://localhost:4840/LmxOpcUa -n 'ns=1;s=MESReceiver_001.MoveInPartNumbers[]'
+```
+
+Observed results:
+- `connect`: succeeded, server reported as `LmxOpcUa`.
+- `read ns=1;s=MESReceiver_001.MoveInPartNumbers`: succeeded with good status `0x00000000`.
+- `read ns=1;s=MESReceiver_001.MoveInPartNumbers[]`: failed with `BadNodeIdUnknown` (`0x80340000`).
+
+## Notes
+
+The service deployment and restart succeeded. The live CLI checks confirm the endpoint is reachable and that the array node identifier has changed to the bracketless form. The array value on the live service still prints as blank even though the status is good, so if this environment should have populated `MoveInPartNumbers`, the runtime data path still needs follow-up investigation.