Last post on Mar 07, 2013 at 10:38 AM
You are in the Subaru Legacy & Outback
What is this discussion about?
Subaru Legacy, Subaru Outback, Wagon
#39 of 406 Re: 2001 Subaru Legacy Check Engine Light "N/A" [ateixeira]
Jan 29, 2008 (9:06 pm)
Hello there. I happened across your post and you just might be the only person who can help. I have a 1995 Subaru Legacy and the Check Engine Light has come on. I've gone to Advance Auto and have been told they can only read 1997 to current and the best price I received to have a mechanic read the code is $80. I really do not want to pay $80 for something that might be a $20 fix. I am in the Maryland area and was wondering if your scanner is able to read the code for a 1995 Subaru Legacy.
#40 of 406 Re: 2001 Subaru Legacy Check Engine Light "N/A" [lostinmaryland]
Jan 30, 2008 (7:14 am)
Well, let's see, I have this model, pictured here:
It is an OBDII reader. There was OBD version I.
Does anyone know when Subaru switched, and if an OBDII scanner will read codes from earlier models?
I know that my Miata, for instance, is OBD v1, but it's a 1993.
Maybe check to see if the port is the same on your 95 Legacy? Let me know. It's under the dash board near the driver's left knee.
Edit: this is what the plug looks like:
#41 of 406 Subaru Check Engine Light
Jan 31, 2008 (1:20 pm)
Now my check engine light is on. It may be off when I start the car again. Doesn't seem to be any rhyme or reason to it. It's off as often as it's on. Just weird.
#42 of 406 Check Engine Light
Jan 31, 2008 (1:24 pm)
Oh, I was looking on Ebay. Not sure how good that is, but they have a bunch of scanners. You could check with the seller and see if it's compatible with your '95 Subaru. Worth a shot anyway.
#43 of 406 Re: Check Engine Light [horspoor]
Jan 31, 2008 (11:08 pm)
OBDII Readers won't read OBDI The plugs aren't the same, etc. OBDI can be read by connecting the test leads to each other and counting blinks of the CEL. Each car is different so you have to check the repair manula of that car.
'95 Imprezas were OBDII, and '96 Legacies are OBDII IIRC.
Motorsports and Modifications Host
#44 of 406 Boy, am I glad to see this thread....
Feb 02, 2008 (3:11 pm)
I happen to have a 2005 Legacy wagon, same as one of the posters here - 19,000 miles on the 2.5 engine. The CEL came on, followed by the blinking cruise. I bought my car used (do I still have the power train warranty, or do I 'lose' that since it's used, not through a dealer?). I tried having the OBD II scanner, but maybe the shops' wasn't updated; no codes were read. I've been doing some searching on the net, and one site notes that Subarus use a bit different code - they recommended an OBD II with VAT. I'd be curious - do I need to go that route - but am re-assured some here have had success with the less expensive units.
I bought this car based on what I'd thought was a stellar reputation for the company. Am I confused on that point (I've been reading a lot of folks saying Subaru is famous for 'issues' such as this - I'm not looking for another 'dependent', if ya know what I mean).
I've checked my gas cap; I haven't checked my fuses. I expect I'm wasting my time until I get an OBD II readout - correct?
#45 of 406 Re: Boy, am I glad to see this thread.... [georgejung]
Feb 03, 2008 (9:13 am)
the factory warranty is good regardless of where you purchased it or how many owners it has had. 3/36 bumper to bumper , 5/60 powertrain. yours should still be covered. you will have to go to a dealer for the work though.
#46 of 406 Re: Boy, am I glad to see this thread.... [cptplt]
Feb 03, 2008 (7:39 pm)
Thanks for the info, cptpit. I'll check tomorrow, see when I can get it in for an evaluation.
BTW, I've been reading a lot about different OBD II scanners; most that I've checked on claim that the Subaru needs one that also has VAG (don't know what that stands for, but apparently reads more codes). I have the 2.5 normally aspirated engine; any suggestions on which I should purchase? (It'd be nice to be able to at least get an idea, for future reference, what's wrong before hauling into the dealership.) Thanks.
#47 of 406 Re: Boy, am I glad to see this thread.... [georgejung]
Feb 04, 2008 (12:45 pm)
VAG = Volkwagon Auto Group, maybe?
#48 of 406 CEL Horrors - 2002 Outback Base Wagon
Feb 04, 2008 (7:33 pm)
I'll start off this post by saying that the dealer's service department that I have been using acknowledges that they have never seen a series of Check Engine Light (CEL) problems like the ones they have seen with my vehicle. I'm hoping that that is not simply a diplomatic way of saying I have a lemon (perhaps the only one on the roadways of Colorado).
Let me give a little history of these problems so that I can get your collective thoughts on whether they are all related and symptomatic of a larger or missed problem or simply unfortunate isolated incidents.
My 2002 Outback Wagon is the base model with a standard 4 cyl. engine, automatic transmission. It currently has approx. 93k miles on it.
Back in late 2005, when I had approx. 51k miles on the vehicle, I started getting constant Check Engine lights. The dealer pulled a Code P0420 and started off by replacing a Fuel (or Oxygen) Sensor. (The dealer indicated that these were the same things.) When the CELs persisted approx. 2500 miles later, and the same code reappeared, the dealer replaced the catalytic converter. I went 15k more miles and the problem resurfaced - same code. The dealer cleared the computer and told me to drive on it some more. At 73787 miles, when the CEL and same P0420 code came back, the dealer replaced the same fuel/Oxygen sensor. Then, at 76874 (now February 2007) -- same code came back and the dealer put in a new catalytic converter.
Up to this point, I simply got constant CELs and it did not really affect driving performance in any perceptible way. That changed this past fall, when I noticed that the vehicle would sputter and I would get intermittent engine vibrations, usually at idle or low RPM. Occasionally, the vibrations and sputtering would get more intense and sometimes at higher RPM (e.g. 2k). I also noticed that I would typically see the problems when the weather turned colder and in stop-and-go traffic or at higher altitudes (in the mountains at 9000 feet and above). The CEL would blink for 20-30 seconds and then turn constant.
When I brought the car to the dealer in November with approx. 89k miles, at first they could not pull a code, and simply cleared the computer. The problem reappeared and technicians were able to pull a code: P0302 (cyl. 2 misfire). I was up for my 90K service, so that was done, replacing the spark plugs, and I also had them do a fuel injector flush at their recommendation.
My problems came back in about 2 weeks and less than 2000 miles. This time the technicians pulled a P0420 code. They cleared the computer, told me to drive it some more, but warned that if the code came back I would be due for my fourth catalytic converter.
The same symptoms persisted but when I brought the vehicle back to the dealer in late January, with approx. 93k, the techs pulled a P0302 code (the cyl 2 misfire) again. At their recommendation, I had the ignition coil assembly and ignition wires replaced. Although it was not documented, the technician also told me he did a comprehension test, which came back with normal results. They told me to use better gasoline and drive on it.
The same problems -- engine sputtering/engine vibs, blinking CELs, etc. - came back within a week and less than 200 miles (using the better grade gasoline). The tech who worked on my car confessed that he was not sure whether the new coils and wires would solve the problem but all that the dealer can offer at this point is the recommendation that I continue to drive on it and keep putting in better grades of gasoline. Otherwise, they are out of ideas. (The service manager confessed that he did not think gasoline quality was really the issue.)
So the short questions I have following this long post are these: Are the problems interrelated? Has something been overlooked? (A friend mentioned that loose connections with the air filter may be a culprit.) Any thoughts on what steps to take next?
I would be grateful for any suggestions or advice.