2000 RK "Historical" error code question
Thread Starter
|
Tourer
Joined: Nov 2009
Posts: 363
Likes: 0
2000 RK "Historical" error code question
On my 2000 carbureted Road King, I got error code 56, which is crankshaft/cam related, like the 2 may be out of phase, etc. It comes up as a "historical code" because the check engine comes on for 4 seconds, goes off and then comes back on for 8 seconds, then goes off again.
I'm getting that it's 56 because the other possible codes are all EFI related and this bike is not EFI.
If I have a "historical" code, does that mean everything's groovy now and that the problem is all in the past, or do I need to get it checked?
I am mechanically challenged, but have the service manual and do basic maintenance?
Also, it's possible that this engine light has come on other times that the neat scenario above, but I'm not totally sure.
I'm getting that it's 56 because the other possible codes are all EFI related and this bike is not EFI.
If I have a "historical" code, does that mean everything's groovy now and that the problem is all in the past, or do I need to get it checked?
I am mechanically challenged, but have the service manual and do basic maintenance?
Also, it's possible that this engine light has come on other times that the neat scenario above, but I'm not totally sure.
Tourer
Joined: Jul 2007
Posts: 497
Likes: 8
From: New Egypt, NJ
I'm speaking from my experience as a longtime car mechanic, but the on board diagnostics on bikes are very similar. In general a "historical" or "stored" code, as opposed to a "current" code, means that the ECU (Engine Control Unit) detected a fault which is no longer present. Depending on the code, this may happen with a single occurrence of the fault, or it may take more than one occurrence for the ECU to store a code.
If you have a code that indicates crank/camshaft, I'd guess that it could be a crankshaft position sensor issue, since there is no cam position sensor.
You might want to have it looked at; the problem with this type of situation is that if the problem that caused the code can't be duplicated, often times the tech winds up going with the "typical" cause (for example, "The crank sensor's 'usually' bad when the bike sees that code") and throw a part in, clear the code, and hope it's right. Hopefully, the wiring all gets checked thoroughly between the sensor, its connector and the ECU to make sure there isn't an intermittent contact or some other wiring fault. Bottom line, if the ECU set a code, there's a problem there. It may take a while for it to show up again or become a problem that you nitice through some running symptom, but the code didn't appear for no reason.
If you have a code that indicates crank/camshaft, I'd guess that it could be a crankshaft position sensor issue, since there is no cam position sensor.
You might want to have it looked at; the problem with this type of situation is that if the problem that caused the code can't be duplicated, often times the tech winds up going with the "typical" cause (for example, "The crank sensor's 'usually' bad when the bike sees that code") and throw a part in, clear the code, and hope it's right. Hopefully, the wiring all gets checked thoroughly between the sensor, its connector and the ECU to make sure there isn't an intermittent contact or some other wiring fault. Bottom line, if the ECU set a code, there's a problem there. It may take a while for it to show up again or become a problem that you nitice through some running symptom, but the code didn't appear for no reason.
Cruiser
Joined: Nov 2008
Posts: 214
Likes: 0
From: Leesburg, FL
The first thing I do with a historical code is, if there are no other symptoms, like hard starting, misfiring, or other noticeable issues, is disconnect the battery for 5 minutes. That will clear the codes. Take it out for a nice long ride, and see if the code reappears.
Tom
Tom
Thread
Thread Starter
Forum
Replies
Last Post
