Hubbry Logo
SAE J1708SAE J1708Main
Open search
SAE J1708
Community hub
SAE J1708
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
SAE J1708
SAE J1708
SAE J1708
View on Wikipedia
from Wikipedia

Society of Automotive Engineers standard SAE J1708 is a standard used for serial communications between ECUs on a heavy duty vehicle and also between a computer and the vehicle. With respect to Open System Interconnection model (OSI), J1708 defines the physical layer. Common higher layer protocols that operate on top of J1708 are SAE J1587 and SAE J1922. The protocol is maintained by SAE International.

Description

[edit]

The standard defines a 2-wire 18 gauge wire cable that can run up to 130 feet (40 m) and operates at 9600 bit/s. A message is composed of up to 21 characters, unless the engine is stopped and the vehicle is not moving in which case transmitters are allowed to exceed the 21 byte max message length. Messages start with a Message ID (MID) character and finish with a checksum at the end. Characters are transmitted in the common 8N1 format.

The hardware utilized are RS-485 transceivers wired for open collector operation through the use of a pullup and pulldown of the separate data lines. Transmission is accomplished by controlling the driver enable pin of the transceiver. This method allows multiple devices to share the bus without the need for a single master node. Collisions are avoided by monitoring the bus while transmitting the MID to ensure that another node has not simultaneously transmitted a MID with a higher priority.

History

[edit]

SAE J1708, although still widely used, is replaced by SAE J1939 which is a CAN protocol.

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

SAE J1708

View on Grokipedia
from Grokipedia
SAE J1708 is a recommended practice established by the Society of Automotive Engineers (SAE) that defines the physical and data link layers for bidirectional serial data communications between microcomputer systems in heavy-duty vehicle applications. This historical standard, originally published in 1986 and last revised in 2004, specifies a twisted-pair wiring interface based on RS-485 electrical characteristics, operating at a baud rate of 9.6 kbps to facilitate reliable data exchange in harsh automotive environments. It serves as the foundational network protocol for interconnecting electronic control units (ECUs) within commercial vehicles, such as trucks and buses, and supports communication between the vehicle and external diagnostic computers. SAE J1708 is commonly paired with the SAE J1587 protocol, which provides the higher-level application and messaging structure, enabling standardized fault reporting, parameter monitoring, and system diagnostics across heavy-duty fleets. While largely superseded in modern vehicles by more advanced protocols like SAE J1939 based on Controller Area Network (CAN), J1708 remains relevant for legacy systems and certain aftermarket applications due to its robustness and widespread historical adoption.

Overview

Definition and Purpose

SAE J1708 is an SAE Recommended Practice that defines a bidirectional, link for connecting microcomputer systems, known as electronic control units (ECUs), in heavy-duty vehicle applications. This standard establishes the foundational protocols for serial data exchange, ensuring compatibility across various vehicle components in demanding operational environments. The primary purpose of SAE J1708 is to enable reliable and efficient data transfer between vehicle modules, such as engines, transmissions, and braking systems, thereby supporting essential functions like vehicle control, performance monitoring, and diagnostic processes. By providing a standardized framework for communication, it addresses the challenges of integrating diverse ECUs from multiple manufacturers, promoting and reducing system complexity in heavy-duty trucks and buses. This is critical for maintaining consistent data flow without proprietary adaptations, ultimately enhancing vehicle reliability and serviceability. As the basis for the physical and layers, SAE J1708 supports multi-master, asynchronous serial networks designed to withstand the harsh conditions of use, including vibrations, temperature extremes, and electrical noise. It facilitates a cost-effective approach to networking by leveraging standard , allowing for flexible expansion of systems while minimizing hardware costs. Often paired with higher-layer protocols like SAE J1587 for defining message content, SAE J1708 ensures that core communication infrastructure remains robust and adaptable for evolving diagnostic and control needs.

Scope and Applicability

