TwinCAT: porting backlog from the stranded auto/driver-gaps branch (4 items, #607) #637
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?
Porting backlog for the TwinCAT driver, from the #607 branch ledger (
docs/plans/2026-10-08-driver-gaps-branch-ledger.md). These issues were auto-closed against PRs merged intoauto/driver-gaps, which never reached master (and predates v3). Each item below was classified STRANDED: no equivalent on master (symbol/file grep plus docs), so the work needs a port-or-drop decision. The branch commit is listed per item (git show <sha>onorigin/auto/driver-gaps); the branch is a design reference, not a cherry-pick, because the driver and the address-space model were rewritten since.Recommendation: DROP #316 (TC3 EventLogger IAlarmSource; the branch was a gated scaffold). #306 touches Core
DriverDataTypeand the node manager; #310 and #314 need an ADS router/hardware to verify.Source: #607; ledger rows for the original issue numbers below.
Port-or-drop checklist (4 items; effort S/M/L from the ledger):
80b2d7f8). TIME/DATE/DT/TOD map to UInt32 (TwinCATDataTypeExtensions.cs:26); branch adds native DriverDataType/UA types / Port risk: Medium: touches Core DriverDataType + node manager931049b5). No ADS sum-read/sum-write / Port risk: Medium: hardware/ADS router to verify24a3cda5). No TwinCATDeviceDiagnostics (cycle/jitter/PLC state); only probe ReadState / Port risk: Medium; synthetic tagsc88e0b6b). No TC3 EventLogger IAlarmSource (branch was gated scaffold) / Port risk: Medium; recommend DROPFiled 2026-10-08 by the hardware-available issue sweep.
Triage: #306 ported (TIME/TOD -> Float64 ms, DATE/DT -> UTC DateTime;
b7b9a57bMerge b626-twincat). #316 dropped (low value). #310 and #314 need real TwinCAT hardware -> filed as #645. Closing in favour of #645.