On the road: need engine warning codes

[Aasland]

So I've come down from the Bighorns and right before I get to Cody, WY the check engine warning light comes on.

I turn off the engine (kill switch) and the display shows a 32 or 35 (don't remember which). Bike starts again and runs fine (sort of .. more later). Not overheating, not missing, plenty of power. Five minutes later the light goes out. Hm.

Stop in Cody, get on web, pull codes (16,3,158) and search forum. No 32 or 35. Forum says: look in the manual. I'm on the road .. and don't have a manual.

If any of you have a manual .. can you post what the codes 32,35,16,3,158 are for?

Last weekend I did an oil change, valve adjust and TB sync. Home is in MN (elev 500). Bike ran fine, strong, smooth, etc. Get out west, first in the Black hills (elev 3000-4000) and top gear roll-on's cause it to bog down a little - from 3500 to 4000 rpm. Note that I have a PC3 with the O2 sensors disconnected, and can switch maps. The bog isn't noticeable when on the standard map for a no-mod bike, but it is when on the zero map (I run the zero map when cruising as it gets 10-15% better fuel economy).

I have the updated ECU.

For those of you in higher elevations .. is the midrange bog typical when running at higher elevations? I'm tempted to decrease the fuel from the PC3 in the midrange.

Thanks again for your help!

 

[ionbeam]

Gen I and Gen II Codes

No code 35 or 158. Code 32 "air-fuel compensation is...rich" Could be: harness, ECU, fuel pressure, O2 sensor, injector or 'other'. Not particularly helpful on the road. I have to ask the ubiquitous question, could it be bad gas?

 

[Bogey907]

It sounds like the ECU adjusts the mixture using the O2 sensor when it detects air density changes. And that doesn't work when the O2 sensor is disconnected.

 

[ionbeam]

...that doesn't work when the O2 sensor is disconnected...

The PCIII is supposed to work with the O2 disconnected. The ECU only works in 'closed loop' a small percentage of the time.

Sometimes, some bikes will throw a code related to the O2, but still runs fine. In this case there is mid-range bogging, which is not normal. Since the engine is out of a 'closed loop' mode, it should run fine using look-up FI maps.

Start your troubleshooting simple. Sudden onset isn't a usual symptom of a serious problem in most cases. Radio Howie excepted.

 

[BwanaDik]

Possible onset of the dreaded grounding pin connector corrosion? He does have an '06

 

[Aasland]

Home again. Thanks for getting the codes - it was indeed a 32, and knowing it was related to parts not hooked up, I decided to ignore the problem and continue my trip (thanks for the codes!)

I never had the chance to lift the tank to look at connectors and hoses. Eventually the light went out for a couple tanks, then came back on 4-5 times per tank the remaining 6k of the trip (i.e. it wasn't a fuel quality issue).

Now that I'm home I get to start the debugging problem (after I hammer out the big dent in the front rim from a big pothole on Matole Road ..grrrrr... Cali DOT can build some great roads, but they need to learn how to maintain them).

 

[Aasland]

I did get under the tank, and saw that I had indeed hooked up the O2 sensor, when I shouldn't have. Dangit.

Still haven't fixed the rim .. so haven't had time to see if reconnecting that worked.