Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J1587-2013: Heavy-Duty Vehicle Electronic Data Interchange Standard
Overview and Scope
SAE J1587 has been a foundational standard for on-board diagnostics and data exchange in heavy-duty vehicles for decades. This 2013 revision, now stabilized, defines the electronic data interchange (EDI) framework among microcomputer systems such as engine control units, transmission controls, and dash displays. While newer technologies like SAE J1939 have emerged, J1587 remains critical for maintaining and troubleshooting legacy fleets.
J1587 specifies a single-wire serial data link protocol for communication between vehicle ECUs. It standardizes message formats, parameter identification (PID), message identification (MID), and failure mode identifiers (FMI). The standard also includes transport protocol definitions for multi‑packet messaging and appendices covering electronic dash displays and driver interface units.
Core Components of SAE J1587
Message and Parameter Identifiers
The MID space is organized by functional groups (e.g., engine, brake, transmission) to avoid conflicts. PID assignments define individual data parameters such as engine speed, coolant temperature, or vehicle speed. The standard provides a structured procedure via SAE to request new identifiers.
Failure Mode Identifiers (FMI)
FMI codes standardize diagnostic trouble descriptions. Examples include "Below Normal" or "Short Circuit". The table below lists common FMIs:
| FMI | Description |
|---|---|
| 0 | Above Normal Most Severe |
| 1 | Below Normal Most Severe |
| 2 | Data Erratic |
| 3 | Short Circuit to Ground |
| 4 | Short Circuit to Power |
| 5 | Open Circuit |
This standardized categorization ensures consistent diagnostic reporting across various ECUs and subsystems.
Transport Protocol
For messages that exceed the standard data link length, J1587 defines connection management commands for segmentation and reassembly. This is essential for uploading configurations, software updates, or extended diagnostic data.
Design Insights, Best Practices, and FAQs
🛠️ Engineering Design Insight: The standard implements a priority scheme for parameter updates, with recommended update periods for each PID. Temperature scaling uses a linear formula (e.g., A * x + B) to convert raw values to engineering units. The use of the ISO Latin 1 character set allows international text messages, critical for global vehicle platforms. When integrating J1587 with newer networks like J1939, careful gateway design is required to maintain translation accuracy.
⚠️ Important: As of 2013, SAE J1587 is classified as a stabilized standard. No further revisions are planned by the committee, and users are responsible for verifying the continued suitability of its technical requirements. Newer technology alternatives exist, but J1587 remains vital for legacy system support and is often used in conjunction with SAE J2497 for data transfer.
Frequently Asked Questions
1. How do I request a new MID, PID, or SID assignment?
The standard outlines a formal procedure through SAE. A request form (shown in the document) must be submitted to the appropriate SAE subcommittee. Currently the process is managed by the Truck and Bus Low Speed Communication Network Committee.
2. Can SAE J1587 be used alongside SAE J1939?
Yes. Many heavy‑duty vehicles use J1939 for high‑speed communications and J1587 for legacy or low‑speed diagnostics. Gateways can translate between the two, but designers must ensure consistency in parameter definitions.
3. What are the limitations of using a stabilized standard in new designs?
Stabilized standards are not maintained; they may not reflect current best practices or address modern requirements such as higher bandwidth or cybersecurity. New designs should evaluate J1939 or other protocols, while J1587 remains suitable for retrofit, service tools, and non‑critical data.
4. How does the transport protocol handle data errors?
The transport layer uses connection management commands with acknowledgments and timeouts. If errors are detected, retransmission or abort procedures are initiated. The appendices detail both error‑free and error‑recovery scenarios.
