SAE Update for I-M Solutions Conference May 6-9, 2013 Schaumburg, IL Robert Gruszczynski Senior OBD Specialist, Volkswagen Group Vice Chairman, SAE E/E Diagnostics Steering Committee

SAE J1962 Status OBD II Diagnostic Connector April 15, 2013 Rich Means Bob Gruszczynski

J1962 Document Has Been Published – July 2012 The Document is available for purchase from SAE. Updates include: –Better definition of location requirement –Well defined access area –Other minor updates Future Changes May Include Additional Mechanical Specifications Related To Torque Placed On The Connector Due To Axial Misalignment When Inserting The Test Tool Connector.

J1930 Update E/E Diagnostics Committee Meeting April 10, 2013 Mark Laleman

SAE J1930 J1930-DA last Published March 2012 –J1930-DA is available as excel document J1930 Schedule –Last meeting on March 22nd, –Pending changes will be included in next update to J1930-DA (2 nd quarter 2013) –Schedule quarterly J1930/J2012 meetings for 2013 to allow more frequent updates. Meetings on Jan. 25 th, Mar. 22 nd, July 19 th, October 11 th

Recent Terms Added in J1930 Adaptive LearningAn algorithm that is used to adjust a control system to compensate for component variance, aging, or environmental conditions. The adaptive values are typically stored in memory (e.g. NVRAM). CalibrationThe permanent settings of software program variables that are assigned by engineering to deliver the desired function of the system or component. Battery Monitor ModuleA module that monitors the 12V battery system. Battery Interface Control Module A control module that monitors temperature, voltage, etc. of a number of cells in a hybrid/ev battery. Battery CellA self-contained energy conversion device whose function is to deliver electrical energy to an external circuit via a controlled internal chemical process Reference USABC document Battery ModuleThe smallest grouping of physically and electrically connected cells that can be replaced as a unit. A module can be thought of as the smallest, repeating building block of a battery pack. Reference USABC document Battery PackAn array of interconnected modules that has been configured for its intended energy storage application, that is, the configuration is application dependent. Reference USABC document Battery SystemCompletely functional energy storage system consisting of the pack(s) and necessary ancillary subsystems for physical support, thermal management, and electronic control. Reference USABC document Reductant Heater Control Module A control module that operates the Reductant heaters Turbocharger Outlet PressureThe pressure at the outlet of a turbocharger compressor EVAP System Vapor Pressure (EVAPVP) The pressure present in the EVAP system, measured in the fuel tank or in an evaporative system vapor line. Electronic Brake Boost Control Module (EBBC) A control module that manages the combination of mechanical and regenerative braking systems. ElecBrkBstCtrl Fuel Composition Sensor (FCOMP) A device that senses the percent blend of the engine fuel, typically used in a Flexible Fuel System Torque Vectoring Differential Control Module(TVDC) A control module that controls the torque distribution between either the two front or two rear wheels. TrqVecDiffCtl

SAE J1930 J1930 Next steps –Discuss “Revision Date” field with SAE web tool team –“Retire” the J1979 PID Annex, as J1979 now has a Digital Annex –Add new Figures in J1930 for intake and exhaust sensor locations, coordinate with J1979 figures, footnote terms related to the figures

J1979 Update E/E Diagnostics Committee Meeting April 10, 2013 Paul Baltusis

Changes to SAE/ISO Documents – J1979 Currently published documents: J1979_ E/E Diagnostic Test Modes (Feb 23, 2012) J1979DA_ Digital Annex of E/E Diagnostic Test Modes (Oct 10, 2011) ISO has the same document content with the exception of the Annexes. It refers to the J1979DA (Digital Annex). J1979 DA is expected to be published every 12 to 18 months. Plan to ballot after next meeting. CARB LEV III OBD changes reference the latest J1979DA J1979 Committee has quarterly meetings scheduled at SAE Troy: –Feb 15, 2013 –May 17, 2013 –Aug 16, 2013 –Dec 6, 2013

J1979 Document Updates Update conditions where data not available – request message supported but cannot be completed within P2 timing. For Service $04, the use of negative response code $78 for an ECU will be limited to avoid “infinite response” before a positive response message is required. Need more than 50 msec to clear DTCs in NVRAM. Clarify proper responses for all services in Table 10 and 11. Negative responses are not allowed for any services except for initialization, clearing DTCs and CVN in some limited circumstances. Added examples for various Service $09 InfoTypes. Corrected typos/language.

J1979DA Document Changes Update engine schematic to include diesel aftertreatment and EGR. Updated Fuel System definition to handle dual fuel systems. Updated PID $1C definitions (OBD Requirements) Update RUNTIM ($1F, $4D, $4E) to match new “propulsion system active” definition. Updated FUEL_TYPE ($51) to simplify implementation and removed electric vehicles. Updated FUEL_RATE ($5E) to specify update rate. Add “Recommended gear” to PID $65. Clarified language in EGR PID $69. Add HEV data PID $9A (EPA requirement). Add DEF reagent quality sensor PID $9B. Add new FUEL_RATE ($9D) for PEMS. Add Exhaust Flow Rate ($9E) for PEMS. Add fuel split ($9F) for dual fuel systems. Add new scaling bytes ($42, $43, $97, $FB)

