89 crx code 1 New o2 beating head against wall
 

ok for about two weeks i've been getting a code 1 so i figure the o2 had gone bad replaced code came back on test drive. ok so i figure bad connection i don't have a connecter on the o2 the wire runs from o2 to the harness and is soldered on both ends so i cut the wires resolder them heat shrink them and go for another test drive code comes back i am out of ideas so any help would be much appreshated

Re: 89 crx code 1 New o2 beating head against wall
 

You are clearing all the codes right? Make sure you pull the 10amp hazard fuse for like 30 secs. If you dont do that the code will still flash even if its fixed.

Re: 89 crx code 1 New o2 beating head against wall
 

ya i made sure to pull the fuse after i installed the new o2

Re: 89 crx code 1 New o2 beating head against wall
 

are you tinning the wires first? this happened to me and it was a loose connector to the dizzy and the ecu was throwing code 1 and 8(i think) when it i fixed the connection the code 1 went away. i know it is different then your situation but i would just check all the connections and see if any are loose. but if the car isn't in limp mode i would just drive it like it is.

Re: 89 crx code 1 New o2 beating head against wall
 

ya code 1 doesnt always mean bad o2 sensor. if the ecu has to correct the a/f ratio over a certain amount it will throw a code 1. (from what i can tell anyways)

Re: 89 crx code 1 New o2 beating head against wall
 

put my voltameter on the o2 to check the voltage 0.4 at ideal and 0.6 at wot so i now the o2 is good and for the hell of it i put a new fuel filter figured the one from 89 was probley a little dirty but the code came back could it be the fpr maybe

Re: 89 crx code 1 New o2 beating head against wall
 

heres a list of things i would check

spark plugs
plug wires
injecter wires
fuel pressure
dizzy wires

it sound like there is a problem that the ecu cant corect so it is throwing a code 1 because it is assuming everything else is working properly and has nothing else to blame the problem on