Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cash338]

I just started having a code flassh shortly after start up for about 10 seconds and then go out. Only on cold start ups.  I did the switch thing and found that it was code 56.  Which reads-canshaft position sensor and crankshaft position sensor timing or signal error.  The bike runs great and only throws this code on cold starts.  I'm trying not to go the stealership to fix.  Any thoughts...thanks.   Scot

[HDDOCFL]

If the engine light goes out after 10 sec. it is a historic code, no problem. You can clear the code or wait 50 starts and it will clear itself.   Doc

[cash338]

I wonder why it comes on only during cold starts.  I was thinking that my timing is good and maybe I may have a sensor going bad.

[Twolanerider]

I just started having a code flassh shortly after start up for about 10 seconds and then go out. Only on cold start ups.  I did the switch thing and found that it was code 56.  Which reads-canshaft position sensor and crankshaft position sensor timing or signal error.  The bike runs great and only throws this code on cold starts.  I'm trying not to go the stealership to fix.  Any thoughts...thanks.   Scot

What year bike?  Unless older you won't have the cam position sensor anymore.  That will narrow down the choices. 

As described above displaying as you're describing it's a historic code.  Means something happened at least once sometime before it started displaying.  If you don't do anything else that sensor is easy to pull out and wipe off (for peace of mind if nothing else).

The start/stop cycles will eventually clear it if it's not recurring.  If you know someone with a scan tool to hook to the bike they can also.  Seeing the code would bug me too.

[cash338]

It's a 2001 fltrsei2.  It is the only code stored, and looks like it came up several times.  Although the bike is running great.  And only comes on right after a cold start for a few seconds, it then turns off.

[Twolanerider]

It's a 2001 fltrsei2.  It is the only code stored, and looks like it came up several times.  Although the bike is running great.  And only comes on right after a cold start for a few seconds, it then turns off.

That one will have a cam sensor.  They were also a bit more likely to fail than the other system sensors (at least I had or have seen more die than the other parts).  Unfortunately more of a pain in the ass to change than the simpler crank sensor also. 

If it craps out you're dead on the side of the road.  So at least get the codes cleared and see if it comes back.  No sense in inviting a tow or trailer's visitation some dark and stormy night (because you know that's when the damn thing will fail if you leave it alone!).

[Ed Ramberger - One_Screamin_Eagle]

I just started having a code flassh shortly after start up for about 10 seconds and then go out. Only on cold start ups.  I did the switch thing and found that it was code 56.  Which reads-canshaft position sensor and crankshaft position sensor timing or signal error.  The bike runs great and only throws this code on cold starts.  I'm trying not to go the stealership to fix.  Any thoughts...thanks.   Scot

Magnetti Marrellis often throw that code if you have even a mild kick back when starting.  Doesn't mean any sensors are bad.  It's historic and if it doesn't happen again will clear after 50 run cycles.

[cash338]

I had a couple funky starts, so maybe that is it.  Thanks everyone for the replies.  Sure is running good.  60 degree weather down here, time to ride....

[dartman]

I just started having a code flassh shortly after start up for about 10 seconds and then go out. Only on cold start ups.  I did the switch thing and found that it was code 56.  Which reads-canshaft position sensor and crankshaft position sensor timing or signal error.  The bike runs great and only throws this code on cold starts.  I'm trying not to go the stealership to fix.  Any thoughts...thanks.   Scot

With MM FI a spitback through the 'throttle Body on start up will cause this condition im betting it will go away on its own.