J1979DA Document Changes Obtaining VIN, CALID and CVN from the network; what to display if data not available - ? for VIN and CALID, $00 for CVN Add several ECU names. Add Fueled Engine Operation Ignition Cycle Counter (InfoType $12) for hybrids (CARB requirement) Add Miles Since Evap Monitoring Decision (InfoType $14) for all vehicles (EPA requirement – still under discussion.) Deleted from draft, no longer under consideration –“Easter Egg” to allow vehicle to enter dyno mode. –Service $09 Battery DTC and location.

SAE J2012 Task Force report to E/E Diagnostics Committee April 15, 2013 Keith Armitage

Introduction J2012 Report April 15, 2013 Activity: – Two meetings since last report: New, Revisions, Ballot Approved – Next J2012 meeting July 19, Troy, MI – Most new DTC requests = Alternative Fuel, Hybrids, Transmissions & More Components! – Interest in common DTCs for other Body & Chassis Systems? Write

Summary Statistics Nov-06Feb-07Apr-07Oct-07Apr-08Oct-08Apr-09Nov-09 New Revised Denied Apr-10Jun-10Oct-10Apr-11Jul-11Oct-11Apr-12Nov-12Apr-13 New Revised Denied

Summary Statistics SAE P-type Codes Possible: 11,160 SAE P-type Codes Used: 5704 SAE P-type Codes Remaining: 5456 FTB sub types available: 127 SAE P-Type Tables: 44 Remaining P-Type Tables: 17 Manf. P-Type Tables: 16+4 Manf. P-Type Available: 5120

SAE J1699 Task Forces report to E/E Diagnostics Committee April 15, 2013 Mark Zachos

SAE J1699 Task Forces J (No Activity) –SAE J1850 Verification Test Procedures J –Test Cases For OBD-II Scan Tools and I/M Test Equipment J –OBD II Compliance Test Cases J (New) –OBD II Communication Anomaly List

J Overview Test Cases For OBD-II Scan Tools and I/M Test Equipment –Being updated to specify OBD II compliance test cases for Scan Tools and I/M Equipment (like a mirror image of J1699-3) –Will cover all past and present OBD II protocols –ETI, Scan Tool and I/M manufacturers, and OEM’s providing specific testing scenarios based on field experience.

J Status Document –Test cases for network initialization are defined –Simple message validation checks have been defined for ISO , ISO , ISO , J1850 VPW, and J1850 PWM –200 pages long; containing 192 test cases –Document structure allow for additional expansion in the future –In process of adding test cases that were removed from ISO –Latest draft posted on the SAE website is dated 6/14/2012 –Look for a ballot around the Fall of 2013

J Status Next meeting –May 17, 2013 from 3:00p.m. to 4:30p.m. (EST) at SAE in Troy, MI (WebEx is available)

J Overview OBD II Compliance Test Cases –OBD II compliance test cases for vehicles to validate J1979 messages and content –Revision 14.6 published in May 2012 Items being addressed: –Heavy Duty ISO has been added to the latest document (V14.92) –Software updates for Heavy Duty will come in stages with the drive cycle tests being implemented first –Minor bug fixes

J Status Document –Draft revision posted on SAE website in March 2013 Software –Latest on SourceForge is V , dated 3/5/2013 –Corresponds to 14.8 of the J document –Next update is planned for late April / early May

J Status Next meeting –May 17, 2013 from 1:00p.m. to 3:00p.m. (EST) at SAE in Troy, MI (WebEx is available)

J Overview OBD II Communication Anomaly List –Informational Report that provides a list of anomalies found in the field (input from ETI) –Where possible, the Informational Report also provides direction Scan Tool Manufacturers –Balloted in October Approve 2 Disapprove 6 Waive 17 No Reply –The document has been updated and will be re-balloted shortly –No further meetings have been scheduled

SAE J1978 OBD II Scan Tool April 13, 2013 Rich Means

J1978 Status The J1978 Document has been reformatted to more closely match the ISO document. Work is proceeding to make further revisions to the document (to account for changes made to J1979, J1699-3, etc.). The next meeting is scheduled for May 15 at DG Technologies at 1:00 PM.

SAE J2534 Pass-Thru Vehicle Communications API Task Force report to E/E Diagnostics Committee April 15, 2013 Co-Chairs:S. Prasad, DG Technologies K. Stofflet, EnGenius

J2534 Task Forces J –Recommended Practice for Pass-Thru Vehicle Programming J –Recommended Practice for Pass-Thru Vehicle Communications J –Compliance Test Cases for SAE J2534 Devices

