Subaru Forester Owners Forum banner

1 - 20 of 66 Posts

·
Registered
2006 Forester
Joined
·
32 Posts
Discussion Starter #1
Driving along with the cruise on and then the cruise just cut-off. The green cruise light blinks and the yellow CEL remains steady. No other issues noted with the car. I have a ScanGauge II hooked all the time, it showed a code of P0000, which isn't even a real code. Cleared the code while driving, the cruise was again working fine. It's now happened again, so I'm not sure why it's throwing this P0000 code. Any thoughts?

MY06 Forester X
 

·
Premium Member
2008 Forester X Premium 5MT
Joined
·
8,073 Posts
Generally a P0000 means no obd code found, AKA there is nothing wrong with the car.

When no trouble codes are triggered the ECU will respond with the P0000, but it should not show up in the code reader, as not to confuse someone when the codes are read and leave them wondering why am I getting this code & what does it mean.

It has also been known to pop up in scanners due to a glitch in their software. Not to long ago scangauge was telling people who seen this code to update to the 3.17(?) firmware
 

·
Registered
2006 Forester
Joined
·
32 Posts
Discussion Starter #3
Generally a P0000 means no obd code found, AKA there is nothing wrong with the car.

When no trouble codes are triggered the ECU will respond with the P0000, but it should not show up in the code reader, as not to confuse someone when the codes are read and leave them wondering why am I getting this code & what does it mean.

It has also been known to pop up in scanners due to a glitch in their software. Not to long ago scangauge was telling people who seen this code to update to the 3.17(?) firmware
I haven't upgraded my Scan Gauge yet, I believe it's on 3.15 or 3.16 though. The manual says this blinking cruise light and CEL can be caused by accidental contact with the cruise switch while starting the car. But that's not the case here, other than I'm not really sure what the cause could be.
 

·
Registered
2006 Forester
Joined
·
32 Posts
Discussion Starter #4
Linear Logic offered to upgrade my Scangauge and ship it back to Australia with no additional cost.

Once in a while the car still throws the P0000 code and the cruise control light flashes (without the scangauge plugged in). I proceed to reset it with the scangauge, then unplug it again. I still don't know what the P0000 means, and why it's happening, other than this the cruise control works fine. Sometimes it'll do it when the cruise control is even on (main switch), other times it'll do it when the cruise main switch is on and the cruise is activated. I see no pattern, I cannot duplicate the issues, it's as random as they come.

There are no other issues, the code seems to not even be a real code. Going to have to take it to Suby I imagine.
 

·
Registered
06 Forester 2.5 Auto
Joined
·
14 Posts
Newbie first post, I have the same symptom on new-to-us MY06 Forester 2.5 auto, trying to clear it by battery disconnect. Wife bought it from her parents, after a 5hr highway drive with cruise, flashing error when hit traffic/roadworks.

Apparently it's come on before and been cleared at dealer with no other action taken.

I'll keenly watch how you go. I've read lots of other emissions related codes/scenarios from this indication, but I won't be throwing $$$ at it until get used to how it runs and any other problem, other than the indicator and losing cruise.
 

·
Registered
2006 Forester
Joined
·
32 Posts
Discussion Starter #6
Newbie first post, I have the same symptom on new-to-us MY06 Forester 2.5 auto, trying to clear it by battery disconnect. Wife bought it from her parents, after a 5hr highway drive with cruise, flashing error when hit traffic/roadworks.

Apparently it's come on before and been cleared at dealer with no other action taken.

I'll keenly watch how you go. I've read lots of other emissions related codes/scenarios from this indication, but I won't be throwing $$$ at it until get used to how it runs and any other problem, other than the indicator and losing cruise.

I still have no idea what the cause is. It happens intermittently whether the cruise main switch is ON/OFF. Still throws code P0000. I have a ScanGauge so I can just clear it on the fly and it's all good again...until the next time any way. Dealer in Australia wants $63 just to read the code, I know it says P0000, and since they won't be able to say more I'll just wait and see what happens.
 

·
Registered
Joined
·
53 Posts
I have a neighbor with an 05 AT 2.5X that is having the same problem. The check-engine-light comes on every few weeks. When we read the code with a ScanGauge, it comes back with P0000. This has been going on for 3-4 months.

The ScanGuage isn't causing the problem. it is not hooked up when the code is thrown.

Has anyone come up with a solution or explanation for this?
 

·
Registered
2006 Forester
Joined
·
32 Posts
Discussion Starter #8
I have a neighbor with an 05 AT 2.5X that is having the same problem. The check-engine-light comes on every few weeks. When we read the code with a ScanGauge, it comes back with P0000. This has been going on for 3-4 months.

The ScanGuage isn't causing the problem. it is not hooked up when the code is thrown.

Has anyone come up with a solution or explanation for this?
I've not found any information as of yet, not even Subaru shops can explain it which concerns me. At least having a ScanGauge allows me to clear the code immediately. This would be hugely annoying if someone had to find someone or a shop to clear the code every time it occurred. If anyone finds out the cause please post up!
 

·
Registered
Joined
·
53 Posts
Rearview: Do you have an automatic? If so, that might be a link between the three cars described as having the problem in this thread.
 

·
Premium Member
2006 Forester XT 4EAT
Joined
·
630 Posts
Same here guys, I drive an 06 xt AT and I just got this same symptom on the way to jersey, cleared it and kept going no prob, my father has a way better obd 2 scanner so I'll use that and report back with results, on a side note, a year ago I didn't have the scanguage but I did get this error, blinking cruise with constant check engine, I used my dads scanner, it said I had a valve stuck open, I drove it over to Subaru and they said the same, so I'll be sure to report back with any good finds, good luck everyone and safe driving!
 

