got the car dryed out and cleaned up.

checked the oil, no water.

started it up and went out for a drive, and 1 mile down the road it started bogging at lower rpm...1500-2000

then the SES started flashing, but did not stay on after that. happened several other times before i got home.

scanned it and got the "o2 sensor Bank 1, sensor 1 high voltage"

and looking at the readings it was reading...or seemed to be pegged at 1107mv while at idle, while the other side was fluctuating from 200-400mv. the percentages for the STFT and LTFT were both 0% for bank one, while bank two was STFT 0% and LTFT 3.9%

now the water (salt water) was high enough to submerge the exhaust and being true duals the water was inside i'm sure. so i'm thinking it's messed up one of the sensors. i'm gonna pull the connector to see if it was corroded.

but i just wanted to run this buy you guys to see if that type of reading on one o2 sensors would cause the bogging and the flashing SES.

thanks

 

oh...and after a few miles of driving, and several separate SES flashing events....the car seemed to smooth right out.

it was after this that i got it home to scan it.

think it had something to do with open/closed loop??

 

I always thought flashing SES was a misfire? High voltage is usually the sensor just crapped out, it should be able to handle some moisture but not being submerged like you said. You can always unplug it and test for power and ground on the harness if you want to check out the wiring.

 

have fun once a car gets wet like that u will chase problems all day....

 

I say reset the codes and drive it and see what it does.

How high was the water? I didn't figure you had any trouble this storm. Should have jumped in the car and headed to central FL! We never get hurricanes!

 

"Should have jumped in the car and headed to central FL! We never get hurricanes!"

preaching to the choir

ok...monday morning update.

car started up fine, drove fine with no SES for about 2 miles (till it warmed up). then it immediately started bogging, sounded like missfiring and the SES flashed.
THIS TIME the light stayed on. gotta wait till tonite to pull the codes at home.

now this is strange....after 1/2 mile of bogging and missing...the car drove fine for the next 3 miles to work. no problems at all.

i'm still thinking it is the O2 sensor since that was the obvious code yesterday, and that the scanner showed the sensor almost pegged on mV.

gonna check the plugs and wires today...but the water didn't get that high.

after i pulled the seats to dry the carpet, i found a waterline on them. the water was just over the bottom of the back of the front seats. just enough to submerge (and short out) the power motors under the driver seat.

i think at that height...nothing major should have been under water in the engine bay. but i'll check anyway...again.

i guess i still haven't heard a YES or NO as to whether a pegged 02 sensor will cause a misfire.

 

Remember.... the sensors need to be exposed to air on the outside of the membrane to get the correct voltage reading. The air gets to the outside of the membrane by entering through the hole where the wires are. If you have water in there, its not going to generate the correct voltage. Its possible it could dry out, but it might leave behind salt particles.

Virtually any electrical plug and device that got submerged is suspect. If the water is still in the connectors, its a problem. If the salt corroded the connectors, its a problem.

Given the high water mark on the seats, how high do you think it got on the engine?

 

i don't think it got much higher than that.

there was no perceivable line in the engine bay, and the cars that were just a bit higher in the lot didn't even have water inside. so i think it only got to the seats.

i'm gonna pull the connectors and inspect them tonite, most likely swap in a new sensor for the one i got the code for.

i figure i'll check the plugs and wires while i'm getting dirty.

my other thought is that maybe the fuel pump or one of the connectors got corroded...droping pressure.

but first things first...fix the messed up sensor.

i'll keep you posted

 

I would be very interested to see if you're popping a P0300. I'm not as up to snuff on OBDII stuff as Fred and Teke, but if you guys saw a thread started by Keliente recently, about the H2O-related misfire, maybe you can solve our headaches as well. I never threw any O2 codes, just the random mis code, but unfortunately I don't have a scanner to see what my O2's are reading. What do you guys use to monitor these voltages anyway? Autotap? Is that software or hardware?
Edit: Teke, those 'cane pics are nuts. I had no idea you guys got hit that hard. Them some big trees knocked down!

Abe

 

well pulled the b1s1 o2 sensor....

one of the electrodes in the sensor side of the plug was corroded green

swapped in the new one after cleaning out the engine side of the plug. took it for a spin and the car drove normal.

we'll see what happens after a nite of cool down.

crossing fingers

 

Cool.

Next cane drive north. Plenty of places you could crash. Oops, I mean no more hurricanes!

 

drove fine to work this morning....think i fixed it.

[knock on wood]

now i just have to figure out what to do with the fried power seat slider

 

It is. A failed o2 can cause a misfire...the computer tries to add a ton of fuel to compensate for the bad sensor and causes the engine to run super rough (misfire). The reason his car drove fine for the first couple minutes was because it was still in open loop, where the car is not relying on sensors to make adjustments.

 

thats what i thought..

BUT..

why after 1/2 mile of running like **** did it suddenly smooth right out and run fine for the next 4 miles?

 

b/c the computer figured that something was up in CL so went back to OL. Every once in a while it will try to get back to OL, which is when it will suddenly start acting up again.

Just out of curiosity, did it store any of the misfire codes? P0300 is random miss and p0301 would be cyl 1, up to p0308 being cyl 8. Curious if it picked individual cylinders to shoot misfire codes and if they were all on the affected bank, or if it just spat out the p0300.