

Please report any dead links
HERE
If you would like to be emailed when
there's a site update, send a blank email
HERE




|
|
 |
Don’t complicate things, it all
starts with two cables.
|
 |
Always start at the beginning.
|
 |
Assume nothing, it leads
to skipping tests. When you still have
the fault after one particular line of investigation, you'll keep wondering about
those missed steps.
|
 |
Approach each problem
car on it's own individual merit. Just because yesterday's poor runner
was an air leak, it has absolutely no baring on today's rough runner.
|
 |
Jumping to the most familiar cause of the complaint is fine as long as
you prove the fault first, be prepared with your next diagnostic route
if that isn’t the problem; "familiarity diagnostics" can be your best
friend or worst enemy.
|
 |
If you do suspect a
component has failed then I would recommend you prove it as far as you
can go.
|
 |
There are times it can be more beneficial to
form a game plan eliminating what the root fault isn’t,
rather than concentrating on what is.
|
 |
I can’t count how many times I’ve
taken out 5 minutes walking away from a problem to revitalises the thought
process. Returning with a fresh approach can really make a difference.
|
 |
If one particular
diagnostic route fails to deliver, it is still a success, now you know
what isn't causing the problem. Move on.
|
 |
Keep the thinking process
logical and methodical.
|
 |
Do your homework.
Preparation is a key factor in any diagnosis.
|
 |
It isn’t all about finding
every fault in 60 seconds flat. If the opportunity is available and
you are prepared to invest a little extra into a problem, you will have a
better equipped approach come the next similar problem.
|
 |
Always look at a problem
from the Control Unit’s perspective. What does it need to see? What is
it seeing that it doesn't
like? How does it know the difference between one condition and another?
|
 |
Don’t peg all your hopes
on a Scan Tool, electrical troubleshooting starts with a DTC but it
should never end with it. Grab the code then grab the Scope.
|
 |
Generally it is still possible to use a “no DTC
logged” condition as a clue. Look around for external influences which the system has no electrical control over.
|
 |
An Oscilloscope is very
much a self educating tool no matter what level you are at. When you
can see the fault visually it helps to understand the circuit and
it's fault a lot clearer. If you are just starting out with you're
own Scope
there isn't any mistake you can do that hasn't
already been made by me and others alike.
|
 |
Remember the greatest
tool you own is you!
Being surrounded by the best Scan
Tools, fast computers and powerful
Scopes; it all looks great but it doesn't
find nor
fix the fault. I never judge
someone's competence by the size of their toolbox or what's inside it.
|
 |
You are not being employed as a memory machine, there's nothing wrong
in writing down bits of useful findings for later. Personally speaking its the very act of
scribbling that helps me remember
for later,
strange I know but - what ever works.
|
 |
Fix as you find. I
wouldn't recommend you go any further into a diagnosis if you've
already proven a component needs replacing. Summarise after an
investigation not during one.
|
All reasonable measures have
been taken to ensure the details held within each article is correct and
reliable at time writing. All material consists of my own thoughts and
opinions. I will not be held responsible through misuse or abuse of the
information on this Web Site. Safety precautions should always be taken.
All original content and
images on this Website are subject to copyright © 2005 - 2006 HIBTECH and
may not be reproduced without proper authorisation.
|