Compliance Testing according to SAE J1699-3

The California Air Resources Board (CARB) introduced regulations requiring consistent communication over the OBD II link for emission related diagnostics for all vehicles of the model year 2005 and beyond. As a result, they helped to create the SAE standard J1699-3 Recommended Practice. J1699-3 defines a variety
of tests to ensure compliance with CARB/EPA OBD II mandates. All cars of model year 2005 and beyond have to pass the tests in order to be allowed to be sold in California. The J1699-3 tests are based on communication with the ECU(s) via a Pass-Thru device which is defined by the SAE standard J2534.

ETAS OBD II Conformance Test System

The ETAS OBD II Conformance Test System is a PC software application that automates the tests defined by SAE J1699-3 utilizing the J2534 Vehicle Interface Module ES6520 of ETAS or others. The ETAS OBD II Conformance Test System gives the user the possibility to work efficiently and target-oriented. The software
provides a comfortable graphical user interface, additional information about the currently running tests, .flexibility in running the tests, and advanced reporting capabilities.

Automation of the OBD II Conformance Test System

Based on the time consuming procedure to run a J1699-3 test with a lot of user interaction, it is convenient to run automated tests with a LABCAR, i.e. for release testing. Therefore, ETAS provides a LABCAR integration that consists of a .NET-API and a LABCAR tool adapter. The API contains a variety of functions
to provide the same functionality as the graphical user interface. The API also provides the possibility to run automated tests from any other test application and 3rd party HiL test systems.

Functions at a Glance

• Full implementation and automation of OBD II conformance tests according to SAE standard J1699-3
• User-friendly graphical interface
• User-selectable execution of individual tests or groups of tests
• Comprehensive reporting
• Detailed log of message traffic
• One supplier for both software (J1699-3) and hardware (J2534)