Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Guidelines for Permanently or Semi-Permanently Installed Diagnostic Communication Devices (SAE J3005-2021)
Note: SAE J3005-2021 was cancelled in December 2021 and superseded by SAE J3005-1 and SAE J3005-2. This article summarizes the key guidelines originally presented in the report, which remain relevant for understanding best practices in permanent OBD installations.
The SAE J1962 connector was originally designed for temporary diagnostic access in a controlled workshop environment. However, as vehicles increasingly host permanently or semi-permanently installed devices—such as telematics gateways, insurance dongles, and emissions monitoring systems—the need for clear guidelines has become critical. SAE J3005-2021 addresses these challenges by providing recommendations to device vendors for safe and non-disruptive integration with the vehicle’s onboard diagnostic system.
Challenges with Permanent OBD Connections 🔍
Permanent or semi-permanent devices connected to the OBD port can interfere with vehicle diagnostics in several ways, as identified in the standard’s foreword:
- Internal client conflicts: The vehicle’s internal OBD clients (e.g., telematics gateways) rely on standardized CAN IDs. External devices using the same IDs can cause the internal clients to lose access to diagnostic data, potentially disabling customer functions.
- Disturbance of vehicle functionality: Sending certain diagnostic services at inappropriate times, such as a Clear Diagnostic Trouble Code (DTC) request while the engine is running, may trigger false DTCs and mislead diagnostic monitors.
- CAN bus collisions: When multiple external devices are connected via a split-cable and use the same CAN identifier, simultaneous transmission can cause bus-off conditions and data loss.
- Monopolizing the bus: Devices that do not respect SAE J1979 timing requirements can prevent other clients from obtaining necessary data.
Key Technical Recommendations 🛠️
The standard offers detailed technical recommendations across several areas. The following table summarizes the core design guidelines:
| Aspect | Recommendation |
|---|---|
| Bus Access and Timing | Devices must not monopolize the OBD bus and must comply with SAE J1979 timing requirements to ensure other clients (including internal ones) can still access the bus. |
| Multiple Device Coordination | In split-cable configurations, devices must detect the presence of other devices to avoid CAN collisions. Coordination mechanisms should be implemented to share the bus effectively. |
| Internal Client Priority | Internal vehicle clients should have priority when requesting OBD data. External devices must not interfere with these requests. |
| Diagnostic Service Restrictions | Avoid sending disruptive services like ClearDTC while the engine is running. Only use services and PIDs that are safe for continuous polling. |
| Data Security and Tampering | Remote OBD devices should transmit data securely and include tampering detection mechanisms to prevent unauthorized manipulation of emissions-related data. |
Common Mistake: Failing to detect other devices on a split-cable can lead to CAN bus-off conditions and data loss. Always implement device detection and coordination mechanisms to avoid communication conflicts.
Application-Specific Guidelines and Frequently Asked Questions
Remote OBD (US and Euro VI)
These devices must use specific services and PIDs as defined in the standard. They should comply with OBD clearinghouse requirements and implement security recommendations to prevent tampering.
Portable Emissions Measurement Systems (PEMS)
Guidelines ensure that PEMS can reliably collect emissions data without interfering with the vehicle’s normal OBD operation or causing diagnostic issues.
Wireless Interfaces and Insurance Devices
Wireless dongles and insurance telematics devices should follow the communication recommendations, particularly regarding CAN bus usage and split-cable considerations. They must avoid sending unnecessary commands that could affect vehicle operation.
GPS and Other Additional Devices
Devices that require location data should integrate with OBD systems carefully, ensuring no conflict with primary diagnostic functions.
Frequently Asked Questions
1. Why should external devices avoid sending ClearDTC while the engine is running?
Clearing DTCs during engine operation can interfere with diagnostic monitors, causing them to incorrectly judge sensor values and potentially trigger false DTCs. This could lead to unnecessary warnings for overheating or other conditions.
2. How can multiple external devices safely share the OBD bus via a split-cable?
Devices must be able to detect each other’s presence and coordinate bus utilization. Without this detection, simultaneous transmission on the same CAN identifier can cause collisions and bus-off conditions. Implementing a simple arbitration or handshake mechanism is recommended.
3. What measures can ensure proper data collection for internal vehicle clients?
External devices should prioritize internal client requests by respecting the standardized OBD CAN IDs and timing. They should release the bus after each transaction and avoid long periods of continuous polling to allow internal gateways to function correctly.
4. Are the guidelines in SAE J3005-2021 still applicable after its cancellation?
Yes, the technical insights and design recommendations remain valid. The standard was superseded by SAE J3005-1 and SAE J3005-2, which provide more detailed guidance. The original report’s principles are still widely referenced by device vendors.
By following the recommendations outlined in SAE J3005-2021, device vendors can ensure reliable and non-disruptive integration with the vehicle’s diagnostic system, whether for remote monitoring, emissions testing, or telematics applications. For the latest detailed requirements, refer to the current versions SAE J3005-1 and SAE J3005-2.
