Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
A Vehicle Network Protocol with a Fault Tolerant Multiplex Signal Bus (SAE J1813)
The SAE J1813 standard, issued in August 1987, describes a Vehicle Network Protocol (VNP) designed to serve all vehicle communication applications that can tolerate a latency of at least 20 milliseconds when operating at a bus speed of 10 Kbit/s. This protocol incorporates a fault-tolerant multiplex signal bus that ensures successful operation even when components fail. In this article, we explore the design goals, technical specifications, and engineering considerations that make SAE J1813 a robust foundation for in-vehicle networking.
Design Goals and Engineering Principles
The VNP was crafted with a comprehensive set of design goals to ensure reliability, flexibility, and performance. These goals include message integrity, bit integrity, asynchronous bus access, priority contention, contention resolution, assignable priority, message content arbitration, expandability, functional and node-to-node addressing, data transfer, low latency, optimized baud rate, microprocessor compatibility, fault diagnosis, and self-clocking waveforms.
| Design Goal | Description |
|---|---|
| Message Integrity | Assurance that a transmitted message arrives as sent, using error checking codes (e.g., CRC) and acknowledgment. |
| Bit Integrity | Distinct representation of logic 1 and 0 to withstand noise corruption. |
| Asynchronous Bus Access | Ability to transmit on an unscheduled or demand basis. |
| Priority Contention | Bus access based on predetermined priority. |
| Contention Resolution | Deterministic resolution so the dominant contender maintains control while the loser becomes receiver. |
| Assignable Priority | Ability to prioritize a message independent of its content. |
| Message Content Arbitration | Resolve bus access contention based on message content. |
| Expandability | Accommodate future needs through flexible features and ability to define new data formats on the same bus. |
| Functional Addressing | Communicate based on functions independent of physical node location; supports multicast. |
| Node-to-Node Addressing | Direct communication between two specific physical nodes. |
| Data Transfer | Transmit multiple data bytes to one or more nodes. |
| Low Latency | Guaranteed access (with maximum priority) within 20 ms. |
| Optimized Baud Rate | 10 Kbit/s balances message latency, simple transmission line media, and acceptable automotive radiation. |
| Microprocessor Compatibility | Message format easily encoded/decoded by 8‑bit, byte-oriented microprocessors. |
| Fault Diagnosis | Ability to isolate faults to physical nodes. |
| Self-Clocking Waveforms | Synchronize message transmissions on a bit‑by‑bit basis without external clock. |
🛠️ Engineering Insight: The use of pulse width modulation for bit encoding not only provides self-clocking but also simplifies interface hardware by combining data and clock into a single signal. This reduces wiring complexity in automotive systems.
Technical Specifications: Bit Encoding and Message Format
The protocol employs a pulse width modulated (PWM) bit waveform to represent logic states and unique start and end‑of‑data bits. This self-clocking approach embeds timing information directly into the signal, enabling robust synchronization even in noisy automotive environments. The general message format begins with a start bit, followed by a priority/type field that also defines the message type, and ends with a stop bit field. All messages must be contained within 101 bit‑cell times from initiation. This flexible structure allows multiple data formats to coexist on the same bus.
⚠️ Common Mistake: Overlooking fault tolerance requirements can lead to system‑wide failures. The protocol provides fault diagnosis to isolate faults to specific nodes, but these features must be properly implemented in the design.
Fault Tolerance and Medium Access Control
SAE J1813’s fault-tolerant bus complements the VNP by ensuring continued operation despite component failures. The contention resolution mechanism ensures deterministic access: when multiple nodes attempt to transmit simultaneously, the message with the highest priority wins without data corruption. Losing contenders automatically revert to receiver mode. This arbitration is based on the priority/type field, which is assignable per message. Additionally, functional addressing allows communication with groups of nodes based on function, independent of their physical location.
Frequently Asked Questions
1. What is the maximum latency guaranteed by SAE J1813?
The protocol guarantees that a message with maximum priority will access the bus within 20 ms, assuming a 10 Kbit/s bus speed. Designers must ensure that latency‑critical applications respect this constraint.
2. How does the protocol handle bus contention?
The built‑in priority contention mechanism uses the start of message to arbitrate. The node with the highest priority (dominant bit pattern) continues transmission; others become receivers. This deterministic resolution prevents data corruption.
3. What bit encoding does SAE J1813 use?
It uses pulse width modulation (PWM) to represent logic 1, logic 0, and special bits (start, end‑of‑data). The duty cycle of the bit cell determines the logical value, providing self‑clocking properties.
4. Is SAE J1813 compatible with modern microcontrollers?
The protocol was designed for 8‑bit, byte‑oriented microprocessors, but its simple message format and encoding can be implemented with modern MCUs as well. However, the bus speed of 10 Kbit/s is low by today’s standards.
The SAE J1813 standard laid important groundwork for later vehicle network protocols, and its emphasis on fault tolerance, deterministic contention, and self‑clocking waveforms remains relevant in many embedded and automotive applications.
