2014 SGS...have only had a month or so and due to weather haven't ridden much but so far had run great...until yesterday. throttle started hesitating and was essentially unresponsive. was able to get home by essentially riding the clutch while keeping the throttle almost completely open. error codes were 1510 and 2138. check engine light is on.

I have done searches on the TPS/codes/etc and will go through the usual troubleshoots and such tonight...but just wondering if anyone else has had this. I was also curious if this was in fact limp mode or something else. from what ive read limp mode is just to get you home, and although I did get home ok this was essentially unrideable and it seems from the things ive read limp mode would be a little more "rideable"

also fwiw there are no obvious gas leaks or anything but it seems like the few miles ive ridden it went through gas a lot quicker than I would have expected.

again I will go through the wires and connectors etc when I can...just wanting some additional insight if anyone could...thanks.

 

Any recent work done on the bike? Like handlebars installed?

 

I did a quick google search, seems TGS (Twist grip sensor) that could be the culprit.

https://www.hdforums.com/forum/touri...ap-08-tbw.html

rk classic.

 

I installed rear speakers and an amp....perhaps I jacked up a connection when putting it all back together? at work now and haven't had a chance to go through it yet. does anyone know if this sounds like limp mode it was in?

 

Check for a bad wire in the plug just behind the aircleaner going into the throttle body. Sometimes a wire will break there. Clean the plug and connectors with some alcohol and then use dielectric gease. Clear you codes and see if that solved your problem. That twist grip sensor is about 125 bucks and a pain to get to the plug on it...at least mine was.

 

Limp mode will render the throttle useless. You will get no response from it or at least I didn't when my bike went into it. my culprit was the TPS sensor on the throttle body but I thought that they fixed that in later models. It sounds like your issue maybe due to something else.