SAE J1708 applies primarily to heavy-duty on-road vehicles, such as trucks, buses, and trailers, where serial data communication is required between electronic control units (ECUs). This standard facilitates bidirectional, low-speed data exchange in networks, supporting applications like diagnostics and basic information sharing among up to 20 nodes on the bus. The scope is strictly limited to wired serial communications over a twisted-pair bus, excluding technologies, high-speed networks, and applications in passenger cars or light-duty vehicles. Operating at a nominal rate of 9,600 bps, it serves as a robust physical and for non-safety-critical data transmission, without support for real-time systems that demand faster protocols. Designed for the harsh operating environments of commercial vehicles, SAE J1708 withstands , mechanical vibration, shock, and temperature extremes ranging from -40°C to +85°C, ensuring reliable performance in on-road heavy-duty scenarios. It complements higher-layer protocols like SAE J1587 for diagnostic messaging but does not extend to control functions requiring higher bandwidth or .

Technical Specifications

Physical Layer

The physical layer of SAE J1708 establishes the hardware foundation for reliable serial communication in heavy-duty vehicle networks, utilizing differential signaling based on principles for enhanced noise immunity and robustness in electromagnetic interference-prone environments. Cabling consists of a twisted-pair configuration with signal wires designated as A and B, employing a minimum of one 360° twist per inch (2.54 cm) to minimize and . The wire gauge is specified as 18 AWG, providing sufficient conductivity for the network while maintaining flexibility; shielding is optional but recommended in high-noise areas to further protect against external disturbances. The maximum bus length is limited to 40 meters to ensure without degradation. The standard connector for diagnostic access is the 6-pin Deutsch type, ruggedized for heavy-duty applications, with pins allocated for A (J1708+), B (J1708-), ground, and power supplies to facilitate connections between electronic control units (ECUs) and service tools. This connector design ensures secure mating and resistance to vibration and in under-hood environments. The network topology is a linear multi-drop bus, supporting up to 20 nodes in a daisy-chain arrangement without the need for terminating resistors at the ends, as the biasing provides inherent operation and prevents signal reflections. This configuration allows multiple ECUs to share the bus efficiently while simplifying installation in commercial vehicles. Environmental resilience is addressed through specifications that withstand automotive operating conditions, including a temperature range of -40°C to 85°C and exposure to fluids such as oils, fuels, and coolants without insulation degradation. The cabling and connectors are engineered for durability against , , and chemical contaminants typical in heavy-duty applications. The SAE J1708 standard specifies electrical characteristics compatible with the interface, utilizing differential signaling over a twisted-pair medium to ensure reliable transmission in harsh vehicle environments. The minimum differential voltage is 1.5 V for a logic 1 (dominant state) and -1.5 V for a logic 0 (recessive state), with receiver thresholds typically at ±200 mV to detect these levels robustly. The common-mode voltage range spans -7 V to 12 V, accommodating ground shifts between nodes, while open-collector drivers enable multi-master operation by allowing any node to pull the bus lines without contention during idle periods. Communication occurs at a fixed rate of 9600 bits per second in asynchronous serial mode, employing an 8-bit data frame with 1 start bit, no parity, and 1 stop bit (8N1 format), resulting in a bit time of approximately 104.17 µs. This configuration supports up to 20 nodes on a bus length of 40 meters using 18-gauge twisted-pair wiring, with no termination resistors required due to the open-collector design. Timing constraints include a minimum inter-message idle period of 10 bit times and maximum inter-byte gaps of 2 bit times to maintain synchronization across nodes. At the data link layer, SAE J1708 employs a multi-master architecture with non-destructive bitwise to manage bus access. Nodes transmit the identifier (MID) byte starting with the least significant bit, simultaneously monitoring the bus; if a transmitted bit differs from the received bit (indicating a higher-priority from another node), the transmitting node immediately ceases and retries after the bus becomes idle. This and resolution mechanism ensures priority-based access without , with priorities ranging from 1 (highest) to 8 (lowest) influencing delays of 0 to 14 bit times (2 bit times per priority level). Messages are limited to a maximum of 21 bytes total, consisting of a 1-byte identifier (MID), up to 19 bytes, and a 1-byte . Bus idle is detected through the recessive state when no node drives the lines, facilitating and error recovery at the link level. Error handling in SAE J1708 focuses on basic link-layer mechanisms without built-in cyclic redundancy checks (CRC) or advanced integrity verification, deferring comprehensive to higher protocol layers. Collisions are resolved via process, and bus faults are detected through idle state monitoring and voltage level discrepancies, prompting nodes to back off and retry. This lightweight approach prioritizes simplicity and real-time responsiveness in multi-node environments, though it relies on overlying standards for robust correction.

