AbLegacy native: prove PLC-5 writes and non-N-file reads on real hardware (R07:U6) #752
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?
Native PCCC on PLC-5 is limited by design until there is hardware proof:
Plc5WriteVerified = false(Ab.Transport/Pccc/PcccServices.cs:16-19), so every PLC-5 write is refused, reads are N-file only, and sub-elements are refused. Each surfaces asBadNotSupportedwith no health impact (#571). Review finding R07:U6 and the remediation plan (Lane AbLegacy, #738) call for a hardware follow-up issue to record this gap; none was filed.Work (needs a real PLC-5):
Plc5WriteVerifiedand widen the native file set with tests.The
logixpcccpath is in the same position. #592 covers SLC/MicroLogix native evidence and the libplctag-deletion decision, which depends on this.Source: docs/reviews/2026-10-21/07-drivers-plc.md:83 (U6); docs/superpowers/plans/2026-10-22-review-remediation.md:338; docs/drivers/AbLegacy.md §Native known gaps. Related: #592, #571, #738.