Blog

OBDonUDS (SAE J1979-2): The New Diagnostic Standard for Modern Vehicles

Januar 15, 2012

Introduction: A New Era for Vehicle Diagnostics

Across the global automotive and trucking industries, on-board diagnostics (OBD) play a critical role in ensuring vehicles comply with emissions regulations throughout their entire life cycle. For decades, OBD standards have defined what diagnostic data must be available and how external diagnostic tools commonly called scan tools can access that data. Today, that diagnostic landscape is changing.

With the release of SAE J1979-2, often referred to as OBDonUDS or OBD on UDS, the industry is transitioning to a modern diagnostic framework based on Unified Diagnostic Services (UDS). This shift is expected to gradually replace legacy OBD variants across passenger vehicles, trucks, and other regulated vehicle categories in the coming years.

What Is OBDonUDS (SAE J1979-2)?

OBDonUDS is the latest evolution of the OBD diagnostic standard defined by SAE J1979-2. It specifies that OBD diagnostic data must now be accessed using the UDS protocol, rather than legacy OBD-specific diagnostic mechanisms. In practical terms:

  • OBD defines the regulatory diagnostic requirements
  • UDS defines the diagnostic communication protocol

UDS itself is standardized under ISO 14229 and has been widely used for manufacturer-specific diagnostics for many years. OBDonUDS extends this proven protocol to cover emissions-related and legislated diagnostic use cases as well.

Why Was the OBD Standard Revised?

The revision of the OBD diagnostic protocol was driven by several technical and practical limitations in earlier standards.

Exhausted Identifier Space

Legacy OBD protocols relied on fixed-length identifiers. Over time, this led to a shortage of unique identifiers in key areas, particularly for diagnostic trouble codes (DTCs). The lack of expansion capability limited how precisely faults could be described.

Limited Fault Detail

Earlier OBD standards provided only basic fault information. Modern vehicles, however, require more detailed diagnostic insight. OBDonUDS introduces extended data structures, enabling richer fault memory content such as:

  • Extended snapshot data
  • More detailed failure context
  • Improved correlation between faults and operating conditions

Improved Diagnostic Frequency Monitoring

OBDonUDS enhances support for In-Use Monitor Performance Ratios (IUMPRs). These redesigned parameters make it possible to determine how often specific diagnostic monitors actually ran during real-world vehicle operation, improving compliance verification and diagnostic transparency.

Overall, OBDonUDS allows significantly more detailed and higher-quality information to be retrieved from emission-relevant components.

Why Is the New OBD Standard Based on UDS?

The decision to base OBDonUDS on UDS was deliberate and strategic.

UDS is a mature, field-proven diagnostic standard already used across the industry for extended and manufacturer-specific diagnostics. It is supported by:

  • AUTOSAR software components
  • Established ECU architectures
  • A wide ecosystem of development and test tools

By building OBD diagnostics on UDS, the industry benefits from one unified diagnostic protocol instead of maintaining separate OBD and UDS implementations.

Key Advantages of a UDS-Based OBD Standard

  • Simplified ECU software architecture
  • Easier integration of regulatory and manufacturer-specific diagnostics
  • Reduced maintenance and validation effort
  • Long-term scalability as vehicle complexity increases

In short, UDS provides a solid technical foundation for legislated diagnostics without reinventing the wheel.

OBDonUDS Diagnostic Architecture

OBDonUDS follows a layered diagnostic model that cleanly separates responsibilities across the communication stack:

Application └── OBD Diagnostic Services └── UDS Stack └── ISO-TP └── CAN

Layer Responsibilities

  • CAN (Controller Area Network) Provides the physical and data link layer for in-vehicle communication.
  • ISO-TP (ISO 15765-2) Enables segmentation and reassembly of larger diagnostic messages over CAN.
  • UDS Stack (ISO 14229) Defines diagnostic services, sessions, security access, and message handling.
  • OBD Diagnostic Services Implements legislated emissions diagnostics using UDS mechanisms.
  • Application Layer Interfaces with scan tools, service equipment, and diagnostic applications.

This architecture ensures robustness, scalability, and compatibility with modern vehicle networks.

From Multiple OBD Variants to One Unified Approach

Historically, different OBD standards evolved for different vehicle categories and markets, including:

  • OBD II
  • Heavy Duty OBD (HD-OBD)
  • World Wide Harmonized OBD (WWH-OBD)

These variations increased complexity for OEMs, suppliers, and tool vendors. OBDonUDS is expected to gradually replace these variants, creating a harmonized diagnostic approach across vehicle types ranging from passenger cars to heavy-duty trucks and construction equipment.

Impact on ECU Development

OBDonUDS significantly changes how diagnostics are implemented within ECUs.

Before OBDonUDS

Although legacy OBD protocols appeared similar to UDS at a high level, they differed in many critical details. As a result, ECUs often contained:

  • One diagnostic stack for OBD
  • A separate diagnostic stack for UDS

This duplication increased software size, complexity, and validation effort.

With OBDonUDS

  • A single UDS-based diagnostic stack can support both regulatory and manufacturer-specific diagnostics
  • Duplicate protocol implementations are eliminated
  • ECU software becomes cleaner and more maintainable

However, ECUs must be updated or newly developed to support OBDonUDS-compliant functionality.

Tooling and Process Implications

The transition to OBDonUDS also affects the diagnostic toolchain.

New Tools Are Required

  • Legacy OBD scan tools are no longer sufficient
  • New scan tools must support UDS-based OBD services
  • Updated test tools are needed to validate OBDonUDS compliance

Specification and Documentation Changes

  • ECU diagnostic content must be precisely specified using updated tooling
  • Documentation and data archiving processes will evolve alongside the new standard

These changes are expected, but they also bring long-term simplification and consistency.

Why OBDonUDS Matters for the Trucking Industry

For commercial vehicles and fleets, OBDonUDS is more than a standards update it is a foundation for future diagnostics.

Key benefits include:

  • Deeper diagnostic insight into emission-related systems
  • Improved compliance verification
  • Better support for connected and remote diagnostics
  • Alignment with software-defined vehicle architectures

As adoption increases, OBDonUDS will become a standard expectation rather than an exception in trucking platforms.

Conclusion

OBDonUDS, as defined by SAE J1979-2, represents the next generation of on-board diagnostics. By combining regulatory OBD requirements with the proven UDS protocol, the industry gains a unified, scalable, and future-ready diagnostic solution. As vehicle architectures continue to evolve especially in the trucking and heavy-duty sectors OBDonUDS will play a central role in ensuring compliance, reliability, and long-term maintainability. Organizations that understand and adopt OBDonUDS early will be better positioned for the diagnostic challenges of tomorrow.