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

Codes...

Bob Denman

New member
Hi Guys!
Well the Missus and I pounded down some decent miles today; 190 of them! :thumbup:
We started out on 17B; our own little curley-que between Jeffersonville and Callicoon.
Then it was a nice shot down Rte 97 through the Hawk's Nest; Wow! teh Delaware looked like chocolate syrup!
Through Port Jervis, Rte 6, then 653 out to 206 heading South...
And we got our lunch at the Chatterbox! :ohyea:
Then back to Port Jervis, up 209 to Ellenvilee, Rte 55 and home.
BUT....
As we entered Elllenville, the bike sagged a bit, I saw a flash of orange in the center, a blinking redl light in the analog tach, and then I think I saw a DPS picture pop up... :shocked:
I got it stopped and pulled codes:
C0051
U0122
C006C

Pulled the key and walked away, did a jig, said a prayer, and sacrificed a pig...
It's running okay now; but what are these codes trying to tell me?
Thanks!
 
Hi Guys!
Well the Missus and I pounded down some decent miles today; 190 of them! :thumbup:
We started out on 17B; our own little curley-que between Jeffersonville and Callicoon.
Then it was a nice shot down Rte 97 through the Hawk's Nest; Wow! teh Delaware looked like chocolate syrup!
Through Port Jervis, Rte 6, then 653 out to 206 heading South...
And we got our lunch at the Chatterbox! :ohyea:
Then back to Port Jervis, up 209 to Ellenvilee, Rte 55 and home.
BUT....
As we entered Elllenville, the bike sagged a bit, I saw a flash of orange in the center, a blinking redl light in the analog tach, and then I think I saw a DPS picture pop up... :shocked:
I got it stopped and pulled codes:
C0051
U0122
C006C

Pulled the key and walked away, did a jig, said a prayer, and sacrificed a pig...
It's running okay now; but what are these codes trying to tell me?
Thanks!


Well, I have about 3 wise :cus: answers for whats wrong with your pressure cooker:p, but the real one is i have no idea..:roflblack:

Probably not a wise thing to do as i get ready to go out for a ride...everythings crossed:yikes:
 
Actually here is all three

C0051
Error in DPS Module
SAS Adaptive Fault. Error in VCM Module
Steering Wheel Position Sensor Failure

U0122
DPS - VCM Communication Fault - Damaged circuit wires, damaged VCM or damaged DPS/VCM pins


From another thread on here...seems like the 3 are linked somehow

And here's a (to me) complicated answer....

C006c is in the ECM module
It is a VSS CAN message plausibility error
Caused by communication intermittent/erratic and/or Check Sum Error.
External troubleshooting is not possible, check for communication fault.

