• There were many reasons for the change of the site software, the biggest was security. The age of the old software also meant no server updates for certain programs. There are many benefits to the new software, one of the biggest is the mobile functionality. Ill fix up some stuff in the coming days, we'll also try to get some of the old addons back or the data imported back into the site like the garage. To create a thread or to reply with a post is basically the same as it was in the prior software. The default style of the site is light colored, but i temporarily added a darker colored style, to change you can find a link at the bottom of the site.

Yesterday Codes C0040 & C006C; Today Codes P061E & P0504! What's up with today's?

Status
Not open for further replies.
How long are the codes stored in the system?
Good question. They usually get checked and cleared by the tech using BUDs before they expire. When I had a throttle body code come up on the 2013 RT I had, the factory service manual or tech bulletin or something of the sort that the tech showed me, said the code would clear after something like 40 no problem restarts.
 
Take a large, sealed beam, like one on older cars and trucks. On the two terminals, connect a wire to each of the terminals, + and -, then pull out the fuse that is burnt and connect the other end of those wires from the sealed beam in series (+ on one of the fuse holder terminals and - on the other.) The sealed beam will light up when you have a short, (saves all the burnt fuses.) Now you can continue testing, if the sealed beam is on (shorted), just unplug wires to your various extras until sealed beam goes out, there is your short.
Used this method hundreds of times in my years as a mech.
 
Last edited by a moderator:
How did this work out? I have the same issue and same codes. I removed the brake switch but it tests good for continuity each way on both switches.
 
P061E and P0504

So, my 2011 RT SM5 just out of the blue threw up these two codes, P061E and P0504, with VSS Fault, Check DPS lights, and went into limp mode. The battery connection is tight, 12.8 volts, and battery is less than 2 months old.

I went on a lengthy ride yesterday with our local Spyder Ryder's chapter, had zero issues... Went for a quick run to the store last night, again, zero issues... Today we headed out for another somewhat longer ride, was only a half a mile from home on a straight residential street, not touching the brake or anything when the errors popped up.

Everyone keeps telling me it's probably battery, but I really doubt that's the problem since it's only 2 months old (I believe the dealer installed a Yuasa as he said the current OEM batteries are unreliable.) and my multimeter shows 12.8 volts.

Any suggestions?
 
Last edited by a moderator:
:oldpost: This is an old post that goes back to 6/2013.

Spyder Ann has not posted on the site in a few years.

This was the bike that went up in flames on the streets of Las Vegas. I believe it made the national news at the time. There was a problem with fires on less than 10 2013's and it started a real controversy issue that ran on the site for a couple of years.

BRP bought her a new bike. Details were kept secret. The 2013's were supposed to get the new 1330/3 engine but problems caused them to delay a full year. The frames were modified for the 1330's and the 998's still being used had heat issues that caused fires.

BRP came up with a air scoop that was installed for all those 2013 owners that wanted the "fix."

I was going to buy a 2013 also, but ended up buying a 2014. That turned out to be one of my favorite Spyders. Kept it over 6 years and 46K miles. :yes:
 
Last edited:
Status
Not open for further replies.
Back
Top