namespace ZB.MOM.WW.OtOpcUa.Driver.Ab.Transport; /// /// Maps wire statuses (CIP general/extended, PCCC STS/EXT STS) to the transport-neutral the /// drivers classify. The class an lands in is load-bearing for driver health (#527/#737/#738): /// an ANSWERED refusal (NotFound / NotAllowed / OutOfBounds / TooLarge / TooSmall / TypeMismatch / /// DeviceStateConflict, and for AbCip Unsupported) proves the device replied; /// is the no-reply comms class; / are a reply that /// cannot be classified. Every code not named below is deliberately . /// public static class AbStatusCodes { /// Maps a CIP general status (and optional extended status words) to an . /// The CIP general status byte. /// The extended status words, if any. /// The mapped status. /// /// 0x01 (connection failure, incl. a routing hop's unconnected-send timeout) and 0x07 (connection lost) stay /// on purpose: a bridge reports a dead END device that way, so they are neither an /// answer nor proof of no reply (AbLegacy #738 "opaque"). A Forward Open refused with one of the request-level /// codes (0x1C / 0x20 / 0xFF-0x2104) stays a connection failure — see /// ConnectionManagerServices.ParseForwardOpenReply. /// public static AbStatus FromCip(byte general, ReadOnlySpan extended) => general switch { 0x00 or 0x0B => AbStatus.Ok, // success / already in requested mode 0x04 or 0x05 or 0x16 => AbStatus.NotFound, // path segment error / path unknown / object does not exist 0x06 => AbStatus.Partial, // partial transfer (fragmented read continues) 0x08 => AbStatus.Unsupported, // service not supported 0x0A => AbStatus.OutOfBounds, // attribute list error 0x0C or 0x10 => AbStatus.DeviceStateConflict, // object state conflict / device state conflict 0x0E or 0x0F => AbStatus.NotAllowed, // attribute not settable / privilege violation 0x13 => AbStatus.TooSmall, // not enough data 0x15 => AbStatus.TooLarge, // too much data // Lane K F1 (#737): the controller answered and refused this one request — not a garbled reply, so not a // comms fault that degrades the driver and evicts the runtime. 0x1C => AbStatus.Unsupported, // missing attribute list entry data 0x20 => AbStatus.Unsupported, // invalid parameter 0xFF when extended.Length > 0 && extended[0] == 0x2104 => AbStatus.OutOfBounds, // offset beyond end of tag 0xFF when extended.Length > 0 && extended[0] == 0x2105 => AbStatus.OutOfBounds, // beyond end of the object 0xFF when extended.Length > 0 && extended[0] == 0x2107 => AbStatus.TypeMismatch, // data type mismatch _ => AbStatus.BadReply, }; /// /// True for the CIP statuses Lane K F1 moved from to a request-level refusal. /// A Forward Open refused with one of them is still a connection failure. /// /// The CIP general status byte. /// The extended status words, if any. /// for 0x1C, 0x20 and 0xFF/0x2104. internal static bool IsRequestLevelRefusal(byte general, ReadOnlySpan extended) => general is 0x1C or 0x20 || (general == 0xFF && extended.Length > 0 && extended[0] == 0x2104); /// Maps a PCCC status byte (and optional extended status) to an . /// The PCCC STS byte. /// The extended status byte, when present. /// The mapped status. /// /// Per the DF1/PCCC STS table (1770-6.5.16). Lane K F3 (AbLegacy F8, review 07 r0 I4): 0x20, 0x30 and 0x90 are /// reported by the HOST or a BRIDGE (a DHRIO, a 1761-NET-ENI) when the END device cannot be reached, so they are /// the no-reply comms class. Mapping them to an answered refusal made a dead DH+/DH-485 node behind a bridge count /// as reachable forever — no fail-fast backoff, no comms-loss watchdog. /// public static AbStatus FromPccc(byte sts, byte? extSts) => sts switch { 0x00 => AbStatus.Ok, 0x10 => AbStatus.Unsupported, // illegal command or format 0x20 => AbStatus.BadConnection, // host has a problem and will not communicate 0x30 => AbStatus.BadConnection, // remote node host missing, disconnected or shut down 0x40 => AbStatus.DeviceStateConflict, // host could not complete: hardware fault 0x50 => AbStatus.NotFound, // addressing problem or memory protect rungs 0x60 => AbStatus.NotAllowed, // function not allowed due to command protection 0x70 => AbStatus.DeviceStateConflict, // processor is in Program mode 0x90 => AbStatus.BadConnection, // remote node cannot buffer command 0xB0 => AbStatus.DeviceStateConflict, // remote node problem due to download 0xF0 when extSts is 0x06 => AbStatus.NotFound, // EXT: address does not point to something usable 0xF0 when extSts is 0x07 => AbStatus.OutOfBounds, // EXT: file is wrong size _ => AbStatus.BadReply, // 0x80, 0xA0, 0xC0, other EXT STS: unclassified }; }