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

AdminUI /raw driver-create quirks, CLI read throws on Bad, AbCip probe default warning #577

New Issue
Closed
opened 2026-10-07 19:11:03 -04:00 by dohertj2 · 1 comment
dohertj2 commented 2026-10-07 19:11:03 -04:00
Owner
Copy Link
Copy Source

Found during the native AB transport AdminUI live gate (Task 19, branch feat/native-ab-transport); pre-existing.

  • Creating a driver in /raw also creates an empty Device1.
  • The device-name box is pre-filled with Device1, so typing appends (Device1plc1).
  • The first click on the tree after a page load is ignored.
  • Client CLI read throws on a Bad status instead of printing the status code.
  • AbCip form defaults the probe to enabled with no probe tag path, so every new AbCip driver logs a probe warning (newly visible now that AbCip drivers receive the host logger).
Found during the native AB transport AdminUI live gate (Task 19, branch `feat/native-ab-transport`); pre-existing. - [ ] Creating a driver in `/raw` also creates an empty `Device1`. - [ ] The device-name box is pre-filled with `Device1`, so typing appends (`Device1plc1`). - [ ] The first click on the tree after a page load is ignored. - [ ] Client CLI `read` throws on a Bad status instead of printing the status code. - [ ] AbCip form defaults the probe to enabled with no probe tag path, so every new AbCip driver logs a probe warning (newly visible now that AbCip drivers receive the host logger).
dohertj2 added the driver/abcip label 2026-10-07 19:11:03 -04:00
dohertj2 commented 2026-10-08 01:53:53 -04:00
Author
Owner
Copy Link
Copy Source

Fixed: device-name box empty with a placeholder; /raw renders without prerender (first-click fix); CLI read prints the Bad status; a new AbCip driver starts with the probe off. Kept as designed: driver create still auto-creates Device1 (pinned by RawTreeServiceWaveBTests — a product call). Live-verified on docker-dev except the first-click fix, which the hidden automation tab could not prove either way. (merge 7105ef3e on master, pushed 2026-10-08)

Fixed: device-name box empty with a placeholder; /raw renders without prerender (first-click fix); CLI read prints the Bad status; a new AbCip driver starts with the probe off. Kept as designed: driver create still auto-creates Device1 (pinned by RawTreeServiceWaveBTests — a product call). Live-verified on docker-dev except the first-click fix, which the hidden automation tab could not prove either way. (merge `7105ef3e` on master, pushed 2026-10-08)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 cross-driver
queue management
 driver/abcip
queue management
 driver/ablegacy
queue management
 driver/focas
queue management
 driver/mqtt
MQTT / Sparkplug B broker-subscribe driver
 driver/opcuaclient
queue management
 driver/s7
queue management
 driver/twincat
queue management
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
No Label driver/abcip
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#577
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?