Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J1939-22 CAN FD Data Link Layer: Design and Implementation Guide
The SAE J1939-22 recommended practice defines the data link layer for J1939 applications using the CAN FD protocol. The 2022 revision focuses on maximizing network bandwidth, supporting functional safety and cybersecurity, improving large data transport, and ensuring AUTOSAR compatibility. This article provides engineers with a practical overview of the standard’s architecture, key protocols, and common design considerations.
Key Updates and Design Goals
The 2022 revision corrects the FD.TP.CM_Abort mechanism to clarify whether the originator or responder session is aborted, and fixes the minimum data size requirement for FD.TP transfers. These corrections are essential for robust connection management. The standard was revised with four primary objectives:
- Maximize Use of CAN FD Network Bandwidth: Leverage larger payloads (up to 64 bytes) and higher data rates.
- Functional Safety and Cybersecurity Support: Integrate safety and security features at the data link layer.
- Improved Large Data Transport Services: Introduce segmented transport with efficient control.
- AUTOSAR Compatibility: Align with automotive software architecture standards.
🛠️ Design Insight: To fully exploit CAN FD bandwidth, design your system to pack multiple parameter groups using the Multi-PG protocol. This reduces arbitration overhead and increases effective throughput for high-rate data.
Data Link Layer Architecture and Transport Mechanisms
The data link layer defines Application Protocol Data Units (A_PDU) and Datalink Layer Protocol Data Units (D_PDU) that map to CAN FD frames. Two D_PDU formats are specified for different identifier schemes:
| D_PDU Format | Identifier Length | CAN FD Base | Typical Application |
|---|---|---|---|
| FEFF | 29-bit (extended) | Extended Frame Format | Multi-network routing with Parameter Groups |
| FBFF | 11-bit (standard) | Base Frame Format | Local networks with limited address space |
The Multi-PG protocol allows a single D_PDU to carry multiple parameter groups (C-PGs), significantly improving bus utilization. For large data transfers, the FD Transport Protocol (FD.TP) provides segmented transmission with connection management via FD.TP.CM and FD.TP.DT messages. The protocol ensures data integrity and flow control across the network.
⚠️ Common Mistakes to Avoid:
- Using FD.TP.CM_Abort without specifying whether to abort the originator or responder session.
- Not respecting the corrected minimum data size for FD.TP transfers.
- Errors in packing C-PGs into Multi-PG frames, leading to incorrect interpretation at the receiver.
- Misapplication of A_PDU1 vs A_PDU2 formats for routing, which can cause addressing errors.
Frequently Asked Questions
1. How does the Multi-PG protocol increase network efficiency?
By combining multiple parameter groups into a single CAN FD frame, the Multi-PG protocol reduces the number of arbitration events and header overhead. This is especially beneficial for periodic messages from a single source.
2. What are the main differences between A_PDU1 and A_PDU2?
A_PDU1 includes a specific destination address for point-to-point communication, while A_PDU2 is used for global broadcasts. Both carry the Parameter Group Number (PGN) to identify the data content.
3. How does the standard support functional safety?
The data link layer incorporates features such as data integrity checks and redundancy mechanisms that can be used by higher-layer safety protocols to meet functional safety requirements.
4. Can legacy J1939 devices coexist with J1939-22 CAN FD devices?
Yes, the standard is designed for AUTOSAR compatibility and allows gateways to bridge classical CAN and CAN FD segments, enabling a phased migration.
