UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

close
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

close
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

SAE - J1699-3

Vehicle OBD II Compliance Test Cases

active, Most Current
Organization: SAE
Publication Date: 1 April 2021
Status: active
Page Count: 280
scope:

The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5.

Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534.

SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met:

• The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface.

• The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534-2 feature "Mixed Format Frames on a CAN Network."

Document History

J1699-3
April 1, 2021
Vehicle OBD II Compliance Test Cases
The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in...
July 1, 2017
(R) Vehicle OBD II Compliance Test Cases
The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE...
July 1, 2015
(R) Vehicle OBD II Compliance Test Cases
The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE...
May 1, 2012
Vehicle OBD II Compliance Test Cases
A description is not available for this item.
December 1, 2009
(R) Vehicle OBD II Compliance Test Cases
The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE...
May 1, 2006
OBD II Compliance Test Cases
The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE...
August 1, 2004
OBD II Compliance Test Cases
The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE...

References

Advertisement