·
Registered
2010 Forester
Joined
·
1 Posts
more of the same

I have a blinking cruise light, steady on check engine and steady on 'vehicle dynamics control OFF' indicator. It's a 2010 forester and less than 10k/10 months old...UGH.
 

·
Registered
2010 Forester XT
Joined
·
2 Posts
same as others

I have the exact same issue as 'notthrilled'. I'm scheduled to take mine to the dealer this Friday (Aug 13th). When I asked the service desk what it could be, he stated that the 2010 Foresters are extremely sensitive and it could be the slightest thing...from the gas cap not being on properly to an actual issue. When I asked why all three lights are occurring (blinking cruise light, steady on check engine and steady on 'vehicle dynamics control OFF' indicator)...he stated that it revolves around the 'check engine'. Once check engine lights up, it disables the 'cruise'..hence blinking cruise...and disables the VDC. :confused: I have not felt any disturbances within the engine...still performs. Once I hear back on Friday (or Saturday if they hold on to it), I'll post a follow up. Notthrilled, let me know as well if you discover anything in the meantime.
 

·
Registered
2006 V50 T5 6spd Manual
Joined
·
2,519 Posts
I just got the same code on our '05 XS 4EAT yesterday. Didn't have the SGII in the car, so had to drive three hours home without cruise control, using the annoyingly springy-stiff drive by wire gas pedal. :|
 

·
Registered
2010 Forester XT
Joined
·
2 Posts
same as others

My lights disappeared and everything went back to normal about 4 days later and 150 miles or so. Still took it into the dealer. They ran their checks and said that the gas cap was not orginally secure. The lights went off and back to normal because after I filled the tank, I secured the cap properly...which led to the computer resetting itself after about 30-50 miles. So now when I refuel, I make certain that I properly slide the cap on perfectly, push it in slightly and turn away. I have not had any other issues since (no lights). Not sure if it was BS or not, but they did state that they made the newer Foresters overly sensative. For now I'll buy the reason.
 

·
Registered
2011 Forester XT 4eat
Joined
·
127 Posts
04 Eat here and it did it to me while bombing up a hill out of a tunnel in traffic last Saturday. I set the cruise and like ten seconds later it wend off and started flashing and the cel came on.

I did just install a catless uppipe and neglected to get a resistor for the egt so we'll see.

Could not figure out how to pull codes. On My Nissan I just turn a flathead screwdriver in a kind of adjustable slot in the side of the ecu and it flashes out a code out on the cel on the dash. Do I have to go to Autozone or somewhere to check?

I reset the ecu by disconnecting the battery and I pumped the brake a few times. So far its fine. No new cel. Managed to stop by radioshack to install a 2.2k ohm resistor in the egt harness plug.
 

·
Registered
2004 Forester XT
Joined
·
11 Posts
Did you guys get any resolution? I just picked up my '04 FXT with auto trans after the engine was rebuilt. 25 miles down the road it popped up CEL & flashing cruise. Read the code at home with new Scangauge II (software version 3.17) and it shows P0000.

Car seems to be running perfectly.
 

·
Registered
2010 Forester 2.5 MT
Joined
·
117 Posts
Yet another case of Mystery CEL/VD/CCL

Another case for the history books

1 year old 2010 MT and this happened to me yesterday.
  1. 59F, clear and sunny with some wind.
  2. Had parked for a few minutes to offload cabbage from the trailer.
  3. When I got going again I noticed the CEL on steady, VD on steady and Cruise blinking.
No other untoward things going on, although I seemed to smell hot brake from time to time all the way home. Checked the wheels and no unusual heating of the brakes. I drive like a grandma anyway. So I went to deliver another load of cabbage and knew that would take me close to the dealer. The idea was to stop into the service bay and see what they might do. However, after delivering the last load the CEL and VD went out by themselves. Brake pedal feels a bit harder. (See brake discussions. I have a really soft pedal the dealer says is nothing)

:icon_idea:My only thought was that a piece of swarf might have gotten into the wheel rotation sensors since: a) I was driving in a field to pick up the cabbage, b) Lots of leaves blowing around, one could have somehow gotten jammed somewhere in the wheel.
 

·
aka DMax in Alaska
'06 Mini Cooper S JCW 6MT
Joined
·
787 Posts
I just got the same code on our '05 XS 4EAT yesterday. Didn't have the SGII in the car, so had to drive three hours home without cruise control, using the annoyingly springy-stiff drive by wire gas pedal. :|
I know this is an old post but next time this happens to anyone, simply disconnecting the negative battery terminal for a few minutes will clear all the codes too.

Just drop a 10mm wrench (at least that is what I needed) in the glovebox and when the code hits, pull over, shut everything down, disconnect the battery for a minute or two, reconnect the battery, and away you go. The code is cleared, and your Cruise Control is restored.

My issue stemmed from an occasional overboost and resulting fuel cut until I dropped the VF43 in there.
 

·
Registered
Joined
·
1 Posts
I know this is an old post but next time this happens to anyone, simply disconnecting the negative battery terminal for a few minutes will clear all the codes too.

Just drop a 10mm wrench (at least that is what I needed) in the glovebox and when the code hits, pull over, shut everything down, disconnect the battery for a minute or two, reconnect the battery, and away you go. The code is cleared, and your Cruise Control is restored.

My issue stemmed from an occasional overboost and resulting fuel cut until I dropped the VF43 in there.
I don't have a code reader and there seems to be nothing noticeably wrong with my 2005 XS (other than the solid CEL and flashing Cruise). If I were to clear the codes in this manner, would the warning lights come right back if there was an actual problem?
 
1 - 20 of 66 Posts
Top