J Report

J Overview Standard API to access vehicle networks –Required for emission-related reprogramming, but has other uses –Last publication date: Dec (Version 0404)

Rationale for Current J Updates –Some issues were reported regarding implementation differences between various vendors, resulting in OEM applications behaving slightly different with different devices –During J conformance specification work lot of ambiguities and untestable features were identified. These had to be corrected. –Some field usability issues needed to be resolved

Goals for J Updates –Tighten the J specification to ensure all features are testable –Remove specification ambiguities that could result in different interpretations –Enhance functionality to meet new reprogramming requirements –Ensure no hardware changes result from these changes –Eliminate optional features –Prohibit pop-up or other types of user interaction from within the DLL

What do the J Changes Mean to Vendors and OEMs The specification is more stable allowing for the finalizations of a good conformance test specification Vendor implementations that conform to the standard are less likely to be different, allowing vendor devices to work with all OEM applications OEMs will spend less time on validating their applications with individual J devices, and a conforming device is very likely to work with no issues The likelihood of field issues related to application/device incompatibility becomes less, leading to better troubleshooting

What do the J Changes Mean to Vendors and OEMs But…….. The new specification (Ver. 5.xx) will not be backward compatible with the current version (04/04) of J OEMs will have to make modifications to their currently deployed reprogramming tool base Device vendors will have to make firmware/DLL modifications and deploy these to the field

What do the J Changes Mean to Vendors and OEMs And…….. The deployment of the new API based application will have to be phased in, with sufficient transition time During the transition both versions may have to coexist for some time As the TF continues on the path to ballot, OEMs, Vendors and regulators need to recognize the benefits of these changes, and commit to making this transition CARB is aware of the changes and has left it up to the OEMs to recommend a transition to the new version

Status –Latest draft on SAE website dated Apr. 3, 2013 – updated draft to be posted shortly –All open issues have been addressed, document will be given a final review by Task Force at next meeting –Expect a ballot in month or so Next Meeting –May 10, p.m. at DG Technologies office in Farmington Hills MI J Status

J Report

A need was seen to support vehicles prior to the 2004 model year as well as non-emission related control modules. The SAE J document meets these needs by detailing extensions to an SAE J interface. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. J Scope

Current Document Status 10/2010 version of the document was published during week of November 25, 2010 and is now available for purchase

SAE J Update New version will be consistent with J X Ballot targeted for 3Q 2013 Eliminates _PS and _CH connect mechanisms and instead use the new connect mechanism of J Eliminates mixed mode CAN that will now be supported by J logical channel Document structure changed to make each feature its own ballotable document

SAE J Update New Features Support for CAN FD Support for DoIP Note: Message structure changes to J (fixed size array to data pointer) will now allow any data size that the above features may have to support

J Report

A series of documents that defines test cases to validate J and J devices Currently focused on validating J devices Test cases development pointed out ambiguities and incomplete requirements in J Document not yet published J Overview

Current draft includes: –749 pages; 810 test cases –Test cases cover: ISO ISO ISO 9141 SAE J1850 PWM SAE J1850 VPW SAE J2610 (SCI) ISO (Raw CAN Frames) General Features J Activities

Status –Need to account for J changes (when completed) –Latest draft on SAE website dated Oct. 19, 2009 –At current pace, may be able to ballot in Fall 2013 Next Meeting –None scheduled at this time… waiting for J changes to be completed J Status

New Document Proposal J US state of Massachusetts has passed a right-to-repair legislation, requiring OEMs to provide the after-market with dealer diagnostics capabilities Expected to go into effect by 2018 This has a potential of becoming a nation-wide trend Legislation provides OEMs an option to provide diagnostics solutions based on SAE J2534 and/or ISO (PDU API) Background: Massachusetts RTR Legislation

SAE J Update EE Diagnostics Committee authorized a ad-hoc TF to look into the requirements of R2R The TF will look into additional OEM requirements for J2534 interfaces to support their diagnostics applications The first meeting of this TF will be scheduled in a few weeks

SAE J3005 Status Remote OBD April 15, 2013 Joakim Pauli Bob Gruszczynski

J3005 Remote OBD Draft document exist J3005 Update Schedule –Next meeting on March 21st, Scope: Permanently or Semi-Permanently connected devices (was Remote OBD).

J3005 Intention limit the disturbances caused by equipment connected to the J1962 connector. Support tool vendors to make equipment which will function correctly in vehicles. Give guidelines for reducing tampering of remote devices.

J3005 Content Recommendations for: –Remote OBD (Continuous I/M) devices –Insurance devices –Portable Emission Measurement Systems –GPS –WLAN/Bluetooth-2-CAN interfaces The document supports both SAE J1979 applications and some ISO (Euro VI HDV) applications.

THE END Thank you for your attention!