• 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.

Sensors, steering and co-inkydinks.....

I (pinkwidow1941) also had my steering taken care of last week. They did all the recalls for the brakes. I am wondering if anyone has had any strange experiences since having it done. Here is what I am now experiencing
Since having the steering reprogrammed my bike now fluctuates when holding the throttle at one speed. It will surge and then die down. My speed remains the same but it sounds almost like I am geared to high for the speed I am at? It never did that before. I did a test, when it would happen I would down shift to see if that made a difference. No go. The other really strange issue is when I am down shifting into first gear I get an error code on my display. It first will tell me that I am in neutral, then first gear and then it will flash E6. I know that I am in first gear. You can hear it go in. At one stop the display said I was in neutral, but when I tried to kick it down into first it was already in first gear. When I started up the display said I was in first gear but it was actually in neutral??? It did it at every stop. It was not a one time deal. I was worried if I would make it home.

So now I know to ask about the gear sensor and have it replaced! Thanks for all the information. Any ideas on the raw fuel smell? Had the vapor canister replaced but it is still smelling like fuel once in awhile.

Fuel... there have been a few report that the fuel hoses to/from the fuel filter were either deteriorated or not clamped/sealed properly.

.
 
They called and told me not to ride it until they fix it. They are going to give it a really close once over and replace the gear sensor. Thanks!
 
Will the software...

upgrade solve this steering problem you are describing? I have one that is and one that isn't doing that. Both are scheduled for the S/W update tomorrow.

Another topic ATADUDE did you install the exhaust wrap? If so did you remove the headers to do it or just squeezed in to install it?
 
upgrade solve this steering problem you are describing? I have one that is and one that isn't doing that. Both are scheduled for the S/W update tomorrow.

Another topic ATADUDE did you install the exhaust wrap? If so did you remove the headers to do it or just squeezed in to install it?

Hey, Ken. The generation I Gear Position Sensor had some bad soldering problems (according to at least one BRP source) that was sending confusing signals to the DPS. Generation II sensors (with a new part number) were apparently put into production sometime in the fall of last year.

Unless the software upgrade eliminates totally the GPS input, it would still be a problem for builds earlier than last fall. BTW... never could figure out why they needed GPS input along with speed, RPMs, steering angle, steering torque and one or two more.

I have not done the wrap... not needed by me... I have ridden enough bikes over the years to accept reasonable "heat" to the rider. I do not perceive any appreciable heat from MY Spyder. Now, if you want heat, ride a Valkyrie or Boss Hoss. :D
 
... As you may have read in the past, I have had a few infrequent times where the power steering (DSP) "caught" in a curve and was very hard to push through the "catch".

On two other occasions (five minutes apart), while on a straight-a-way, the steering actually pulled me into the lane immediately to the left. (No, it was not the highway design, either... I was watching carefully after the first time because it scared the crap out of me.) Thankfully, that was on west bound IH-40 in Oklahoma on an early Sunday morning with little, or no, traffic.

Just this last weekend, I had a combination of the "steering catch" and gear position errors at the same time... at least, it was the first time that I noticed the two issues at the same time.

On this last ride, the gear position indicator sometimes would indicate an "E" when in 5th gear... or indicate 4th when I was actually in 5th. (No, not soft shifting, either.) At the same time, the steering problem/"catch" occurred.

As we have a CAN Bus (Controller Area Network)... probably a Bosch, if I had to bet... which was created for automobiles to eliminate wiring... I'm guessing that maybe sub-areas are conflicting... or the controller is going nuts not knowing what to do with what signal. I know they're not supposed to... dominant versus recessive signals... identifier bits and the like... but...

I saw one post a week or so ago that said an uneven, rough idle was "fixed" after a new gear position sensor was installed under warranty... an added plus for the person. BTW, I've had this uneven idle since new and BUDDs said nothing was wrong.

I'll get the dealer to order a new gear position sensor before I take it in... maybe in a week or two.

However...

For you bit-heads... can errors from one device (sensor) cause errors in another? I thought all of the bits and bytes were specifically identified so that this couldn't occur... that the CAN controller referee'd the traffic?

If so, could a continual error from one device prevent other devices from functioning correctly? I understand that the signals are not timed... that if a "collision" of data occurs, the non-dominant signal just fades away into nothingness... to be retried later.

I'm just curious... always want to know more.

BTW, does this controller run Windows? :joke: Oh, no... not another blue screen! :yikes:





I know I am a little late to this, but thought I would try and give an answer from a "bit-heads" view point.

With the data bus systems I have worked on, the signals are timed *refereed by the network controller*, so that there isn't any chance of "lost" data. As part of that, they use a "query - answer" system; even if the "query" is nothing more than a pulse through a sensor making sure there is a return. These queries are also timed. As well as the other "smart" systems sending "go-nogo" data bits to the network controller in timed intervals. Now I am working with aviation data bus systems, so may be more sophisticated, I don't know.

However, a faulty sensor shouldn't cause other systems to malfunction due to faults in the bit stream. However, if the sensors input is needed for that system or the system that requires the sensors input is needed for the other system to function properly, then neither system will function correctly.

Clear as mud, right?:roflblack:
 
I know I am a little late to this, but thought I would try and give an answer from a "bit-heads" view point.

With the data bus systems I have worked on, the signals are timed *refereed by the network controller*, so that there isn't any chance of "lost" data. As part of that, they use a "query - answer" system; even if the "query" is nothing more than a pulse through a sensor making sure there is a return. These queries are also timed. As well as the other "smart" systems sending "go-nogo" data bits to the network controller in timed intervals. Now I am working with aviation data bus systems, so may be more sophisticated, I don't know.

However, a faulty sensor shouldn't cause other systems to malfunction due to faults in the bit stream. However, if the sensors input is needed for that system or the system that requires the sensors input is needed for the other system to function properly, then neither system will function correctly.

Clear as mud, right?:roflblack:


I've read this post 3 times, I finally figured it out.


The killer was..............................................
 
So if System A cant read its sensor then System B cant recieve the input it needed from System A so that is where the "Anomoly" shows up.
 
I know I am a little late to this...

However, if the sensors input is needed for that system or the system that requires the sensors input is needed for the other system to function properly, then neither system will function correctly.

Clear as mud, right?:roflblack:

.
Only about a year. :D

And, I got it. Thanks.

.
 
Atadude, so how is it holding up?

.
Oh, that worked well for ten months. Then a second and third round of steering issues after the first update. Second update made it worse.

I sold it in October... traded it in actually, on a Triumph Thunderbird. That one's missing a wheel but it's a nice ride.

.
 
So if System A cant read its sensor then System B cant recieve the input it needed from System A so that is where the "Anomoly" shows up.

What you said.

:roflblack::roflblack::roflblack: at myself!

I was rushed when I posted that. When I had time to think about it, I realized I should have explained it like that.:opps:
 
Back
Top