Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Hydrogen Surface Vehicle to Station Communications: Hardware and Software (SAE J2799:2024)
The SAE J2799 standard defines the hardware and software requirements for infrared (IrDA) communication between hydrogen surface vehicles and fueling dispensers. The 2024 revision introduces protocol version 2.00, enabling high-flow fueling (SAE J2601/5) with expanded temperature ranges and structured optional data fields. This article covers key technical updates, hardware geometry, data link protocol, and verification tests essential for reliable and safe hydrogen fueling.
Key Updates in the 2024 Revision
The 2024 edition of J2799 adds a new communication protocol version number 2.00 specifically for high-flow fueling protocols like SAE J2601/5. This version includes a larger temperature variable (TV) range and structured formatting rules in the optional data (OD) field, allowing additional metadata such as station ID and user data to be transmitted without changing the base frame length. The protocol remains backward-compatible with version 01.10, and the vehicle and dispenser negotiate the version implicitly through the fueling protocol context.
Design Insight 🛠️ IrDA communication provides galvanic isolation and tolerance to optical misalignment, critical for safe operation in hydrogen fueling environments. The standard explicitly assumes the communication link itself is not safety-critical (non-ASIL/SIL), shifting system-level safety to other layers. The layered protocol with delimiters, transparency, and frame check sequence (FCS) ensures robust error detection in potentially noisy conditions.
Hardware and Infrared Communication Requirements
The physical layer specifies IrDA transceivers with a wavelength around 850–900 nm, a data rate of 9600 baud, and defined power levels. The geometry of the vehicle transmitter and nozzle receiver is critical for reliable communication. The standard provides minimum and maximum distances between the emitter and receiver for different connector sizes, as summarized in Table 1.
| Connector Size (mm) | Min Distance (mm) | Max Distance (mm) |
|---|---|---|
| 35 | 5 | 25 |
| 50 | 5 | 30 |
| 70 | 5 | 35 |
The vehicle transmitter and nozzle receiver must conform to specific front-view and side-view geometries, as detailed in the standard. The alignment tolerances ensure that the IrDA beam remains within the receiver’s field of view even during mechanical play or connector wear.
Data Link Protocol and Verification Testing
The data link layer uses a standard IrDA framing with opening and closing delimiters (0x7E). A transparency mechanism using an escape byte (0x7D) prevents misinterpretation of delimiters inside the payload. The receiver implements a state machine to handle byte stuffing correctly. The frame includes a 16-bit FCS (CRC-CCITT) for error detection.
Verification testing requires the communication system to correctly receive frames for at least 20 consecutive seconds under defined conditions. Table 2 (from the standard) gives test scenarios including varying distance, offset, and noise. This ensures the link is robust before certification.
Common Mistake ⚠️ Misapplying the transparency mechanism by failing to insert or properly interpret the escape byte (0x7D) can cause frame rejection. Also, using protocol version 01.10 when the station expects 02.00 will cause communication failures, especially for high-flow fueling. Designers must verify version compatibility and implement the full receiver transparency state machine.
Frequently Asked Questions
How is the protocol version negotiated?
Version negotiation is implicit. The dispenser and vehicle agree on a fueling protocol (e.g., from SAE J2601) which determines the communication protocol version. Version 02.00 is used with high-flow protocols and includes a larger TV range; version 01.10 is used for conventional fueling. The frame format remains similar, but the interpretation of some fields (like OD headers) differs.
What is the purpose of the transparency mechanism?
The transparency mechanism avoids misinterpreting byte values that match frame delimiters. The sender inserts the escape byte 0x7D before any 0x7E or 0x7D in the payload. The receiver’s state machine removes the escape and restores the original byte, ensuring robust data integrity over the IrDA link.
What are the verification test requirements for certification?
The system must pass a 20-second verification test where it correctly receives frames with specific timing and content. The test includes scenarios with varying distances, offsets, and background interference, with a target bit error ratio better than 10-4. This is a mandatory step for compliance with standards like CSA HGV 4.3.
Can the same hardware be used for both protocol versions?
Yes, the physical layer and most of the data link layer are identical. The hardware design accommodates both versions. The difference lies in the presentation layer interpretation of the optional data field and temperature variable range. System software must correctly handle the version-specific fields based on the fueling protocol in use.
🔍 For more details, engineers should refer to the full J2799 document and its appendices, which include frame examples, FCS calculation, and historical documentation for version 01.00.
