UDS Status Byte
UDS Status Byte
2
OBD/UDS
Background:
• Industry concerned about limited number of remaining undefined 2-byte diagnostic
trouble codes (DTC) and the need for additional DTCs for hybrid vehicles.
– Indicating 2-byte DTCs will run out soon. P-Codes 7753 used, 3510 remain
3
OBD/UDS
Background (cont.):
• SAE J1979-2: the proposed standard that documents select ISO 14229-1
(UDS) services that can be used for OBD communication on Controller Area
Network (CAN) data links.
– OBD/UDS includes the porting of classic J1979 Modes $01 to $0A as well
as additional features such as DTC-specific readiness, test results and
IUMPR to OBD.
4
OBD/UDS
• Current Requirement:
Only one freeze frame required (1968.2(g)(4.3.4)).
Freeze frame for misfire and fuel system malfunctions have priority.
• Proposal: Add more freeze frame information to provide additional data for a repair
technician to diagnose and repair an emission-related malfunction.
– Require freeze frame for at least 5 DTCs, each with 2 frames per DTC (one for the 1st
fault occurrence and the other for the most recent fault occurrence).
– Eliminate freeze frame priority requirements.
– 1st freeze frame - save all Parameter Identifiers (PIDs) required in
1968.2(g)(4.2.1)(A) on 1st fault occurrence.
– 2nd freeze frame - update at least once per driving cycle anytime a fault occurs, and
record all PIDs required in 1968.2(g)(4.2.1)(A).
5
Freeze Frame First and Last Occurrence - OBD
1968.2(g)(4.2.1)(A)
6
OBD/UDS Amendments - Readiness (Current)
8
OBD/UDS Amendments - Readiness
SAE INTERNATIONAL 9
OBD/UDS Amendments - Readiness
Also
• New Readiness Completion Requirements
• DTC-Specific Information in Readiness
10
OBD/UDS Amendments – Test Results
• Current Requirement: Required to report test results for monitors listed in 1968.2(g)(4.5).
• Issue: Manufacturer-defined Test Identifiers (TIDs) are used to identify each test performed by an
OBD monitor.
– Difficult for vehicle repair technicians and CARB OBD staff to correlate TIDs to specific
DTCs/monitors without detailed reference material often missing in service literature.
– Monitor test results intended to help the vehicle repair technician identify systems that may be
close to failing and to verify an emissions repair.
• Proposal: Report test results by DTC from all monitors subject to the IUMPR requirements except for
CCM.
– DTC-specific test results also required for all misfire and fuel system monitors, even though they
are not subject to IUMPR requirements.
– This new service will aid in the identification of monitor test results.
– Allow only one set of test results/TID per DTC
– DTC-specific test results service allow only one set of test results/TID per DTC. UDS data stream
service allows more than one set of test results/TIDs per DTC for misfire monitor only.
11
Why move away from the status quo?
12
Why move away from the status quo?
13
Today’s solution
14
In Discussion
15
Overview Service-Mapping
0x08 Request Control of On-Board System, Test or Component 0x31 01 StartRoutine, RID 0xE000 - 0xE1FF
16
Data - Changes in J1979 DA
Data Identifier (DID): 2 byte identifier for a data item, e.g. PID, OBDMID,
InfoType (see table)
Routine Identifier (RID): 2 byte identifier for a routine (e.g. ”EVAP leakage test”)
17
Data - Changes in J2012 DA
Supported Remark
0 TestFailed OBD
1 TestFailedThisOperationCycle OBD Used for trigger condition for Freezeframe (latest occurence)
2 PendingDTC OBD
3 ConfirmedDTC OBD
4 TestNotCompletedSinceLastClear OBD DTC based readiness since last clear
19
OBD/UDS Proposed Implementation Timeline
20
People that either willingly or unwillingly contributed to this information but
should be credited here for their good work and dedication.
21