I agree- odd.  I have never had the F1 error except while cruising at high speed.  Every post I have seen about the mysterious, "instant" F1 errors has been while cruising.  Never when in idle or stopped, etc.  Plus, his didn't sound instant (like 1 sec or less), so there might be something else going on.

I have, twice.

I've documented 12 FI errors on my bike since new, and it's now over 22,000 miles:

298 miles and got a brief FI error.  Outside air temp was about 60F, half tank of fuel, the RPM's had peaked around 5K just before I closed the throttle, sunny and dry.
434 miles, another brief FI error.  Sunny, dry, 65F, transitioning from rural to suburbia, Full tank of fuel, short shifting to 3rd.
1543 miles, another brief FI error.  This time, it happened while coasting to a stop in OD, at about 2200 RPM's.  Weather was clear, 65F, full tank of fuel.
1837 miles, another brief FI error.  This time it happened while steady speed cruising in OD at 70MPH.  Weather was 64F, dry, overcast, about 1/4 tank of fuel.
6680 miles, brief FI error, middle of nowhere (central WY desert), cruising at 80+ in OD, 90+F.
10125 miles, brief FI error, downtown PDX, late evening, 1st gear driving through an intersection, 64F, 2/3 tank of fuel,
14896 miles, brief FI error, inside Sylvan tunnel (PDX, US26), 8:30PM, 61F, coasting downhill in 4th gear @ 50MPH, just about to short shift to 6th, 2 bars on the fuel gauge.
16,284 miles, brief FI error, stop sign at Woodard Rd (Springdale side), 8:00pm, 64F, full tank of fuel, on a down hill doing a quick stop and go at a stop sign, just downshifted to 1st, abrupt off to on throttle change,
19188 miles, brief FI error, NW PDX, sitting stopped at light, EB NW21st & Lovejoy, 70F, full tank, 7:30pm.  Didn't turn on red light, but did screen swap 4 times (2 each screen).
21663 miles, brief FI error, PDX, sitting stopped at light, WB 181st & Sandy, 55F, Full tank, 10:30am.  No read light, just caught a glimps of it.
21825 miles, Another FI error, EB US26 @ Cedar Hills cruising at 70MPH, 6th gear, a couple minutes before low fuel came on, 55F, 12:45am, red light flashed twice.
21943 miles, Another FI error, HCRH South of Stark St. bridge almost to Springdale, 50MPH, low fuel on, 50F, 8:45pm, it turned off Red light (was on after clearing low fuel warning).

They did seem to taper off after tightening up the throttle cable slack a couple different times, though that could have also been a coincident.

Yeah, that documentation is a little light- we are going to need the direction the bike was pointing toward in each instance, as well as the phase of the moon to make any type of useful guesses.

What do you do, ride with a notepad open and a pencil in one hand?

Brian

I have, twice.

I've documented 12 FI errors on my bike since new, and it's now over 22,000 miles:

<snipped tabulated data>

They did seem to taper off after tightening up the throttle cable slack a couple different times, though that could have also been a coincident.

Yeah, that documentation is a little light- we are going to need the direction the bike was pointing toward in each instance, as well as the phase of the moon to make any type of useful guesses.

What do you do, ride with a notepad open and a pencil in one hand?

Brian

Yeah, that documentation is a little light- we are going to need the direction the bike was pointing toward in each instance, as well as the phase of the moon to make any type of useful guesses.

What do you do, ride with a notepad open and a pencil in one hand?

Brian

Gotta admit, Brian, he's good.

Good nothing, that is fantastic! No dealer could resist such documention- they would give in and just give him a new C-14 before he was one- half way through that list.

 

Brian

Gotta admit, Brian, he's good.

Wow! I have similar miles but have only seen 3 or 4 F1 errors. But I'm sure there have been others. It is so brief that unless you are looking at the screen at the time you would miss them.

I have, twice.

I've documented 12 FI errors on my bike since new, and it's now over 22,000 miles:

