AutoInc. Magazine
   
MAGAZINE
Home
Current Issue
Ad Index
AutoInc. Archive
How to Contribute
Reprint Permission
RSS
READER SERVICES
Subscription Info
Letters to the Editor
ANNUAL FEATURES
Top 10 Web Sites
Software Guide
NACE Online Daily News
How's Your Business?
ADVERTISING
Ad Opporunities
Media Planner
ABOUT AUTOINC.
AutoInc. Mission
Meet Our Staff
  Tech to Tech

The Most Important Diagnostic Tool

Posted 5/10/2004
By Brian Manley

Strategy-based dynamics helps techs develop
a methodical process to troubleshooting.

Figure 1As an automotive instructor, I teach my students system theory first. Next, I teach them how to apply that theory to a good system. Finally, they learn how to apply that knowledge when faced with a system that is not operating as designed. I also remind them often about which diagnostic tool is the most important one.

Case in point: a Ford Explorer with an antilock brake system (ABS) lamp that is illuminated (Figure 1). The customer who had this problem came to us through one of my second-year students, Gary, who has gained a reputation around school as a guy who knows how to fix Fords. He developed this reputation from being an apprentice at a local Ford dealer for two years, and from working on many students' vehicles on the side. He is also becoming a better diagnostic tech with each passing month. He is one of several outstanding students who are gaining an understanding of strategy-based diagnostics.

Strategy-Based Diagnostics

