2010 FJR1300 engine stop when starting from stop

Yamaha FJR Motorcycle Forum

Help Support Yamaha FJR Motorcycle Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

Skip Irwin

Member
Joined
Jun 17, 2010
Messages
12
Reaction score
2
Location
Surry, VA
I have a problem with my new 2010 FJR that keeps recurring.... when I am at a stop and I let out the clutch and starting giving the gas, the engine stops. It does not stall from dragging the clutch... it stops like I turned the key off. I haven't even let the clutch go far enough to stall the engine. It has happened at least a dozen times in the 2 weeks I have owned the bike. Almost like a dead spot on the throttle, but it does not happen every time.

Ideas??

Skip

 
Your's is pretty new to be suffering from corrosion issues, but its possible that water got into the sidestand safety switch. I experienced similar symptoms and traced it back to that. Clicky

 
I have a problem with my new 2010 FJR that keeps recurring.... when I am at a stop and I let out the clutch and starting giving the gas, the engine stops. It does not stall from dragging the clutch... it stops like I turned the key off. I haven't even let the clutch go far enough to stall the engine. It has happened at least a dozen times in the 2 weeks I have owned the bike. Almost like a dead spot on the throttle, but it does not happen every time.
Ideas??

Skip
Hello fellow newbie

Mine did a similar thing when she had 500 miles on her. I made a very brief stop after a 100 mile run, restarted the bike and gave her a touch of gas and the motor simply stopped.b Did this twice and on the third restart I let it run a bit longer and all was well. I had the bike in for the 600 service the same day at the end of this ride and mentioned the event. Mechanic thought it was due to the motor being still "Tight" and hot as there were no codes or problems found. I had one more occurance at about 700 mi. and none since and have 1600 miles on the her now.

 
Last edited by a moderator:
Skip,

I had the same thing with mine from new (09)

In and out of dealers no fault code, no joy

Had in the back of my mind, if I want it sorting I'd have to do it myself.

After searching this forum, which is first class for info and help I did a throttle body sync and turned the tickover up from

1000rpm to 1100rpm, been spot on ever since. 4000mls.

Keith.

 
Mine (an 08) has done this since it was new. Blip the throttle sometimes (or open it abruptly from a stop) and it stalls. Hot, cold- doesn't make a difference. I took it back to the dealer after about 500 miles and they adjusted the idle. No joy. Did a throttle body sync at 10,000 miles. Same, same. I have over 20,000 miles on it and it still does it. Frustrating.

It doesn't happen if I don't blip the throttle, so I don't blip the throttle anymore.

Harumph.

Jim in BR

 
May I suggest the Barbarian Jumper modification?

Here's a link to the GenII Bin O' Facts - BJM Here

I had one of the first GenII's in California, and it did the exact same thing. Since I did the BJM, never a problem since.

 
I too have this problem on my 2010 FJR. Just got back from dealer with 600 mile service. They could not replicate the problem. So, I too am looking for answers. Wouldn't you know the first stop light after I picked it up, it cut off.

** Update ** Got home and read forum, moved idle to 1100 and rode 100 miles this evening with no stalling at all......I believe this fixed it.

** Update2 ** rode 135 miles today, stop and go traffic, still no stall.

 
Last edited by a moderator:
It may be a slight glitch in the ECU <_< caused when it is calling for more fuel to mix with the increase of air when the throttle body is first being opened, or a throttle position sensor issue. Maybe the dealer of your choice can re-burn, Re-program, flash or whatever you call it to your existing ECU. I have a stock 07 ECU from the altitude recall you can have, but you probably don't want it. :assassin: It sucked!

 
Mine is an "08 and it did the exact same thing. Sometimes as I was turning left and as I would go through the intersection and pull in the clutch to prevent running into a slow moving cager, I'd blip the throttle and the sucker would just die like I turned the key off. I move the idle up to 1100 rpm and has not happened since. These FJR's can be pretty temperamental at times.

 
It seems that every week this same question pops up on '10s. The forum is littered with posts on this. Standard advice is to raise the idle rpms, but most report this doesn't make a difference. Others report it goes away with miles. As an '06 guy, I don't have this problem, but one of you '10 guys might want to do a search on this (2010 FJR (whatever) site:fjrforum.com) to see if you can gather info on how many others have this problem and whether anyone has found a fix.

Really guys, as an interested but not impacted bystander, this seems to be a recurring thread. Maybe there is something to it.

 
2010 without any problems at all. I know that engines are tight during the break-in process and with a low idle once could experience stalling.

How hot is your engine running on the temp gauge and what are the temps that you are riding in when the stalling incurs?

 
When this happens, it is like the key is turned off. It is not an idle problem because I haven't let the clutch out enough to start to grab. Blipping the throttle will also cause the engine to stop randomly. I am going to ask the dealer about it, but I know what the answer will be when I cannot duplicate it.

When this happens, it is like the key is turned off. It is not an idle problem because I haven't let the clutch out enough to start to grab. Blipping the throttle will also cause the engine to stop randomly. I am going to ask the dealer about it, but I know what the answer will be when I cannot duplicate it.

 
Same thing happened to me while on a test ride at the Midwest Star B Q (heck always willing to ride for free) The guy from yamaha tried to make it look like I was doing something wrong but I had a feeling the bike was not running up to par....

 
Top