298 miles and got a brief FI error.  Outside air temp was about 60F, half tank of fuel, the RPM's had peaked around 5K just before I closed the throttle, sunny and dry.
434 miles, another brief FI error.  Sunny, dry, 65F, transitioning from rural to suburbia, Full tank of fuel, short shifting to 3rd.
1543 miles, another brief FI error.  This time, it happened while coasting to a stop in OD, at about 2200 RPM's.  Weather was clear, 65F, full tank of fuel.
1837 miles, another brief FI error.  This time it happened while steady speed cruising in OD at 70MPH.  Weather was 64F, dry, overcast, about 1/4 tank of fuel.
6680 miles, brief FI error, middle of nowhere (central WY desert), cruising at 80+ in OD, 90+F.
10125 miles, brief FI error, downtown PDX, late evening, 1st gear driving through an intersection, 64F, 2/3 tank of fuel,
14896 miles, brief FI error, inside Sylvan tunnel (PDX, US26), 8:30PM, 61F, coasting downhill in 4th gear @ 50MPH, just about to short shift to 6th, 2 bars on the fuel gauge.
16,284 miles, brief FI error, stop sign at Woodard Rd (Springdale side), 8:00pm, 64F, full tank of fuel, on a down hill doing a quick stop and go at a stop sign, just downshifted to 1st, abrupt off to on throttle change,
19188 miles, brief FI error, NW PDX, sitting stopped at light, EB NW21st & Lovejoy, 70F, full tank, 7:30pm.  Didn't turn on red light, but did screen swap 4 times (2 each screen).
21663 miles, brief FI error, PDX, sitting stopped at light, WB 181st & Sandy, 55F, Full tank, 10:30am.  No read light, just caught a glimps of it.
21825 miles, Another FI error, EB US26 @ Cedar Hills cruising at 70MPH, 6th gear, a couple minutes before low fuel came on, 55F, 12:45am, red light flashed twice.
21943 miles, Another FI error, HCRH South of Stark St. bridge almost to Springdale, 50MPH, low fuel on, 50F, 8:45pm, it turned off Red light (was on after clearing low fuel warning).

They did seem to taper off after tightening up the throttle cable slack a couple different times, though that could have also been a coincident.

Wow! I have similar miles but have only seen 3 or 4 F1 errors. But I'm sure there have been others. It is so brief that unless you are looking at the screen at the time you would miss them.

Your KiPass is correcting the problem so fast the human eye can't detect the flash of the red light

There ya' go- next year's marketing sound bite: "The new KiPass, now faster than light. The only area left that could be improved."

Brian

Your KiPass is correcting the problem so fast the human eye can't detect the flash of the red light

Yeah, that documentation is a little light- we are going to need the direction the bike was pointing toward in each instance, as well as the phase of the moon to make any type of useful guesses.

What do you do, ride with a notepad open and a pencil in one hand?

Brian

No notepad, just commit the details to memory until the next stop (usually fuel or arrived at my destination).  Some of us still have our short term memory 

Actually, I consider it ammunition, just in case I ever have to deal with Kawi on some electronic problem with this bike.  Some would say you can always use more ammunition. 

Wow! I have similar miles but have only seen 3 or 4 F1 errors. But I'm sure there have been others. It is so brief that unless you are looking at the screen at the time you would miss them.

I'm sure there were many more that I didn't see.  I think mine has been on the "worse" side of the scale, for how many I seem to get.

Plus, I'm always checking my gauges and display while I'm riding.  For me, it's part of staying focused I guess.

Your KiPass is correcting the problem so fast the human eye can't detect the flash of the red light

That explains it! Maybe up here at high altitude KiPass works even faster because of less aerodynamic drag

Yeah, that documentation is a little light- we are going to need the direction the bike was pointing toward in each instance, as well as the phase of the moon to make any type of useful guesses.

What do you do, ride with a notepad open and a pencil in one hand?

Brian

I just split my sides.

This thread is competing to be more full of  win than the drive shaft thread on the old forum 

Yeah, that documentation is a little light- we are going to need the direction the bike was pointing toward in each instance, as well as the phase of the moon to make any type of useful guesses.

LOL!!!!  And here I thought I was anal-retentive with keeping much simpler logs....

Hey, no complaints from me- I think you did a great job with the documentation. I am a little surprised there were so many incidents but I would never dispute it either.

And besides, it is not like you went overboard or anything- if you recorded the 'clock' position of the valve stem for each incident I would say that was too much but the fuel level, the vehicle speed, the gear it was in, the acceleration (or deceleration), the throttle position.... those were just right....

  back at 'ya.

 

Brian

No notepad, just commit the details to memory until the next stop (usually fuel or arrived at my destination).  Some of us still have our short term memory 

Actually, I consider it ammunition, just in case I ever have to deal with Kawi on some electronic problem with this bike.  Some would say you can always use more ammunition.

YeeeHaaa!  I finally got to join the FI Error club!  7k miles and she blipped on me.  Scared the &#!+ out of me, then gently rode home wondering who can tow me home if needed :/  From what I'm reading here, not a problem.  Feels good being one of the guys now   BTW, any good tow vehicles in Cincinnati?

YeeeHaaa!  I finally got to join the FI Error club!  7k miles and she blipped on me.  Scared the &#!+ out of me, then gently rode home wondering who can tow me home if needed :/  From what I'm reading here, not a problem.  Feels good being one of the guys now   BTW, any good tow vehicles in Cincinnati?

Welcome to the club- surprised it took you 7K to get to it