ACF
- IEEE 1722 Part 2 — ACF (AVTP Control Format): Field-Bus Tunneling over TSN
ACF in the AUTOSAR module IEEE1722Tp: ACF_CAN and ACF_LIN, TSCF vs. NTSCF, bundling multiple field-bus messages, and why it matters for zonal architectures — including a clear boundary against Open1722's broader format scope.
- IEEE 1722 Part 4 — End-to-End Practical Examples with Open1722
Two followable end-to-end examples with Open1722: a camera stream from capture to deterministic delivery, and a CAN subnet transparently tunneled via ACF.CAN over a TSN backbone.
- IEEE 1722 Part 5 — Hands-On Project: ACF-CAN Kernel Module Between Two Real BeagleBone Black Boards
Cross-compiling and loading the Open1722 ACF-CAN kernel module against the Yocto kernel, and testing it between two physical BeagleBone Black boards over Ethernet — real CAN tunneling, no loopback on one machine.
- IEEE 1722 Part 6 — What IEEE 1722-2025 Can Do That AUTOSAR Doesn't (Yet) Define
The full AVTPDU and ACF scope of IEEE 1722-2025 compared to the AUTOSAR module IEEE1722Tp (R24-11): CVF, CAN-XL, FlexRay, MOST, GBB/ABB, GISF, and more — what the standard can do that AUTOSAR doesn't (yet) define.
- IEEE 1722 Part 7 — CAN-XL & CAN-XL Brief: the Most Practically Relevant Gap
ACF_CANXL and ACF_CAN_XL_BRIEF in detail: VCID, SDT, acceptance field, and segmentation — the new header fields from IEEE 1722-2025 that AUTOSAR (R24-11) doesn't yet know.
- IEEE 1722 Part 8 — CAN_V2, CAN_BRIEF_V2 & LIN_V2: More Bus IDs, an Unfinished Format
ACF_CAN_V2 and ACF_CAN_BRIEF_V2 in detail: an 11-bit bus ID instead of 5 bits — and why LIN_V2 so far only exists on paper.
- IEEE 1722 Part 9 — Generic & Abbreviated Byte Bus (GBB/ABB): Tunneling Without a Dedicated Protocol
ACF_GBB and ACF_ABB in detail: the generic request/response format from IEEE 1722-2025 for bus systems without their own ACF format — and why it matters for niche automotive protocols.