Electric spark timing - low voltage detected

Garryowen

Deceased
That was the books interpretation of the code for the "check engine" light on the dash of my 84 Chev. 1500. It has A/c and 5.0 L. gas engine. I understand there should be a disconnect that will allow one to reset the timing, but am unsure just which of the connections that would be. There is one involving two wires: a green one (I'm thinking grd, but maybe that isn't correct) and one that is brown and white. That connector is clipped to the firewall, and the wires come out of the wiring harness going both directions.

We had one code that indicated the O2 sensor was bad, and replaced it.

Any insights would be much appreciated. I won't be back until after sunrise.

TIA

Garryowen
 

Garryowen

Deceased
Pick-up coil, under the rotor?

It seems to be in one of those sensor circuits. We really need to get the schematic for the wiring to even find what they are talking about. According to the book the current seems to be controlled by a knock sensor. I'm going to try to find the proper book for that year. We are trying to figure it out with a book for a previous year, and sometimes it may as well be for a foreign car if you don't have the right year.
 

Publius

TB Fanatic
Ok; you replaced the sensor and you should disconnect the battery for about min then reconnect! This will reset the computer and the engine may (but not always) run a little funny for the first 5 min of travel as it go's threw a relearning stage. Try that and see if the check engine comes back on if it does, do the code thing again and see what comes up with.
 

Garryowen

Deceased
Ok; you replaced the sensor and you should disconnect the battery for about min then reconnect! This will reset the computer and the engine may (but not always) run a little funny for the first 5 min of travel as it go's threw a relearning stage. Try that and see if the check engine comes back on if it does, do the code thing again and see what comes up with.

Yes. We did that, and the light still comes on and we get the same code. But it is no longer saying that the O2 sensor is bad. (that sucker was about 75 bux).

Hardpan, I copied the information from your link. We will check the connection first. We had a suspicion that maybe that could be a problem. That link looks like just the kind of thing we needed. Will probably attack it again sometime this week.

Thanks for your help, everyone.

gratefully,

Garryowen
 
Top