1300 died - Any ideas? - Star Motorcycle Forums: Star Raider, V-Max, V-Star, Road-Star Forum
 1Likes
Reply
 
LinkBack Thread Tools Display Modes
post #1 of 12 (permalink) Old 06-06-2018, 03:35 PM Thread Starter
Member
 
Join Date: May 2018
Location: Denver, CO
Posts: 54
1300 died - Any ideas?

2009 V-Star 1300, 13.5k mi, I've put 3200 trouble-free miles on the bike since January.
So, I had been riding on the highway at 80+ for 40 miles. Got off on the State Road, traffic lights about every mile or two.

After about 3 miles, cruising 50mph, the power starts decreasing. Increasing throttle maintained speed for about 5 seconds. Over the next five seconds, power continues to drop off. Opening throttle generates a little more power, but very little.
I pull the clutch to maintain the speed I have, and the engine spins down to zero. Fully open throttle does not keep the engine running.

Coast off to the side, kickstand down. No warning lights (maybe oil pressure, can't remember). Certainly no Check Engine Light.

Turn the key off for about two seconds, than back on. Needles sweep, etc, all normal. No CEL. Hit the starter. She starts right up.
Rode her to my meeting (another 2 miles), then home 45 miles (at 80+). No issues.

Anyone seen this behavior? It's troubling, I'm not sure what to think about it.
(PS, I did search, nothing about this behavior came up).

Thanks!

--
Alan in Denver
2009 1300 Tourer
Cutdown windscreen, MS fork deflectors, lizard lights, Mustang seat and backrest
pilotalan is offline  
Sponsored Links
Advertisement
 
post #2 of 12 (permalink) Old 06-07-2018, 01:38 AM
Super Moderator
 
bevo1981's Avatar
 
Join Date: Apr 2009
Location: Austin
Posts: 12,984
my guess would be a glitch with the ECU's fuel mapping. and restarting your bike cleared it.

on a steel horse I ride
i create motorcycle videos. check them out here

bevo1981 is online now  
post #3 of 12 (permalink) Old 06-07-2018, 07:06 AM
Senior Member
 
baron58's Avatar
 
Join Date: May 2016
Location: Kansas
Posts: 317
Garage
Quote:
Originally Posted by pilotalan View Post
2009 V-Star 1300, 13.5k mi, I've put 3200 trouble-free miles on the bike since January.
So, I had been riding on the highway at 80+ for 40 miles. Got off on the State Road, traffic lights about every mile or two.

After about 3 miles, cruising 50mph, the power starts decreasing. Increasing throttle maintained speed for about 5 seconds. Over the next five seconds, power continues to drop off. Opening throttle generates a little more power, but very little.
I pull the clutch to maintain the speed I have, and the engine spins down to zero. Fully open throttle does not keep the engine running.

Coast off to the side, kickstand down. No warning lights (maybe oil pressure, can't remember). Certainly no Check Engine Light.

Turn the key off for about two seconds, than back on. Needles sweep, etc, all normal. No CEL. Hit the starter. She starts right up.
Rode her to my meeting (another 2 miles), then home 45 miles (at 80+). No issues.

Anyone seen this behavior? It's troubling, I'm not sure what to think about it.
(PS, I did search, nothing about this behavior came up).

Thanks!
I had the same thing happen once, but I figured it out before I came to a stop, my thumb it the kill switch. Sounds silly but one complaint about the 1300 is the kill switch is a little easy to accidentally hit.

If that wasn't it, could be a loose wire connection. BTW the throttle mapping doesn't get corrupt and then fixed again by re-starting the bike so I doubt that is it. The TPS (Throttle position) sensor also could be flaky or have a bad connection as well

Last edited by baron58; 06-07-2018 at 07:08 AM.
baron58 is offline  
Sponsored Links
Advertisement
 
post #4 of 12 (permalink) Old 06-07-2018, 07:27 AM
KCW
Senior Member
 
Join Date: Sep 2016
Posts: 5,218
Garage
this is one of the tradeoffs of fuel injection vs carbs. If any one of your sensors quits or becomes intermittent the engine runs poorly or not at all.

Intermittent issues are very difficult to trace down.

If the bike continues to do that at random the only way I know to fix it is to:

1. start checking all the connections and wires to the sensors
2. start swapping out the sensors one by one until the fault goes away.
KCW is offline  
post #5 of 12 (permalink) Old 06-07-2018, 08:20 AM
Senior Member
 
Scrumdown's Avatar
 
Join Date: Feb 2018
Location: Poquoson, VA
Posts: 924
Garage
Logical: Like KCW said.... Check all connection and wires to sensors. While checking connections, make sure the grounds are good and seated well on the bike.


Illogical (but funny): Do you have any enemies? Any "friends" have access to an EMP and they 'blasted' you?

No matter what you ride. Just ride!
Scrumdown is offline  
post #6 of 12 (permalink) Old 06-07-2018, 08:56 AM Thread Starter
Member
 
Join Date: May 2018
Location: Denver, CO
Posts: 54
Quote:
Originally Posted by KCW View Post
this is one of the tradeoffs of fuel injection vs carbs. If any one of your sensors quits or becomes intermittent the engine runs poorly or not at all.

Intermittent issues are very difficult to trace down
Thanks guys. That's what I figured, but was hoping that there was a "known issue" that would simplify things.

If it happens again, I'll update.

--
Alan in Denver
2009 1300 Tourer
Cutdown windscreen, MS fork deflectors, lizard lights, Mustang seat and backrest
pilotalan is offline  
post #7 of 12 (permalink) Old 06-07-2018, 12:00 PM
Super Moderator
 
bevo1981's Avatar
 
Join Date: Apr 2009
Location: Austin
Posts: 12,984
Quote:
Originally Posted by baron58 View Post
BTW the throttle mapping doesn't get corrupt and then fixed again by re-starting the bike so I doubt that is it.
maybe not, but why do people claim that you can reset it by disconnecting the battery for a short time? i've seen this claim on multiple forums but haven't seen anyone cite any evidence.

on a steel horse I ride
i create motorcycle videos. check them out here

bevo1981 is online now  
post #8 of 12 (permalink) Old 06-07-2018, 12:21 PM
Senior Member
 
Scrumdown's Avatar
 
Join Date: Feb 2018
Location: Poquoson, VA
Posts: 924
Garage
Quote:
Originally Posted by bevo1981 View Post
Quote:
Originally Posted by baron58 View Post
BTW the throttle mapping doesn't get corrupt and then fixed again by re-starting the bike so I doubt that is it.
maybe not, but why do people claim that you can reset it by disconnecting the battery for a short time? i've seen this claim on multiple forums but haven't seen anyone cite any evidence.
Is there any cached memory in the throttle mapping?
If the answer is yes, then the reason why disconnecting the battery works is that it resets to the last known good configuration. Same way the battery from a laptop or power cord from a work, hold the power button for 15 seconds clears the cache from the bios & removes any residual power that is "saving bad memory".
If the answer is no, I would have to research to find the correct answer.

No matter what you ride. Just ride!
Scrumdown is offline  
post #9 of 12 (permalink) Old 06-07-2018, 01:54 PM
KCW
Senior Member
 
Join Date: Sep 2016
Posts: 5,218
Garage
the VS 1300 service manual should have one of those fault debugging trees.

If you are not getting any faults blinking the check engine light, then the ECM is being completely swamped by the fault condition, to the point of cutting off the fuel or ignition, or flooding the fuel so bad the engine wont fire.

I dont know if the 1300 service manual is available online - I know the 650 service manual is.
KCW is offline  
post #10 of 12 (permalink) Old 06-07-2018, 03:58 PM Thread Starter
Member
 
Join Date: May 2018
Location: Denver, CO
Posts: 54
Quote:
Originally Posted by KCW View Post
If you are not getting any faults blinking the check engine light, then the ECM is being completely swamped by the fault condition, to the point of cutting off the fuel or ignition, or flooding the fuel so bad the engine wont fire.
That's exactly what got my attention, that there were no CEL lights, blinking lights, or anything.

Troubleshooting is always fuel, air, spark.
My first thought was fuel starvation (filter or pump), but after 40mi of 80+mph, a problem should have presented itself on the highway rather than at cruising at 50mph.
Second thought was air, but for the same issues, it didn't seem likely (and there's a 30 day old air filter in there).
Spark didn't seem likely, as the bike was running perfectly smooth, just felt like I rolled off the throttle. It was smooth all the way to shutdown.

I looked in the tailpipe with a light, and didn't see any blockage. One very bad thing with airplanes is getting a loose baffle that blocks the exhaust and chokes the engine.
That would seem to make sense in that after the engine quit, the loose baffle had pressure removed and fell away from where it was blocking. That would also explain no CEL, in that the engine management is doing everything right, there just is too much backpressure.
But I don't know how MC mufflers are made and whether than can actually happen. The exhaust is factory, and not drilled.

--
Alan in Denver
2009 1300 Tourer
Cutdown windscreen, MS fork deflectors, lizard lights, Mustang seat and backrest
pilotalan is offline  
Sponsored Links
Advertisement
 
Reply

Quick Reply
Message:
Options

Register Now



In order to be able to post messages on the Star Motorcycle Forums: Star Raider, V-Max, V-Star, Road-Star Forum forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.

User Name:
Password
Please enter a password for your user account. Note that passwords are case-sensitive.

Password:


Confirm Password:
Email Address
Please enter a valid email address for yourself.

Email Address:
OR

Log-in










Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page
Display Modes
Linear Mode Linear Mode



Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

 
For the best viewing experience please update your browser to Google Chrome