Applications

Vehicle Network Integration

SAE J1708 functions as the physical and backbone in heavy-duty vehicle networks, facilitating low-speed serial data exchange among electronic control units (ECUs) such as control modules (ECMs), transmission control modules, and (ABS) controllers. Operating at a nominal rate of 9.6 kbps over a twisted-pair bus based on differential signaling, it enables multi-drop communication where multiple ECUs share the same network segment for real-time status updates, command signals, and data . This supports efficient inter-ECU coordination in applications like performance monitoring and control, without the higher bandwidth demands of modern protocols. Node addressing in SAE J1708 networks relies on implicit mechanisms embedded within the message content, where each data packet includes identifiers such as source addresses and parameter IDs to route and filter information among connected devices. This content-based approach allows ECUs to process only relevant messages, minimizing overhead in low-speed environments. The standard supports up to 20 ECUs per bus segment, ensuring scalability for typical heavy-duty configurations while maintaining and resolution through with non-persistent collision avoidance. Integration with vehicle power systems involves direct compatibility with 12V and 24V DC electrical architectures, where all nodes share a common ground reference to prevent potential differences that could disrupt communication. The protocol incorporates provisions for transient protection, including the use of robust transceivers and external components like transient voltage suppressors (TVS diodes) to safeguard against and voltage spikes common in automotive settings. This ensures reliable operation across the vehicle's electrical distribution without dedicated power lines for the bus itself. As a legacy standard, SAE J1708 was widely adopted in pre-2000s heavy-duty trucks for signals from sensors and actuators, replacing dedicated wiring with a single serial bus to streamline harness design and reduce overall vehicle weight and assembly costs. This multiplexing capability allowed centralized control of diverse functions, from position to pressure, fostering earlier advancements in electronic vehicle management while paving the way for subsequent protocols like SAE J1939.

Diagnostic and Service Tools

SAE J1708 employs a standardized 6-pin Deutsch connector, typically gray in color, for off-board diagnostic access, commonly located under the near the or in the to facilitate service tool connections. The pin assignments include A for J1708 positive, B for data link negative, C for ground, and D for ignition-switched power (battery positive, often fused at 10A), enabling reliable communication while powering external devices. This connector design, prevalent from the early to the mid-2000s, supports plugging in scan tools for vehicle interrogation without disrupting in-vehicle operations. Diagnostic tools compatible with SAE J1708 often utilize PC-based interfaces through to J1708 adapters, such as the Cummins INLINE 6, which connects via a 25-pin to access the for parameter reading, fault clearing, and updates. These adapters bridge legacy to modern PCs, allowing technicians to interface with electronic control units (ECUs) using software like INSITE for comprehensive service functions. The protocol's UART-based signaling ensures straightforward integration with off-board equipment, though adapters must handle the twisted-pair differential signaling for noise immunity. In fleet operations, SAE J1708 tools are routinely used for fault code retrieval to identify issues in trucks and buses, enabling quick resolution of and transmission problems. They also support emissions testing by extracting compliance data from older heavy-duty vehicles, aiding regulatory inspections. For predictive maintenance, diagnostic scans via J1708 help monitor trends in component health, scheduling interventions before failures occur in commercial fleets. Despite its utility, SAE J1708's data rate of 9600 baud imposes limitations on real-time monitoring, making it unsuitable for high-speed applications in modern diagnostics. Consequently, it is frequently supplemented by in newer vehicles, which offers faster CAN-based communication through a 9-pin connector for enhanced service efficiency.

SAE J1587 Protocol

