1. OBD and Safety

2. Drew Technologies Founded and incorporated in 1996 Core focus on vehicle communications and diagnostics Customers divided among 3 business groups: OEM, Aftermarket, and Emissions Engineering, Manufacturing, and HQ in Ann Arbor, Michigan Over 20,000 vehicle communications products delivered to OEMs, dealerships, smog shops, and the aftermarket last year

3. Safety Inspections Today Founded and incorporated in 1996 How things work today – Car comes in for safety inspection – OBD tool is plugged in to read out VIN – Technician is directed to perform visual inspection and mechanical tests – Car is determined safe or not safe

4. Missed Opportunity Founded and incorporated in 1996 – During this test, we are connected to the car’s Onboard Diagnostic System – Yes, it’s called “On Board Diagnostic” system. And we aren’t asking it for any diagnostic information – Why?

5. Safety thru OBD Founded and incorporated in 1996 The D in OBD is Diagnostics Onboard vehicle computer systems have been used for diagnostics, even before OBD emissions testing: – By OE engineers/calibrators – Dealerships – Repair shops

6. Diagnostic Capabilities There are hundreds, sometimes even thousands of diagnostics tests run by each ECU Some cars have > 100 ECUs Some tests are automatic and trigger trouble codes Other tests are user directed: – bi-directional controls – cylinder balance test – etc

7. What can we get? The car can tell you more about itself than a visual test can determine Many modules can contain their own self- tests and trouble codes related to Powertrain, Body, Chassis, and Network Many of these trouble codes may not illuminate the dash light!

8. What can we get? Examples of things that may set a code, but not a light – Chevy Cruze, tail light burnt out DTC – Cadillac CTS-V power steering DTC, inop in cold weather – ABS Module – wheel sensor not working – Brake Systems – brake fluid low – Lane departure warnings – camera not working – Stability control – yaw sensor – Dashboard – Temp Sensor – Tmps – tire pressure low – Airbags – occupant sensor not working – Electrical – battery is degraded

9. Bus Analyzer Check the “BUS” for proper voltage and module communications GM’s example:

10. Challenges Getting diagnostic information out of ALL ecu’s does require scantool experience and software development from the vendor. In certain vehicles, you may not be able to get access to all modules on the vehicle because some non- powertrain systems are separated out onto separate physical networks. You can still get a lot of data.

11. Recommended Practice When you plug that OBD interface in, read more than VIN Read all modules, list all trouble codes on safety report After you collect data and start studying it, determine if you want setup some criteria for automatic fail. Vehicles should not have any trouble codes Grow the test to manufacturer specific items as needed

12. Benefits Benefits to state, contractor, motorist, general public – You are already plugged into OBD, why not give them a list of diagnostic codes – You capture these codes before the inspection starts. Great snapshot of vehicle health before it’s touched by a technician – Will make cars safer.

13. Resources You can purchase an OE scantool and conduct some tests to see how often trouble codes exist To integrate this into your IM system, you may need to reach beyond typical IM contractors to scan tool companies Drew Technologies holds patents pending related to OBD safety, simulation, and vehicle interfaces that can be licensed

14. Questions? Brian Herron Drew Technologies, Inc bherron@drewtech.com Phone: 734-222-5228 x602 Brian Herron Drew Technologies, Inc bherron@drewtech.com Phone: 734-222-5228 x602