Very slight hesitation
#6
LoL, you should just put in your signature "run a koer test" thats your favorite saying. I checked for vac leaks and didnt see/feel any, the only definate leak I have is in the exhaust where the intermediate pipe meets the tailpipe section, a rather large one too. I have to get that welded together and then Ill go from there. In the mean time ill run a koer.
#7
first:Understand customer complaint = Here I rely on your ametuer ability to explain the issue
second: verify complaint through a visual or test drive and after that based on what I properly interpret the situation to be, I perform a visual if need be of the car and under the hood.
Third if visual reveals nothing, ALWAYS USE whatever vehicle self diagnostics are availible and use them properly.....problem here is most deem this function useless cause they fail to comprehend it's design, purpose and function....hence we see 3-4 pages on a thread of a "I'M LOST"
4th if koer reveals nothing based on what causes a hesitation/misfire I look at components that cause incomplete combustion = hesitation/misfire.....often times a hesitation off Idle is a lean spot, on a efi car it could be a glitch in the tps, vaccum leak, faulty ignition parts/components, faulty o2 readings, exhaust leaks before o2's that'll skew readings, weak spring in egr valve causing pintle to lift,ect ect
To be a good diagnostician one must develop a strategy that always yields results and once you have one, don't deviate from it or risk becoming lost in the process
Last edited by mjr46; 03-23-2009 at 09:22 PM.
#8
YOU KNOW WHY???.......PROPER troubleshooting begins with:
first:Understand customer complaint = Here I rely on your ametuer ability to explain the issue
second: verify complaint through a visual or test drive and after that based on what I properly interpret the situation to be, I perform a visual if need be of the car and under the hood.
Third if visual reveals nothing, ALWAYS USE whatever vehicle self diagnostics are availible and use them properly.....problem here is most deem this function useless cause they fail to comprehend it's design, purpose and function....hence we see 3-4 pages on a thread of a "I'M LOST"
4th if koer reveals nothing based on what causes a hesitation/misfire I look at components that cause incomplete combustion = hesitation/misfire.....often times a hesitation off Idle is a lean spot, on a efi car it could be a glitch in the tps, vaccum leak, faulty ignition parts/components, faulty o2 readings, exhaust leaks before o2's that'll skew readings, weak spring in egr valve causing pintle to lift,ect ect
To be a good diagnostician one must develop a strategy that always yields results and once you have one, don't deviate from it or risk becoming lost in the process
first:Understand customer complaint = Here I rely on your ametuer ability to explain the issue
second: verify complaint through a visual or test drive and after that based on what I properly interpret the situation to be, I perform a visual if need be of the car and under the hood.
Third if visual reveals nothing, ALWAYS USE whatever vehicle self diagnostics are availible and use them properly.....problem here is most deem this function useless cause they fail to comprehend it's design, purpose and function....hence we see 3-4 pages on a thread of a "I'M LOST"
4th if koer reveals nothing based on what causes a hesitation/misfire I look at components that cause incomplete combustion = hesitation/misfire.....often times a hesitation off Idle is a lean spot, on a efi car it could be a glitch in the tps, vaccum leak, faulty ignition parts/components, faulty o2 readings, exhaust leaks before o2's that'll skew readings, weak spring in egr valve causing pintle to lift,ect ect
To be a good diagnostician one must develop a strategy that always yields results and once you have one, don't deviate from it or risk becoming lost in the process
#10
I havent done a computer check on an obd1 since....forever ago. I remember I had a hard time getting the same reading from check to check. I was using an obd1 scanner, which i still have, and not reading the cel. It would throw codes like 21, then 17 the next time, and 36 the time after that. Is there a procedure for reading the beeps/flashes that I was doing incorrectly?