SAE J1587, originally published in and last revised in , serves as the protocol layered atop the SAE J1708 serial mechanism, standardizing the format and content of messages for diagnostic and operational data exchange in heavy-duty networks. It defines a set of identifiers (PIDs) to represent specific , such as engine speed (PID 190, reported as an unsigned 16-bit value with 0.25 RPM per bit resolution), engine coolant temperature (PID 110, in degrees with 1°C per bit), and speed (PID 84, in km/h with 1 km/h per bit). These PIDs enable consistent interpretation of data across electronic control units (ECUs) from different manufacturers, facilitating in diagnostics and monitoring. The core message structure in SAE J1587 consists of packets limited to a maximum of 21 bytes to align with J1708 constraints, beginning with a 1-byte message identifier (MID) that specifies the source ECU address (ranging from 0 to 255, with values 128-255 typically reserved for ECUs). This is followed by up to 19 bytes of data, which includes 1-2 bytes for a ID (PID) or subsystem ID (SID) to denote the or affected component and up to 17-18 bytes encoding the parameter values in a predefined format (e.g., signed or unsigned integers with specified scaling), and concluding with a 1-byte calculated via modulo-255 arithmetic for transmission integrity. Messages may also include proprietary identifiers like proprietary PIDs (PPIDs) or subsystem proprietary PIDs (PSIDs) for vendor-specific extensions, ensuring flexibility while maintaining core standardization. For data exceeding 21 bytes, multi-section messages can be used with PID 192. Fault reporting in SAE J1587 employs a structured diagnostic trouble code (DTC) format broadcast via dedicated messages, incorporating the MID to identify the reporting ECU, a PID or SID to pinpoint the affected parameter or subsystem, a 1-byte failure mode identifier (FMI) describing the nature of the fault (e.g., FMI 3 indicates voltage above normal or shorted high, while FMI 4 denotes voltage below normal or shorted low), a 1-byte occurrence count tracking fault instances since last reset, and lamp status bits signaling required dashboard indicators (e.g., stop lamp or amber warning lamp). This scheme allows for up to 31 FMI values per PID/SID, covering electrical, mechanical, and data-related , with codes transmitted in response to queries or automatically upon detection to support on-board and off-board diagnostics. Data exchange under SAE J1587 primarily follows a request-response model for diagnostics, where a diagnostic tool or ECU sends a targeted inquiry (e.g., using PID 0 with the desired PID, such as 84 for vehicle speed, as the data byte) to elicit detailed responses from addressed nodes, enabling on-demand retrieval of status or configuration . Complementing this, the protocol supports broadcast messages for efficient sharing of real-time parameters, such as periodic broadcasts of critical PIDs like engine load or fuel rate from the source ECU's MID, which reduce bus traffic while ensuring timely updates across the network. This dual approach balances diagnostic depth with in multi-ECU environments.

Comparison with SAE J1939

SAE J1708, when paired with the J1587 protocol, employs an RS-485-based serial architecture operating at a fixed rate of 9.6 kbps, utilizing twisted-pair wiring for communication and supporting single messages up to 21 bytes in length, with limited multi-section capabilities for longer data using PID 192. In contrast, is built on the Controller Area Network (CAN) 2.0B protocol, leveraging a differential two-wire with standardized rates of 250 kbps (per J1939-11 and J1939-15) or 500 kbps (per J1939-14), and employs 29-bit extended identifiers structured around Parameter Group Numbers (PGNs) for message identification, enabling variable-length data payloads up to 8 bytes per frame and multi-packet transport for larger datasets reaching 1785 bytes. The transition from SAE J1708 to SAE J1939, which gained momentum in the mid-2000s, was driven primarily by the former's limitations in bandwidth and scalability, as the increasing complexity of heavy-duty vehicle powertrains, sensor arrays, and diagnostic requirements outpaced the 9.6 kbps speed and 21-byte message constraint of J1708/J1587 systems. J1939 addressed these shortcomings by providing higher data throughput and robust error handling via cyclic redundancy checks (CRC), facilitating multiplexed networking for advanced features like telematics and real-time diagnostics in modern trucks. During the transitional period from the early 1990s to the 2010s, many vehicles supported coexistence of both standards through dual-bus configurations, often via a 9-pin Deutsch diagnostic connector where J1708 signals appeared on pins F and G (using the legacy 6-pin layout compatibility), while J1939 utilized pins C and D for CAN high/low lines, allowing diagnostic tools to interface with both legacy and new systems simultaneously. While SAE J1708 offers simplicity and lower implementation costs suitable for basic diagnostics in older vehicles, its obsolescence for high-bandwidth applications—such as video integration or advanced driver-assistance systems (ADAS)—highlights J1939's advantages in scalability and reliability, though the latter introduces greater complexity in and address claiming.
AspectSAE J1708 (with J1587)SAE J1939
Physical Layer serial, twisted-pairCAN 2.0B, differential twisted-pair
Baud Rate9.6 kbps250 kbps or 500 kbps
Message FormatUp to 21 bytes, fixed; MID/PID/FMI; limited multi-section8 bytes per frame; PGN/SPN/FMI; multi-packet
Error HandlingBasic CRC with network management
ScalabilityLimited to basic diagnosticsSupports advanced and