UO122DPS is in the DPS module.
It is a loss of communication with the VCM (loss of CAN ID's.)
Caused by VCM fault active. Damaged circuit wires, damaged VCM or damaged DPS/VCM pins.
Action..Check for VCM fault.
Disconnect MPI2 from DLC connector.
Measure resistance between DLC-1 and DLC-2 (expected value = 50-70 ohms.)
Measure resistance between DLC-1 and ECMB-C1 (expected value < 2 ohms).
Measure resistance between DLC-2 and ECMB-C2 (expected value < 2 ohms)

COO51VCM is in the VCM module
It is a steering wheel position sensor failure.
It is caused by defective steering angle sensor (SAS), wrong sensor mounting.
and/or Steering angle sensor is not yet initialised/calibrated.
and/or Loose magnet on DPS output shaft.
Action.. Open VCM Monitoring page in BUDS.
Check SAS mechanical position Reset steering angle offset using BUDS.
Check magnet position on DPS output shaft


Well, that's what the service manual says.
C0051 sounds like they may have just fitted the SAS and not calibrated it in BUDS...worth a look.
The UO problem looks like a plug hasn't been reinserted properly or at all.
COO6 problem could be being caused by the other 2
Hope that gets you started on solving the problem.
Guesses only ..just an opinion
 
Last edited:
Oh no Bob those are the 3 codes I got before I burned up!!!!! Kidding :roflblack: but it sounds like you were riding a little recklessly and upset the steering angle sensor. :roflblack::roflblack:
 
Bob,
I got those codes on the way to spyderfest in 2012.
18000 miles later and I also got them once this spring on a bumpy long curve.
No other ill effects.
I wouldnt get too worried.
Clair

Sent from my Desire HD using Tapatalk 2
 
I would put the communication errors at the top of the problem list and put the rest as symptoms. Have any harness connectors been taken apart recently? Loose connection maybe?

You carry a pig with you to sacrifice, just in case. :shocked:
 
Actually here is all three

C0051
Error in DPS Module
SAS Adaptive Fault. Error in VCM Module
Steering Wheel Position Sensor Failure

U0122
DPS - VCM Communication Fault - Damaged circuit wires, damaged VCM or damaged DPS/VCM pins


From another thread on here...seems like the 3 are linked somehow

And here's a (to me) complicated answer....

C006c is in the ECM module
It is a VSS CAN message plausibility error
Caused by communication intermittent/erratic and/or Check Sum Error.
External troubleshooting is not possible, check for communication fault.

UO122DPS is in the DPS module.
It is a loss of communication with the VCM (loss of CAN ID's.)
Caused by VCM fault active. Damaged circuit wires, damaged VCM or damaged DPS/VCM pins.
Action..Check for VCM fault.
Disconnect MPI2 from DLC connector.
Measure resistance between DLC-1 and DLC-2 (expected value = 50-70 ohms.)
Measure resistance between DLC-1 and ECMB-C1 (expected value < 2 ohms).
Measure resistance between DLC-2 and ECMB-C2 (expected value < 2 ohms)

COO51VCM is in the VCM module
It is a steering wheel position sensor failure.
It is caused by defective steering angle sensor (SAS), wrong sensor mounting.
and/or Steering angle sensor is not yet initialised/calibrated.
and/or Loose magnet on DPS output shaft.
Action.. Open VCM Monitoring page in BUDS.
Check SAS mechanical position Reset steering angle offset using BUDS.
Check magnet position on DPS output shaft


Well, that's what the service manual says.
C0051 sounds like they may have just fitted the SAS and not calibrated it in BUDS...worth a look.
The UO problem looks like a plug hasn't been reinserted properly or at all.
COO6 problem could be being caused by the other 2

I was also thinking a loose connection somewhere in the maze...

Oh no Bob those are the 3 codes I got before I burned up!!!!! Kidding :roflblack: but it sounds like you were riding a little recklessly and upset the steering angle sensor. :roflblack::roflblack:

I did tweak Nanny's tail a couple of times today...I had an update to BUDS; can she now burn me at the stake for having too much fun??
14_6_1.gif


I would put the communication errors at the top of the problem list and put the rest as symptoms. Have any harness connectors been taken apart recently? Loose connection maybe?

You carry a pig with you to sacrifice, just in case
. :shocked:


You mean; you don't?? :shocked:
It sounds a bit as if I got a connection under her skirts that's not connecting quite as well as it used to... :gaah:
It actually didn't die when all of this was occurring, so maybe I'll ignore it until the next trip to the dealer is planned...
Thanks!
:thumbup:
 
Last edited:
Hi Guys!

I got it stopped and pulled codes:
C0051
U0122
C006C

Pulled the key and walked away, did a jig, said a prayer, and sacrificed a pig...
It's running okay now; but what are these codes trying to tell me?
Thanks!

Had the same thing many thousands of miles ago. Went into limp mode. Pulled off, checked the codes and they were exactly what you found. It was a nice road, nice curves, no problems of any kind to indicate why it should have happened. Turned off the key, waited, started up and all was fine. Hasn't recurred since.
 
At least this did not happen again ;)

attachment.php


Bob
Thanks for reminding me of that wonderful picture! :shocked:

Now for a question:
Since it appears that the VCM, and the ECM might have had a smail lapse in communication; exactly where are those two critters hidden under the Tupperware? I'd like to be able to at least go look at the cabling and connections fo look for something that's gotten loose...
 
Back
Top