Subaru Forester Owners Forum banner
  • The "Garage" feature is for images of YOUR VEHICLE/S only - no blanks or other unrelated images please, thanks

2013 - Traction control light on, cruise light flashing?

9.6K views 10 replies 5 participants last post by  Jdf60  
#1 ·
I have the traction control light on and cruise light flashing. and the cruise doesn't work. I've googled and found that there are many reason for this ranging from fuel cap to PCU. I've checked codes and it has nothing stored related to any traction control. Just a misfire code I'm working on diagnosing as well. Engine is running fine.

I would think a wheel speed sensor could be the most common issue, but wouldn't my code reader see that? On my Honda SUV the same light is on and it does throw a wheel speed sensor code and I am able to read it with my cheap reader. But I'm sure there are differences btw honda and subaru codes for this kind of thing.

The only thing I've done so far is replace the fuel cap because some people said that fixed their issue, but not mine. I didn't have any codes related to the fuel cap but needed a new one anyway due to the retainer strap broken off.

Any help is appreciated!
 
#2 ·
Often a code will disable various systems that might potentially be affected by the problem that actually caused the code. It's frequently a safety measure, just in case. That turns their lights on.

Lots of lights light up. We call it 'the Christmas tree'.

Concentrate on the misfire code, P030x I assume? They can be hard to track down.
 
#5 ·
I may take that bet just because if I do then you’ll be right for sure!
I’ve replaced the engine and I’m pretty certain the misfire code along with the traction control and cruise lights never changed. I’m not 100% sure on the misfire code because I never read codes before. But the check engine light was on before engine swap. I reused all the sensors from the original engine but have no sensor codes. So it was basically a long block swap.
 
#6 · (Edited)
Jdf60
Hmmm..
You had a CEL on before the swap and if you never cleared the CEL codes, you may just have a red herring problem.
I'd suggest you clear the CEL codes (most code readers can do this) and it might just solve your problem. i.e. the problem just might be recorded from the prior engine, and the ECU still remembers that if the disconnected battery didn't clear it.
As was mentioned, Subaru turns off about everything when anything goes wrong...
Good luck.
 
#7 ·
Jdf60
Hmmm..
You had a CEL on before the swap and if you never cleared the CEL codes, you may just have a red herring problem.
I have reset codes several times. It always comes right back. I don’t believe anything on the engine itself was causing a code. I think since I reused everything, coils, sensors, etc. whatever code was there will remain if it was sensor related. The only issue with the old engine was a rod knock, it was running fine. And I never read codes on it because had lost my reader until now.
Could a crank or cam sensor, etc be causing an issue but the sensor itself not cause a code? Maybe my reader is not capable. It is a cheap $20 reader and does some strange things.
 
#8 ·
Anything (just about) is possible, but a failed crank/cam sensor is unlikely to be causing a misfire issue without a lot of other symptoms as the engine won't be running well, or often not at all.
The reported misfire would likely not be isolated to one cylinder if it's just a bad sensor.

If by the code, (" whatever code was there will remain if it was sensor related") you mean the problem that created it, yep. A bad sensor causing the ECU to complain by reporting the CEL code would likely be the same when it is reinstalled on the newer engine.

IIRC the misfire code will report which cylinder is having the reported problem.
The CEL is telling you there is a misfire, but not why.

A sensor may be reporting an actual problem to the ECU.
It could be a coil going/gone bad or it's electrical connections so it's a spark issue, or an injector problem, either in fuel availability, the injector itself, or the electrical connections to the injector that is causing a fuel delivery issue.

OTOH it could also be a problem reported by the ECU by a bad sensor, or a wiring issue or even the ECU itself.

There are two approaches -
1 - Find the problem and then fix it, also known as diagnosis
or
2 - Throw parts at the problem until the problem disappears, often known as the dealership approach ;)

The former may seem to take more time but it will save money in parts that aren't doing any good to remedy the issue.

The coil pack for the problem cylinder might be a good place to start checking.

Good luck, or even better advice, be methodical...
 
#10 ·
Anything (just about) is possible, ...
appreciate all the tips. The only thing I haven’t checked or swapped yet is the injector wire/connector and the ecu. I also haven’t checked any wiring past the coil wire because I know it is firing and running good.

haven’t changed any sensors because I have no sensor codes. I’ve swapped coils, injectors, coil wire/connector and checked compression. I haven’t bought new parts but just swapped with other cylinders. I did buy the new coil connectors and wires.

I’ll keep checking stuff snd I’m reading over that pdf diagnostic document also.
 
#9 ·
What code are you seeing? The normal misfire code is P030x, where x indicates the cylinder involved.

Typical reasons that we've seen here, in order of increasing complexity, are plug wires, plugs, coil, injectors.
 
Save
#11 ·
What code are you seeing? The normal misfire code is P030x, where x indicates the cylinder involved.

Typical reasons that we've seen here, in order of increasing complexity, are plug wires, plugs, coil, injectors.
I’m getting the p0303. And I have checked/swapped all these things. Except #3 injector wiring/ connector.

gonna keep at it!

thanks!
 
You have insufficient privileges to reply here.