History

Initial Development

SAE J1708 originated in the mid-1980s as a response to the increasing complexity of electronic control units (ECUs) in heavy-duty vehicles, where the proliferation of standalone electronic systems necessitated a standardized communication framework to manage data exchange efficiently. The standard was developed by the and Bus Electronic Interface Subcommittee of the SAE and Bus Electrical/Electronic , in collaboration with the and Maintenance Council (TMC) of the American Trucking Associations (ATA), to address the challenges posed by fragmented electronic architectures in and buses. This effort was motivated by the need to replace proprietary communication systems employed by major engine manufacturers, such as and , which hindered and maintenance across different vehicle platforms. A key milestone in its development occurred with the first issuance of SAE J1708 as a Recommended Practice in , establishing it as the foundational serial protocol for heavy-duty vehicle applications. By that year, the protocol was already deployed in field test trucks to facilitate real-time communication between engine electronic controls and emerging all-electronic instrument panels, marking an early step toward integrated vehicle . The drive was further propelled by the impending 1988 U.S. Environmental Protection Agency (EPA) emissions regulations, which mandated stricter controls on nitrogen oxides () and particulate matter (PM) for heavy-duty diesel engines starting in the 1991 model year, thereby accelerating the adoption of ECUs and the diagnostic capabilities they required. Influenced by the robust electrical characteristics of the standard for industrial multipoint communications, SAE J1708 incorporated balanced twisted-pair wiring and open-collector operation to ensure reliability in harsh vehicle environments, while prioritizing wiring reduction through multiplexing to minimize the complexity of point-to-point connections. This design choice enabled bidirectional serial links among multiple microcomputer-based modules, supporting essential functions like diagnostics and basic data sharing without the vulnerabilities of earlier proprietary setups. Early adoption of SAE J1708 gained traction in the , as it became integrated into production heavy-duty for fundamental applications, effectively supplanting traditional hardwired systems and laying the groundwork for enhanced vehicle network integration. By the mid-, the protocol was a staple in diagnostic connectors and ECU interfaces across major fleets, facilitating compliance with evolving regulatory demands and improving serviceability in commercial operations.

Revisions and Current Status

The SAE J1708 standard has undergone several revisions since its initial development, with notable updates in 2004 and 2016. The August 2004 revision, designated J1708_200408, updated the specifications for serial data communications in heavy-duty vehicle applications, focusing on hardware and software compatibility parameters. The September 2016 revision, J1708_201609, further refined these parameters and was subsequently stabilized, indicating no anticipated major changes. As of 2025, SAE J1708 remains a stabilized standard maintained by for backward compatibility in existing systems. It continues to see use in legacy heavy-duty vehicle fleets, particularly for diagnostic and communication functions in older equipment, but has been largely phased out in new vehicle designs in favor of the more advanced protocol. Recent developments underscore ongoing concerns with the protocol's . A SAE technical paper introduced the Legacy Intrusion Detection System (LIDS) as a cybersecurity defense for J1708/J1587 networks in heavy-duty vehicles, marking the first such research and emphasizing inherent vulnerabilities, including the absence of and mechanisms. There have been no major updates to the standard since its stabilization. Looking ahead, SAE J1708's role is expected to remain limited to aftermarket retrofits, gateway solutions for protocol transitions, and diagnostic tools supporting pre-2010 vehicles, with sustained relevance in international markets where legacy systems persist.

