Kawasaki Concours Forum
The C-14, aka Kawasaki Concours-14, the new one :) => The Bike - C14/GTR 1400 => Topic started by: Poseidon on August 23, 2018, 05:47:19 AM
-
Anyone know of a reason why the FI warning would pop up for a couple of seconds then go off? I’ve had it happen twice now. It doesn’t stay on, so I can’t check for error codes. Probably going to have to take it to the dealer to have them check the history to see what’s going on. Thought I would throw the question up on here to see if anyone has any ideas.
-
If the FI light comes on for a few seconds and then goes off, it's usually caused by some interference. If there had been an actual issue, the light would not clear itself and you'd be able to read out the fault code. In your case there is no actual fault.
-
Happens to everyone. I get it probably twice a year. No issue. A "feature" of the bike.
-
It has never happened on my bike, but I have the first gen. Is it because the first gen bikes are faster? :banana
-
I have had it happened a few times momentarily on my 2017. I don't know about 1st Gen the only 1st Gen bikes I've ever seen were in my rearview mirror and fading fast. ;)
-
A well- known quirk of the Gen. 2 C-14's. The FI (Fuel Injection) light pops on but then goes right out and no errors are logged. I believe what is happening is that certain requirements in the software are met momentarily and that triggers the error light but does not actually generate an actual error.
Put another way, 'Nothing to see here, move along......'
:-)
Brian
Anyone know of a reason why the FI warning would pop up for a couple of seconds then go off? I’ve had it happen twice now. It doesn’t stay on, so I can’t check for error codes. Probably going to have to take it to the dealer to have them check the history to see what’s going on. Thought I would throw the question up on here to see if anyone has any ideas.
-
Is there any way to fix it / prevent it from happening? If it is common and only a gen 2 issue, you would think they would have a fix for it by now...
-
I assume most people were too busy un-linking their brakes that they didn't care about the random FI light
-
Every Gen2 gives an occasional, brief, unknown-why FI error
http://www.zggtr.org/index.php?topic=336 (http://www.zggtr.org/index.php?topic=336)
http://www.zggtr.org/index.php?topic=22579 (http://www.zggtr.org/index.php?topic=22579)
http://www.zggtr.org/index.php?topic=12295 (http://www.zggtr.org/index.php?topic=12295)
http://www.zggtr.org/index.php?topic=10192 (http://www.zggtr.org/index.php?topic=10192)
http://www.zggtr.org/index.php?topic=1637 (http://www.zggtr.org/index.php?topic=1637)
http://www.zggtr.org/index.php?topic=11130.0 (http://www.zggtr.org/index.php?topic=11130.0)
http://www.zggtr.org/index.php?topic=11335 (http://www.zggtr.org/index.php?topic=11335)
http://www.zggtr.org/index.php?topic=9892 (http://www.zggtr.org/index.php?topic=9892)
etc...
-
Is there any way to fix it / prevent it from happening?
Not that I know of. Keep in mind, nobody even knows why it does it. My theory is that it is intense radio frequency interference.
If it is common and only a gen 2 issue, you would think they would have a fix for it by now...
One would think so, but I don't believe Kawasaki has *EVER* offered updates to the ECU firmware.
-
Is there any way to fix it / prevent it from happening? If it is common and only a gen 2 issue, you would think they would have a fix for it by now...
It's not just Gen II bikes, my '08 did it at the noted mile points also, around 8k and 11k, then never again... no big deal, it was a 'flash' and off.. and I wasn't anywhere near a place generating any signals either time...
as Brian noted, it's common, and does not stay in the code registry...
it usually occurs around 8k miles, and i don't recall it happening on any bikes reporting 20k miles or over... it is always early on, I also agree with his hypothesis that it something in the 'code' triggered by mileage waypoints, and never seems to appear later on in life... don't sweat it.. all is good.... if it comes on, and STAYS ON... then be concerned.
-
For us mortals, no. You would have to get the source code for the ECU, find the problem in that software, correct it, then burn into the ECU. First of all, we cannot get the source code as it is proprietary and not available. Then the other problem(s) such as re-writing it to eliminate that glitch. Even if it could be done, not worth the time and effort IMO.
Again, this is just a little glitch in the software and nothing but a passing quirk- nothing to be concerned with.
Brian
Is there any way to fix it / prevent it from happening? If it is common and only a gen 2 issue, you would think they would have a fix for it by now...
-
Glitch?
nahhhh, it's in the program...
the program is perfect, perfect, perfect, perfect,....hic...
It's actually there as a 'waypoint', and everything you do while riding before it happens, is recorded, especially how many time it was 'banged' off the rev limiter prior to 6k miles...
lets just name this "The Prime Directive"....of Kaw.
google it...
it is a guiding principle of the United Federation of Kawasaki Planets prohibiting the protagonists from interfering with the internal development of alien civilizations.
This conceptual law applies particularly to civilizations which are below a certain threshold of technological, scientific and cultural development; preventing C14 starship crews from using their superior technology to impose their own values or ideals on them...
As time travel became a recurring feature in the franchise, the concept was expanded as a Temporal Prime Directive, prohibiting those under its orders from interfering in historical events.
"Little Brother is watching you....".... bwwooohhaaaaaHaaaahHaaaaaaa
-
Glitch?
nahhhh, it's in the program...
the program is perfect, perfect, perfect, perfect,....hic...
It's actually there as a 'waypoint', and everything you do while riding before it happens, is recorded, especially how many time it was 'banged' off the rev limiter prior to 6k miles...
lets just name this "The Prime Directive"....of Kaw.
google it...
it is a guiding principle of the United Federation of Kawasaki Planets prohibiting the protagonists from interfering with the internal development of alien civilizations.
This conceptual law applies particularly to civilizations which are below a certain threshold of technological, scientific and cultural development; preventing C14 starship crews from using their superior technology to impose their own values or ideals on them...
As time travel became a recurring feature in the franchise, the concept was expanded as a Temporal Prime Directive, prohibiting those under its orders from interfering in historical events.
"Little Brother is watching you....".... bwwooohhaaaaaHaaaahHaaaaaaa
Wow! All that from an FI error?!?! :yikes:
-
It's not just Gen II bikes, my '08 did it at the noted mile points also, around 8k and 11k, then never again... no big deal, it was a 'flash' and off.. and I wasn't anywhere near a place generating any signals either time...
as Brian noted, it's common, and does not stay in the code registry...
it usually occurs around 8k miles, and i don't recall it happening on any bikes reporting 20k miles or over... it is always early on, I also agree with his hypothesis that it something in the 'code' triggered by mileage waypoints, and never seems to appear later on in life... don't sweat it.. all is good.... if it comes on, and STAYS ON... then be concerned.
I’m not even to 5000 miles yet and it has happened twice. Currently at 4748 miles. Never around anything electrical. Both times were on back country roads. No cell towers, radio towers, power substations, or high power lines around.
-
Just curious... anyone ever have it happen after an ecu reflash?
-
It's not just Gen II bikes, my '08 did it at the noted mile points also, around 8k and 11k, then never again... no big deal, it was a 'flash' and off..
Well, with Gen 2, it seems normal for it to happen anywhere from once to a few times a year, every year. I stopped keeping track on mine but do have some logged.... Had a few in the first 1K miles, then again at around 2.2K miles and then 20 miles after that. Happened at around 25.5K. Those are all I logged, but I didn't log many of them (because I stopped caring).
and I wasn't anywhere near a place generating any signals either time...
RFI is everywhere- cell towers, planes, cars, even your own phone. Who knows. Not saying it *is* RFI, but that it could be, even when in a remote place.
it usually occurs around 8k miles, and i don't recall it happening on any bikes reporting 20k miles or over...it is always early on,
Maybe on Gen 1, but I still get them at 36K. But it does seem to be much more rare than when the bike was newer.
-
Just curious... anyone ever have it happen after an ecu reflash?
Yes
-
Both times were on back country roads. No cell towers, radio towers, power substations, or high power lines around.
I have had several occur along the same small stretch of a particular road, over a period of years, which seemed oddly less-than-random. All those times were just slab cruising around 65MPH with zero acceleration (steady low throttle), no "load", and no bumps.
-
It has never happened on my bike, but I have the first gen. Is it because the first gen bikes are faster? :banana
That would be correct.
I have had several occur along the same small stretch of a particular road, over a period of years, which seemed oddly less-than-random. All those times were just slab cruising around 65MPH with zero acceleration (steady low throttle), no "load", and no bumps.
I really believe it's caused by one of the 'A' government agencies. I have it on good authority that wrapping your helmet in tin foil will prevent this from happening. It's either that or space aliens.
Just curious... anyone ever have it happen after an ecu reflash?
I didn't have it before nor after my ECU got flashed. I don't think it has anything to do with that..try tin foil.
-
Just curious... anyone ever have it happen after an ecu reflash?
Not yet...
-
To be totally serious and I really hate doing that, it's some sort of external interference especially when it happens in the same general area. As long as it's not in association with any other codes there's nothing to worry about. If it's really concerning, I have a gen1 bike that doesn't get that error I'll sell you. Sorry about that, I lapsed into non-serious mode for a few seconds.
-
Must be those space indians.
-
Not yet...
But yours is a Gen 1.... had it happened at all before the flash? And if so, how many miles was the last error before the flash, and how many miles has it been since the flash? Gotta watch the numbers to get any feel for the data. :)
-
Must be those space indians.
Probably or space cowboys.
-
Poseidon, it is the ONLY 'problem' you will ever have with it, unlike some other brand. :-X
Although the fuel filter may get blocked if not changed in a few years time. :)
-
Probably or space cowboys.
Trump's new "Space Force" should take care of that then. LOL
-
it usually occurs around 8k miles, and i don't recall it happening on any bikes reporting 20k miles or over... it is always early on, I also agree with his hypothesis that it something in the 'code' triggered by mileage waypoints, and never seems to appear later on in life... don't sweat it.. all is good.... if it comes on, and STAYS ON... then be concerned.
I still get it with 64,000km. Just 2 weeks ago the last time it happened
-
Just curious... anyone ever have it happen after an ecu reflash?
Yes both times ({*}Guhl; SISF decel), and after a battery replacement as well. Plus two other times with no associated electrical event. Total of 5 times that were noticed in 75K+ miles, Gen II '10.
*Edit: both times battery was disconnected
-
But yours is a Gen 1.... had it happened at all before the flash? And if so, how many miles was the last error before the flash, and how many miles has it been since the flash? Gotta watch the numbers to get any feel for the data. :)
Upon further review... ;) 🕵️♂️
Purchased in early ‘17 with just under 38,000 miles. So, before that, I do not know. Put about 8,000 miles on it before the Mountain Runner flash and never saw it light up. I’ve put about 2,000 on it since the flash, and haven’t seen it.