MTConnect P1.5: CONDITION as Part 9 alarms, TIME_SERIES arrays, EVENT enumerations, DataType validation #613
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?
The design's P1.5 fast-follow is unbuilt: CONDITION surfaces as plain String; TIME_SERIES and DATA_SET/TABLE as
BadNotSupported; EVENT vocabularies aren't enumerations; a raw tag's DataType is never validated against observation coercion.Sources: docs/drivers/MTConnect.md:366-443; MTConnectObservationIndex.cs:53,272.
IAlarmSource(Galaxy native-alarm pattern)/probeinference/raw-Device routing (RawTagEntry.DeviceNameignored today)Filed 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep.
Partial on master; left open. Slice 1 landed (
b78c7ff9, merge33d72edc).MTConnectTagConfigModel) advises when a raw tag's DataType disagrees with the observation's inferred type, and the driver logs it (MTConnectTagConfigModelTests,MTConnectRawTagBindingTests); docs/drivers/MTConnect.md updated.RawTagEntry.DeviceNamenow produces a loud warning. The actual routing decision remains open and is tracked in its own issue.Progress 2026-10-08 by the hardware-available issue sweep (master
d898262c); left open for the remaining items.Tracker closed. MTConnect P1.5: CONDITION (#626), TIME_SERIES (#627) and per-device routing (#628) landed; feature-status table added to docs/drivers/MTConnect.md (
9244ae2c). EVENT enumerations + DATA_SET/TABLE moved to #650.