References

  1. https://www.sae.org/standards/j1708_200408-serial-data-communications-microcomputer-systems-heavy-duty-vehicle-applications
  2. https://kvaser.com/about-can/can-standards/j1708/
  3. https://www.vector.com/us/en/know-how/protocols/j1587-j1708/
  4. https://copperhilltech.com/a-brief-introduction-to-sae-j1708-and-j1587/
  5. https://www.sae.org/standards/j1708_201609-serial-data-communications-microcomputer-systems-heavy-duty-vehicle-applications
  6. https://www.vector.com/int/en/know-how/protocols/j1587-j1708/
  7. https://www.diesellaptops.com/blogs/news/troubleshooting-j1708-connections
  8. https://jcom1939.com/sae-j1708-vs-sae-j1939-understanding-the-differences-and-transition-in-heavy-trucks/
  9. https://www.renesas.com/en/document/apn/an1990-rs-485-transceivers-j1708-physical-layer-applications-heavy-duty-vehicles
  10. http://www.bitsavers.org/components/national/_appNotes/AN-0915.pdf
  11. https://www.auelectronics.com/downloads/usermanual_simj1708.pdf
  12. https://opusivs.com/wp-content/uploads/2023/12/DrewLinQ_Industry_Connectors_Reference_OpusBranded.pdf
  13. https://community.automationdirect.com/s/question/0D53u00002AhX5RCAV/rs485-modbus-help-needed-for-3rd-party-slave
  14. https://jcom1939.com/j1708-to-j1939-gateway-solutions-for-diesel-engine-retrofits-mid-2025/
  15. https://www.sae.org/standards/content/j1708_201609/
  16. https://www.simmasoftware.com/j1587-vs-j1939/
  17. https://www.scribd.com/document/435615887/01-Datalink-J1587-J1708
  18. https://www.researchgate.net/publication/296665448_Multiplexed_Operator_Control_Switches_in_a_Modular_Package
  19. https://www.rvupgradestore.com/v/vspfiles/assets/pdf/VMSPC9-Wiring.pdf
  20. https://www.cummins.com/parts-and-service/digital-products-and-services/inline
  21. https://www.balticdiag.com/cummins-inline-6-diagnostic-tool
  22. https://www.trucknews.com/transportation/vehicle-diagnostics-provide-real-time-performance-reports-to-optimize-fleet-maintenance/1000037750/
  23. https://www.fcarusa.com/TechSupport/FAQ/intro-j1587-j1708-standard-fault-codes
  24. https://kvaser.com/about-can/can-standards/j1587/
  25. https://cdn.hackaday.io/files/18651797964384/SAE%2520J1587%2520%282002%2520Standard%29.pdf
  26. https://otrperformance.com/blogs/quick-tips/intro-to-sae-j1587-j1708-standard
  27. https://www.vector.com/at/en/know-how/protocols/j1587-j1708/
  28. https://www.ssi-sensors.com/perch/resources/documents/acu-trac-j1708-mode-messaging-at-an7.pdf
  29. https://www.noregon.com/guide-to-sae-j1939/
  30. https://www.vector.com/int/en/know-how/protocols/sae-j1939/
  31. https://www.csselectronics.com/pages/j1939-explained-simple-intro-tutorial
  32. https://legacy.sae.org/publications/technical-papers/content/861971/
  33. https://img.antpedia.com/standard/files/pdfs_ora/20221105/SAE%2520J1708-201609.pdf
  34. https://www.simmasoftware.com/products/j1708/software/
  35. https://www.epa.gov/regulations-emissions-vehicles-and-engines
  36. https://jcom1939.com/why-j1939-doesnt-speak-j1708-j1587-protocols-in-conflict/
  37. https://www.noregon.com/tech-tips-selecting-the-correct-diagnostic-port/
  38. https://www.sae.org/standards/content/j1708_200408/
  39. https://standards.globalspec.com/std/14684580/j1708-201609
  40. https://rosap.ntl.bts.gov/view/dot/38822/dot_38822_DS1.pdf
  41. https://saemobilus.sae.org/articles/trucking-forward-intrusion-detection-sae-j1708-j1587-networks-heavy-duty-vehicles-2024-01-2805
  42. https://jcom1939.com/market-analysis-sae-j1708-monitoring-diagnostic-devices-north-america/
  43. https://www.diesellaptops.com/blogs/news/truck-sae-codes-such-as-j1939-j1708-spn-fmi-mid-explained
Add your contribution
Related Hubs
User Avatar
No comments yet.