Module tree 

A frame decoded into a tree of fields, each with the octets it came from: the capture screen’s decode tree, and the range its hex view highlights for the selected field.

Only the frame the user selects is decoded this far. Offsets come from the codecs’ own views where they give them (the BVLL and NPDU slices, the NPDU’s payload_offset) and otherwise from the fixed layout of each header: Clause 9.3 for MS/TP, Annex J.2 and U.2 for the BVLLs, Annex AB.2 for BVLC-SC, Clause 6.2 for the NPCI and Clause 20.1 for the APDU headers. The common services’ parameters are named field by field (service); any other’s, and any a decoder refuses, are walked tag by tag (Clause 20.2).

Structs

Field

One decoded field.

Functions

decode_apdu_tree

An APDU given on its own, decoded into its fields: the header, then the service parameters, named field by field for the common services and otherwise tag by tag. Ranges are offsets in apdu.

decode_npdu_tree

An NPDU given without its link, decoded into its fields: the NPCI, then a network message or the APDU. Ranges are offsets in npdu.

decode_tree

Decode frame into its fields, link layer first.