Figure 2
Figure 2 - Codes 11, 32 and 36 on the scan tool.
General Motors developed strategy-based diagnostics because their technicians needed help with vehicle diagnosis. I teach the following process to my students to help them become more successful troubleshooters.

  • Step 1: Verify the customer concern. A technician needs to know how the system is supposed to function normally before deciding that the system is malfunctioning. A thorough customer interview, or a diagnostic worksheet filled out by the customer, is necessary before troubleshooting can begin.

  • Step 2: Preliminary checks. Operate the suspect system, and evaluate its performance. Perform a thorough visual inspection of all components, including fuses, connectors, grounds and harness routing. This is also an ideal time to pull up the service history on the vehicle.

  • Step 3: Perform published diagnostic system checks. If there is a published diagnostic procedure that will help you narrow down the cause of the problem, use it first.

  • Step 4: Check for bulletins. If you have access to published service bulletins for the vehicle, search those for a possible fix. This can save a lot of time in the long run. I also print safety bulletins for my customers at this point, as an added value.

  • Step 5: Stored diagnostic trouble codes (DTCs) and symptoms with no DTCs. If there is a hard trouble code, you're lucky. If you have a repeatable symptom, you're equally as lucky because both options will quickly help you narrow your focus.

  • Step 6: No published diagnostics. When there is no DTC stored and no matching symptom for the condition in the service manual, you will have to develop your own diagnostic process based on your understanding of how the circuit operates. This is the time when there is no substitute for advanced systems training.

    With the Explorer in our bay, Gary had already verified the customer concern: The ABS lamp was illuminated at all times. Gary's first instinct was to grab the scan tool and probe the ABS module. Fifteen minutes later, after running key-on engine off (KOEO) and key-on engine running (KOER) tests, Gary had a hand full of trouble codes (Figure 2):

    • 11 Defective electronic control unit (ECU)
    • 32 Right Front Sensor Electrical Failure
    • 36 Erratic Right Front Sensor Output
    • 41 Erratic Front Left Sensor Output
    • 42 Erratic Front Right Sensor Output
    • 67 Pump Motor
    • 75 Erratic Front Right Sensor Output
    • 76 Erratic Front Left Sensor Output

    I know where I would have started with this Ford - right or wrong. I would have looked to see why the ABS ECU was so unhappy with the front speed sensors. But, as I've become a better instructor, I've also become better at letting students discover their own diagnostic routine. When I am smart enough to step back and simply facilitate the learning process - instead of showing the entire procedure - students often learn more by meandering through testing and discovering their way to the correct diagnosis.

    Figure 3
    Figure 3 - ECU failure chart.
    Gary investigated the code charts to get an idea of what may lay ahead of him. He also checked for pertinent technical service bulletins (TSBs), but none applied to our situation. Beginning with code 11, Gary saw, quite possibly, the shortest diagnostic trouble tree (Figure 3) of his short career:

    SERVICE CODE - 11
    COMPONENT - ECU Failure
    PINPOINT TEST - Replace ECU

    At this point, I strongly urged Gary to perform a thorough inspection of all brake system components, right down to the friction material. I stressed the fact it has been my experience that ECUs are usually not faulty, but they do fail occasionally, and we should keep this fact in mind. When faced with a "fatal error" type of code, I explained, always search for peripheral causes, which are cheaper to fix than taking the code charts for gospel and throwing ECUs at the problem. Further, we cover electrical signals in our first quarter each year, and if the ECU was claiming that there was an erratic wheel speed sensor, I fully expected Gary to back-probe each sensor with a lab scope and either confirm or deny that fact.

    As an added benefit to our customers, we also check steering and suspension components, leaks, belts and hoses and fluid conditions. I try to instill a sense of ownership with my students - to treat each vehicle as if their mom were driving it out of town on a long trip.

    Figure 4
    Figure 4 - Corrosion on the battery terminal and ground wires.
    We had already noticed the science experiment taking place inside the battery cable. So we questioned whether or not that corroded ground lead (Figure 4 ) could possibly have something to do with our multiple trouble codes. We both agreed it certainly wasn't an optimal connection and proceeded with the inspection.

    Gary got the vehicle into the air, where we immediately began inspection of both wheel speed sensors for the front wheels, due to the multiple codes pointing in their direction. The picture of the ABS wheel speed wire against the wheel (Figure 5) shows what we initially discovered. Could this cause the ABS ECU to freak out? Absolutely! Upon closer inspection, we discovered that the edge of the wheel had rubbed right through the speed sensor's insulation, into the copper wire strands, creating an "erratic" connection to ground.

    Figure 5
    Figure 5 - The ABS wire rubbed through on the wheel edge.
    I asked Gary, "Can you see why the speed sensor wire is rubbing against the wheel?" As I recall, he found the root cause after staring at it for awhile. The last brake tech had twisted the brake caliper 360 degrees before reinstalling it. The stress of this twist had pushed the sensor wheel out toward the wheel, sealing its fate.

    We inspected the rest of the brake system and found no other hose twists or worn-out friction lining, so Gary broke the news to his customer.

    Pointing Fingers

    The customer was informed of our discovery. She then told us that a local brake specialty chain store had recently replaced the front brakes. The next day she told us that their response was, "We couldn't have twisted the brake hose." I gave her my card and asked her to tell them to call me so I could explain the situation; otherwise, they were responsible for repairing the damage to the speed sensor wires. I never received a call, and the Explorer was repaired by the chain store.

    The Most Important Diagnostic Tool

    Once again, using our most important diagnostic tool found the root cause of another customer concern. Properly functioning sensor inputs into this tool (sight, sound, smell and touch) are critical for the read-only memory (ROM), electronically erasable programmable read-only memory (EEPROM), and random access memory (RAM) circuits - grey matter - to function properly. Proper "feeding" (technical update training) and "watering" of our most important diagnostic tool will help keep it fully functional for years to come.

    Jeff Bach Brian Manley is a vocational automotive instructor for the Cherry Creek school district in Aurora, Colo. He is an ASE master certified automobile technician and a former member of the National Automotive Technicians Education Foundation (NATEF) board of trustees. He can be reached at manley_brian@hotmail.com.


    share your thoughts...

    RATE THIS ARTICLE

    What do you think of this article? Your input will help AutoInc. develop additional articles on this subject. Share your thoughts!

    Your name

    Your e-mail address

      

    MOST ACCESSED ARTICLES

  • Fuel Injection Service, Not Just Cleaning
  • The Art of Extraction
  • EGR Systems: Operation and Diagnosis
  • Proactive Target Marketing:_Rethinking Your Business Strategy
  • Engine Performance: HO2S Diagnostics

    MOST E-MAILED ARTICLES

  • Developing Employee Potential
  • How Critical Thinking Can Help Your Business
  • How to Diagnose the Ford Glow Plug
  • What to Look for When Shopping for the Right Shop Management Software
  • Putting a Price Tag on Complaints
  • AutoInc. Web Site | ASA Web Site | Congress Focuses on Clean Air Reforms | History and Future of On-Board Diagnostics | Measuring Success: How CSI Technology Can Improve Your Bottom Line and Turn Customers into Advertisers | The Keys to Freedom - Escaping from the Tyranny of Business Ownership | Guest Editorial | Tech to Tech | Tech Tips | Around ASA | Shop Profile | Net Worth | Stat Corner | Chairman's Message

  •  
    Copyright (c) 1996-2011. Automotive Service Association®. All rights reserved.
    XML Add RSS headlines.