AASHTO Subcommittee on Maintenance Vehicle Communication Standards, Issues, & Potential Solutions

1. AASHTOSubcommittee on MaintenanceVehicle Communication Standards, Issues, & Potential Solutions July 19, 2011

2. NEXIQ Technologies • NEXIQ - a brand of Snap-on, Inc. • Focused on vehicle diagnostics 30+ years. • Active in vehicle communication standards. • Technology Maintenance Council (TMC) • Co-Authored original Recommended Practice (RP1210A, B) • Society of Automotive Engineers (SAE) • Participate in various standards subgroups • www.nexiq.com

3. Standards Organizations • International Standards Organization (ISO) • Society of Automotive Engineers (SAE) • Technology Maintenance Council (TMC)

4. Standards Organizations • International Standards Organization • Focused on International standards of all types • Global & societal in scope • Non-governmental • 160 member countries • All aspects of all industries • Ex: Automotive • ISO14230, ISO15765, etc. • www.iso.org

5. Standards Organizations • Society of Automotive Engineers • Focused on global automotive industry • Autos, trucks, construction, agricultural, aircraft, etc. • Anything that has an engine and moves • Develops standards of all types for design, production, and maintenance of vehicles • J1708, J1939, J1850, J2534 etc. • www.sae.org

6. Standards Organizations • Technology Maintenance Council • Working sub-unit of American Trucking Association (ATA) • Focused on U.S. heavy duty truck industry • Develops recommended practices (RP) for HD truck design, production, and maintenance • RP1210 – Recommended Practice defining a Windows Application Programming Interface (API) for vehicle communications • www.truckline.com

7. Types of ECU Data • Public • Data accessible by anyone • Primarily government mandated data • US = Environmental Protection Agency (EPA) • Proprietary • Data accessible only by those authorized by an OEM • Ex: OEM franchised dealer

8. Different ECU Communication Standards • Automotive • Cars and light/medium duty trucks • Heavy duty truck • Class 6-8 • Long-haul, over-the-road and vocational vehicles • Off road • Construction, industrial equipment • Back hoe, loaders, gen sets

9. ECU Communication Standards • Automotive • On-Board Diagnostics (OBD-II) • SAE • J1850 Variable Pulse Width (VPW-GM/Chrysler) • J1850 Pulse Width Modulation (PWM-Ford) • J2534 – EPA mandated for reflash, but, expanded for data • ISO • ISO 9141 K-Line Interface – physical layer • ISO 14230 Keyword over K-Line – message protocol • ISO 11898-1 CAN Interface – physical layer • ISO 15765 Keyword over CAN – message protocol

10. ECU Communication Standards • Heavy Duty Truck • SAE • J1708 • J1939 (CAN) • OBD in 2013 • Different than automotive • ISO standards on European import engines • EX: DAF engine in a Peterbilt

11. ECU Communication Standards • Construction Equipment & Industrial Applications • Generally follow HD standards, but… • Most are implemented with proprietary twists • Most are unique to each OEM • Some OEMs follow no standards • Implement their own software and hardware interfaces

12. ECU Communication Standards • In its most basic form, there are: • Hardware standards • USB, WiFi, Bluetooth • Software standards to talk to the hardware • Drivers for each hardware type • Software standards to request/receive data • Public vs. proprietary • OEM specific – Protocol is same, messaging is different • ECU & model year specific

13. Example of HD Truck Communication PC or Telematic Device Vehicle Vehicle Comm Interface Hardware USB, WiFi, BT Hardware USB, Bluetooth, WiFi Device drivers Communication drivers Communication manager 1708, 1939, KW, VPW, PWM Device drivers Hardware Hardware Device drivers ECU Application Application RP1210, 2534 Device drivers Hardware

14. Interface, Communication Trends • Older specs going away • J1708, J1850, ISO9141 • New specs evolving • J1939 CAN (single and/or dual channel) for HD • ISO15765 for automotive • New, high-level layer diagnostic call spec • ISO 14229 • Universal Diagnostic Services (UDS) • Common calls across lower level protocols

15. Telematics Challenges • Data accessibility • Public versus proprietary • Different ECU communication standards across mixed vehicle fleet • No consistency, highly complicated and mixed communication • Vehicle brand, ECU type, Data type, Model year, Mixed standards • Installation is not standard • No standard connectors for telematics installation • Must break into OEM wiring causing own set of issues • Ex: J1939 - # of devices and cable length considerations

16. Possible Solutions for Telematics • Telematics industry standards for APIs • Vehicle manufacturer provide standard connector for telematics installation • Industry standards groups settle on common data set • What data parameters • What format • Frequency of transmission • Etc.

17. Possible Solutions for Telematics • AASHTO and TMC partner in joint standards committees. • EX: TMC has work group developing standard for telematics connector provision

18. Thank you Dan Doss Snap-on Business Solutions 2950 Waterview Drive Rochester Hills, MI 48309 248-613-9670 Daniel.L.Doss@Snapon.com