2nd time it's hapened

[wetwolf]

On a ride today, rolling along at a pretty quick pace. Got up to 120 in 5th, about 7500 rpm. bike stuttered for a few seconds like it was hitting the rev limiter, CE lite flashed and went out. 3 weeks ago, was running a little hotter in 3rd gear and same thing, only that time I'm pretty sure I was bangin the rev limiter, quick glance at the tach when it was happening was over 9k. I have an FSM but I still haven't been able to find out if the ECU will actually store a code, let alone be able to pull it up.

It's an 05 gen1. The search on the forum pulls up so much BS, I figured I would reach out for a little help.

Any ideas, or can you point me in the right direction to actually pull a code from the ECU that was momentary??

[0face]

Paging Ray to the white phone....

[ionbeam]

The Gen I tables and Gen II tables below show the Code numbers and Diagnostic actions for the ECU. You will need the Factory Service Manual (FSM) to troubleshoot using these codes, there is additional code information in the FSM that is not placed here.

How To Access The Diagnostic Screen:

Place your FJR on the center stand, neutral, side stand up. This will let you test the side stand switch.

With the key off and the red Run switch ON, press and hold the "Select" and "Reset" buttons simultaneously and turn the key on (do not start, just ON), continue to hold the buttons until the display next to the fuel gauge says diAG (5-10 seconds). If someone has performed the Barbarian Jumper modification at the ECU connector the first screen will be CO for the CO offset adjustment, the diAG screen will be the next function. (Edit: The Gen II will come up in the CO mode automatically.)

Release the two buttons. Now, press the "Select" and "Reset" buttons simultaneously again. After ~ 2 seconds the display should show dI:01 on top and a two digit number at the bottom. dI:01 is the diagnostic code number. The two digits at the bottom of the meter is the value for the diagnostic code number. Diagnostic Code dI:01 lets you look at the throttle position sensor (TPS) output. The TPS value is the two digits at the bottom of the display. Turning the throttle will change the bottom two digits. Normal is 15-17 with the throttle closed and 97 to 100 with the throttle wide open. This is an example of how the dI:xx top and bottom two digit data works.

Press "Select" to increment the diAG sequence number and press "Reset" to decrement the diAG sequence number. At code dI:09 the fuel system voltage will be displayed and you should hear the fuel pump turn on. Expect to see roughly 11.7 to 12.4 displayed on the bottom, this is the battery voltage to the fuel pump. A reading like 00.1 would indicate a blown fuse or broken wire.

There are also 'Actuator' codes that let you turn on things like radiator fan relay and the fuel pump relay as well as firing the coils and injectors. The Actuator codes are enabled by switching the red Run/Stop switch on the handlebars Off then back On again.

The following tables are Gen I Code Numbers, their value and action. The text size is squint to read and not intended to cover all the information about the codes. You will need the FSM to properly use these codes.

===============================================================

Gen I Codes:













================================================================

Gen II Codes:

[NTXFJR]

When you get done working through Alan's excellent post and if the problem is still there, you might consider looking at the ignition coils. My old school V65 V4 had twin coils with wasted spark technology, similar to the gen 1's system. Those coils when failing would break down under heat and higher loads such as when at speed. Other possibility could be the crank sensor breaking down.

[ionbeam]

I should have mentioned that diAG code 61 & 62 are were you need to go to look at fault history.

[wetwolf]

I should have mentioned that diAG code 61 & 62 are were you need to go to look at fault history.

Tbats exactly what I was looking for!

[wetwolf]

12,16,19,30

Lookin like it might be a crank sensor, all the other codes were my fault. LOL. Cleared them all and time to try to reproduce the failure and see what codes come up again.

Thanks Ionbeam, I have an FSM, but it would have taken me 2 hours to read thru al the BS to get to how to check history. Scrollin thru is a cakewalk.
Once again, thank you very much.

[HotRodZilla]

12,16,19,30

Lookin like it might be a crank sensor, all the other codes were my fault. LOL. Cleared them all and time to try to reproduce the failure and see what codes come up again.

Thanks Ionbeam, I have an FSM, but it would have taken me 2 hours to read thru al the BS to get to how to check history. Scrollin thru is a cakewalk.
Once again, thank you very much.

Any chance you have a Power Commander? I had a VTX doing that and it ended up being a loose ground to the dammed PC. If you don't have one, then ignore me and carry on.

Good luck.

[raYzerman]

Paging Ray to the white phone....

More than adequately covered already. I'd clear the codes and see what returns when the condition repeats.
If there's a PC, sometimes they need to be disconnected and rebooted, ground check, etc. One could also just unplug it and run stock FI to see if the condition occurs without the PC in the loop.