ZR-1 Net Registry Forums - View Single Post - '91 missing and would like a second opinnion

Paul Workman · 03-30-2010

Initially, the suggestions were in line with what I might have suggested, so I kept quiet to see what the results were. But, after reading the thread, a couple things come out which may be more the result of putting stuff in writing, so take this with a grain of salt, if I'm off base:

Troubleshooting: One of the deadliest traps one can get into is to assume something or another can't be the problem because it was recently replaced with a new item. I read this several times in this thread, and so I raise it as a flaw in the logic. A technique that has saved my bacon many times is to assume NOTHING about the condition of a device is known unless it is tested!! You might be well served to step back and then proceed to test functionality of components in question and forget about when it/they were replaced. (In fact, one of my new - out of the box - Airtex fuel pumps had bad check valve resulting in a failed leak-down test. I had to isolate the pump to determine the problem (more on that later, if you want - got pictures showing how that is done).)

The other is putting a scanner on it or a computer and data logging to see what is going on. Problems leading me to buying my own scanner stemmed from "no codes thrown" condition, yet ran like chit (and a "no problem found" from the dealer's mechanic) In one case one of the O2's was shorting out after reaching about 3000 rpm, but it wouldn't do it all the time. Try to run THAT down without a scanner! My point is, a scanner and data logging will show you what is really going on over 40 some sensor and readout results and time stamp them all so you can see the interaction.

Hope this doesn't sound "preachy". Just that I'm late for work - gotta run!!

Mo later if ya need.

P.

03-30-2010	#50
Paul Workman Join Date: Nov 2007 Location: Squires (near Ava MO in the Mark Twain N'tl Forest) - Missouri Posts: 6,466	A couple observations... Initially, the suggestions were in line with what I might have suggested, so I kept quiet to see what the results were. But, after reading the thread, a couple things come out which may be more the result of putting stuff in writing, so take this with a grain of salt, if I'm off base: Troubleshooting: One of the deadliest traps one can get into is to assume something or another can't be the problem because it was recently replaced with a new item. I read this several times in this thread, and so I raise it as a flaw in the logic. A technique that has saved my bacon many times is to assume NOTHING about the condition of a device is known *unless* it is tested!! You might be well served to step back and then proceed to test functionality of components in question and forget about when it/they were replaced. (In fact, one of my new - out of the box - Airtex fuel pumps had bad check valve resulting in a failed leak-down test. I had to isolate the pump to determine the problem (more on that later, if you want - got pictures showing how that is done).) The other is putting a scanner on it or a computer and data logging to see what is going on. Problems leading me to buying my own scanner stemmed from "no codes thrown" condition, yet ran like chit (and a "no problem found" from the dealer's mechanic) In one case one of the O2's was shorting out after reaching about 3000 rpm, but it wouldn't do it all the time. Try to run THAT down without a scanner! My point is, a scanner and data logging will show you what is really going on over 40 some sensor and readout results and time stamp them all so you can see the interaction. Hope this doesn't sound "preachy". Just that I'm late for work - gotta run!! Mo later if ya need. P.