Hello today i was on the highway and the bike started to buck as if it was runing out of gas but it didnt it was low so i stoped and put gas then when i went to turn it on the FI light comes on and it wouldnt let the bike start finally after 10 min it turned on and the FI light was off but it still was bucking kind of. How do i pull up the past and present codes on there to see if i can pin point wat it was thanks any help would b appreciated

From memory: w/key on hold down both trip and mode together and wait some? Possible number pops up, rather than blinks in short and long sequences.

Yes i tried that and it went to a alternate menu fa like the clock or shift light... it went ofafter like ten min but is there away to check passed codes on there also

Take seat off. As if sitting on bike, look at the rear where the ECU is. To the right will be a sponge type plug holder. If you do not have the immobilizer, there is an empty sponge block. The other clip inserted into the sponge holder is the self checker. Use an ohm resistor and install it in one wire, then past that other end into the other 3. Wait for the memory to show the possible saved code with key on and wait for something to cycle on in a few seconds. Don't pull the resistor wire out of each 3 remaining wires so fast. Wait for the cycling of each test wire to wire. One combo is going to pop the code up in other words.

I had an FI light on my busa and was able to bring the code up in the same way. A resistor was not necessary but a piece of wire or paperclip inserted between two of the contacts did the trick. If you figure out which two contacts bring up the code #, please show a pic.

I have told this story about 10x now but I had bucking like running out of gas happen with my bike a few years ago. The speedo also went crazy and eventually stopped working. I didn't notice any codes on the meter but it's possible that I didn't notice that. The bike was back to normal after sitting a few hours. I'm pretty sure it was water in the speed sensor wire harness.

* Last updated by: Rook on 6/19/2016 @ 8:13 AM *

A... it probably won't matter, but I had this argument with Cblast. I have 4 wires coming out of the code detect plug. I have the variable of thinking I have a hot that possibly shorts to ground, blows a fuse. So I cover my ass by using the resistor, can feel the heat at the porcelain, know this acts as a fuse as it takes the heat or feel the heat build up and no code pops up sort of safety wire hacking; without knowing what wires to connect or having the factory toggle tool that needs no fuse, and this just ties the wires together to show the memory bank.

You can't pull that wire fast enough as it turns cherry red before it pops or burns the harness wire from one end of the harness to the other point... Ask me how I know?

Yea i have 4 wires on that plug and i definatly dont want that to happen. Will check it tommorw as today ill b wit my family

Just find the right contacts. I wouldn't go experimenting. More problems waiting to happen. Try ZX1441R.com and someone will prollly know which contacts work.

http://zx1441r.com/forum/index.php?sid=c3e32802723409606c0377a4c0d04c7f

* Last updated by: Rook on 6/21/2016 @ 1:37 PM *

Ok s i was finally able to get to the dealer and get the code and it was a camshaft sensor... the guy at the dealer told me to not worry bout it now cuz it went away... i drained the gas out and put new gas and it still doin the same thing my next step is to check the plugs to see if they are fouled out and to c if the injectors are good and firing good and not clogged

Pull the right crank cover, inspect the tone wheel off the crank for a loose bolt, wheel, etc. Reason way is:

Cam sensor is a phantom code. Why? If the cam sensor fails, no start.
Member installed an aftermarket adjustable advancer and replaced the stock tone wheel off the crank. Cam code kept popping up, but I said if the cam sensor was bad, no start. He did not listen to turtle, wasted his money, comes to find out it was a loose crank bolt and sporadically sent cam codes.

Try there...