MTConnect: decide per-/raw-Device routing (client per device vs DraftValidator error) #628
Assignees
dohertj2 (dohertj2)
Clear assignees
dohertj2 (dohertj2)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: dohertj2/lmxopcua#628
Reference in New Issue
Block a user
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?
Split from #613 (decision item). The MTConnect driver ignores
RawTagEntry.DeviceName: all raw tags bind through one agent client regardless of the /raw Device they sit under. #613's slice added a loud warning when a DeviceName is set, but the actual behaviour needs a decision.Sources: docs/drivers/MTConnect.md;
MTConnectDriver.cs(ignored-DeviceName warning).Options to decide between:
(a) one agent client per /raw Device (Device row carries agent base URL + MTConnect device name)
(b) keep a single client per driver and make a Device-scoped tag a deploy-time
DraftValidatorerrorChoose (a) or (b) and record it in docs/drivers/MTConnect.md
Implement it (routing, or the validator rule + authoring-time message in the tag editor)
Tests, including multi-device agents and the existing single-device configs staying valid
Filed 2026-10-08 by the hardware-available issue sweep.
Fixed in
723392e3(Merge b626-mtconnect): one MTConnect driver = one agent client = at most one /raw Device. A second is a deploy error (MTConnectMultipleDevices) and RawTreeService.CreateDeviceAsync refuses it.