I have a 2009 ultra classic that I bought last year with Vance and hines twin slash oval mufflers already on it but not tuner. I installed xieds for a short time which caused o2 sensor codes which is normal when you run xieds. I ended up getting a vance and hines fuelpak and took the xieds off and cleared the codes. I checked a few times afterwards and the codes didn't come back. Yesterday I washed the bike with a hose in the driveway trying not to spray water directly on anything electrical and when I tried to start it afterwards, it would only run for a couple seconds and sounded like it was running on 1 cylinder. I checked and there was a po132 and po152 code. I was able to get the bike running right and cleared the codes. Went for a 70 mile ride today and the codes came back.
Do you think the xieds could have caused issues with both o2 sensors or maybe the connectors for the o2 sensors got wet from washing the bike?
The bike has 99,600 miles on it so I'm wondering if the o2 sensors just need to be replaced.

Thanks for your suggestions.

 

If the bike was cold when you started it, it shouldn't be an o2 issue. I don't believe the bike runs in closed loop until it warms up, so at least 60 seconds or so. If I'm wrong saying that, sorry. I'll be corrected VERY quickly, lol. Good luck with your issue, hopefully it's something minor.

 

I was wondering if maybe I got the coil wet which caused the misfire , which allowed unburned fuel to pass through and get onto the o2 sensors causing them to go bad.

 

The likelihood of two sensors going bad all at once is no way. Those error codes going on in both cylinders usually means not enough air going in. Did you happen to get the air intake filter wet? Is it gummed up?

 

I checked the air intake and there was a small amount, maybe a soda bottle cap full, of water in the bottom of the housing but the k&n air filter felt dry. Before I got it started, when I was trying to start it, there was a couple times that it backfired through the intake and smoke came out of the intake.

 

I cleared the codes lastnight and just went for a 20 mile ride and there is only the po152 code for the rear cylinder. The po132 hasn't come back yet.

 

I'm not sure what is going on. I rode the 20 miles like i said and the po152 code came back but not the po132. I cleared the code and went another 20 miles and both the po132 and po152 came back. Cleared the codes again and went another 30 miles and just the po152 came back, not the po132. Cleared that code again and went another 25 miles and only the po152 came back, not the po132.

 

Well with PO132 and PO152 popping-up telling you that both front and rear O2 are running high/rich, you are likely dealing with a tuning module issue. It's unlikely that the O2 sensors are damaged by the xieds or the water. Xieds are little more than resistors that reduce voltage to the O2 sensors. Just think, riding down the road in the heavy rain, you don't think the O2 sensors will fail do you? No, they won't, they are sealed.

You might have introduced water in the connection up at the fuel pak during washing. Remove the connector, make sure all is dry, and you might want to dab in a little dielectric grease to keep the pins protected from oxidation. The fact that you are now getting only the PO152 code may indicate that things are drying out as you ride.

 

Ok. I took the seat off lastnight and didn't see any signs of moisture at all. I hope something just got wet and it's taking this long to dry out. The o2 sensors are $53 a piece.

 

I would have to agree with Joe. Could very likely be a tuning issue. I don't know a whole lot about the FP, but can you put it back to a stock flash and go for a short drive to see what happens? You don't have enough mods to hurt anything and that will narrow down the possibilities if nothing else.