Welcome to AutoForumz.com!
FAQFAQ   SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

2003 Forester: CEL but no code

 
   car problems (Home) -> Subaru RSS
Related Topics:
SRS light on 2003 forester - has anyone had with this, I don't want to go to the dealer and be soaked..

Head and Tail Lights Won't Go Off on 2003 Forester - Yep, that's my problem in the Subject. I had to the battery tonight. Possibly the timer is defective that turns out the lights when the the ignition is turned off while the lights are on. It may have been by an earlier event. A..

considering '05 Forester - My wife and I were on the lot today and each and every Forester had a $1495 US markup. The Legacy's and Impreza's were also right there and same markup! The separate dealer sticker had something like showing this $1495 in..

New Forester? - I own a 2002 model Forester S. I bought it in summer 2001 when the 02's came out. At 55k miles, it's the best vehicle I've ever owned. Now I'm thinking of buying a new Forester and give the one to my wife (who loves driving it). My question to..

05' WRX and Forester XT - Is of the 05' WRX and Forester XT (turbo engines) on par with non-turbo models? I mean long term use like 200K + miles. A.
Next:  93 Wrx total loss of power  
Author Message
Mike Bender

External


Since: Aug 06, 2004
Posts: 11



(Msg. 1) Posted: Thu May 29, 2008 12:55 am
Post subject: 2003 Forester: CEL but no code
Archived from groups: alt>autos>subaru (more info?)

Hi all,

About 2.5 weeks/300 miles ago my '03 Forester (US) started showing a
check engine light. I hooked up my OBDII code reader and when I read the
display, there was not code recorded. I thought that maybe there was some
noise in the system, so I used the code reader to clear the CEL, which it
did. Shortly after I started the car the next day, the CEL came back
again with no code recorded. I've started leaving my code reader
connected while I'm driving to see if it can pick up a transient code,
but nothing has been recorded. Some other things to note:

- the car runs great and my fuel mileage is normal

- when I reset the CEL, the I/M readiness monitors were also reset. In
the two weeks or so since then, the oxygen sensor, catalyst and
evaporative system monitors have yet to come ready

- don't know if it matters, but about 6 weeks ago, I had the pistons
replaced under warranty for piston slap. At the same time, they replaced
the cam belt tensioner, cam belt and various seals.

I've done some googling about this, but everything I've found (none of it
Subaru specific) was basically "your computer is fried, buy a new one".
It seems to me that if the computer was actually gone, the car wouldn't
run normally.

Ad<thanx>vance for any assistance...

- Snuffy -

--
Feeding the trolls since 1989.

 >> Stay informed about: 2003 Forester: CEL but no code 
Back to top
Login to vote
dnoyeB

External


Since: May 29, 2008
Posts: 2



(Msg. 2) Posted: Thu May 29, 2008 7:02 am
Post subject: Re: 2003 Forester: CEL but no code [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Thu, 29 May 2008 00:55:04 +0000, Mike Bender wrote:

> Hi all,
>
> About 2.5 weeks/300 miles ago my '03 Forester (US) started showing
> a
> check engine light. I hooked up my OBDII code reader and when I read the
> display, there was not code recorded. I thought that maybe there was
> some noise in the system, so I used the code reader to clear the CEL,
> which it did. Shortly after I started the car the next day, the CEL came
> back again with no code recorded. I've started leaving my code reader
> connected while I'm driving to see if it can pick up a transient code,
> but nothing has been recorded. Some other things to note:
>
> - the car runs great and my fuel mileage is normal
>
> - when I reset the CEL, the I/M readiness monitors were also reset. In
> the two weeks or so since then, the oxygen sensor, catalyst and
> evaporative system monitors have yet to come ready
>
> - don't know if it matters, but about 6 weeks ago, I had the pistons
> replaced under warranty for piston slap. At the same time, they replaced
> the cam belt tensioner, cam belt and various seals.
>
> I've done some googling about this, but everything I've found (none of
> it Subaru specific) was basically "your computer is fried, buy a new
> one". It seems to me that if the computer was actually gone, the car
> wouldn't run normally.
>
> Ad<thanx>vance for any assistance...
>
> - Snuffy -

Anytime there is a code, it should be recorded. Maybe there is something
wrong with your code reader. Hopefully its set to read both active codes
and codes stored in history!?


CL

 >> Stay informed about: 2003 Forester: CEL but no code 
Back to top
Login to vote
Carl 1 Lucky Texan

External


Since: Jan 20, 2004
Posts: 647



(Msg. 3) Posted: Thu May 29, 2008 10:29 pm
Post subject: Re: 2003 Forester: CEL but no code [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

dnoyeB wrote:
> On Thu, 29 May 2008 00:55:04 +0000, Mike Bender wrote:
>
>
>>Hi all,
>>
>> About 2.5 weeks/300 miles ago my '03 Forester (US) started showing
>> a
>>check engine light. I hooked up my OBDII code reader and when I read the
>>display, there was not code recorded. I thought that maybe there was
>>some noise in the system, so I used the code reader to clear the CEL,
>>which it did. Shortly after I started the car the next day, the CEL came
>>back again with no code recorded. I've started leaving my code reader
>>connected while I'm driving to see if it can pick up a transient code,
>>but nothing has been recorded. Some other things to note:
>>
>> - the car runs great and my fuel mileage is normal
>>
>> - when I reset the CEL, the I/M readiness monitors were also reset. In
>>the two weeks or so since then, the oxygen sensor, catalyst and
>>evaporative system monitors have yet to come ready
>>
>> - don't know if it matters, but about 6 weeks ago, I had the pistons
>>replaced under warranty for piston slap. At the same time, they replaced
>>the cam belt tensioner, cam belt and various seals.
>>
>>I've done some googling about this, but everything I've found (none of
>>it Subaru specific) was basically "your computer is fried, buy a new
>>one". It seems to me that if the computer was actually gone, the car
>>wouldn't run normally.
>>
>>Ad<thanx>vance for any assistance...
>>
>> - Snuffy -
>
>
> Anytime there is a code, it should be recorded. Maybe there is something
> wrong with your code reader. Hopefully its set to read both active codes
> and codes stored in history!?
>
>
> CL

Yep, very curious. Has this reader worked before on your car? Any chance
the reader could be tested on another sube? I THINK, there are 4
protocols for OBDII and the reader must read the ISO/w'ever style to
read a sube. I think a few cheaper readers won't read subes - but then
it seems unlikely it could clear the computer. weird.

I think it takes a number of heat up/cool down drive cycles to acheive
'readiness'. If you drove only short distances, perhaps that's why the
readiness hasn't completed?

Carl


--
to reply, change ( .not) to ( .net)
 >> Stay informed about: 2003 Forester: CEL but no code 
Back to top
Login to vote
Mike Bender

External


Since: Aug 06, 2004
Posts: 11



(Msg. 4) Posted: Sat May 31, 2008 1:06 am
Post subject: Re: 2003 Forester: CEL but no code [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Carl 1 Lucky Texan <alckytxn.DeleteThis@swbell.not> wrote in
news:CwK%j.2314$uE5.2214@flpi144.ffdc.sbc.com:

> dnoyeB wrote:
>> On Thu, 29 May 2008 00:55:04 +0000, Mike Bender wrote:
>>
>>
>>>Hi all,
>>>
>>> About 2.5 weeks/300 miles ago my '03 Forester (US) started
>>> showing a
>>>check engine light. I hooked up my OBDII code reader and when I read
>>>the display, there was not code recorded. I thought that maybe there
>>>was some noise in the system, so I used the code reader to clear the
>>>CEL, which it did. Shortly after I started the car the next day, the
>>>CEL came back again with no code recorded. I've started leaving my
>>>code reader connected while I'm driving to see if it can pick up a
>>>transient code, but nothing has been recorded. Some other things to
>>>note:
>>>
>>> - the car runs great and my fuel mileage is normal
>>>
>>> - when I reset the CEL, the I/M readiness monitors were also reset.
>>> In
>>>the two weeks or so since then, the oxygen sensor, catalyst and
>>>evaporative system monitors have yet to come ready
>>>
>>> - don't know if it matters, but about 6 weeks ago, I had the pistons
>>>replaced under warranty for piston slap. At the same time, they
>>>replaced the cam belt tensioner, cam belt and various seals.
>>>
>>>I've done some googling about this, but everything I've found (none
>>>of it Subaru specific) was basically "your computer is fried, buy a
>>>new one". It seems to me that if the computer was actually gone, the
>>>car wouldn't run normally.
>>>
>>>Ad<thanx>vance for any assistance...
>>>
>>> - Snuffy -
>>
>>
>> Anytime there is a code, it should be recorded. Maybe there is
>> something wrong with your code reader. Hopefully its set to read
>> both active codes and codes stored in history!?
>>
>>
>> CL
>
> Yep, very curious. Has this reader worked before on your car? Any
> chance the reader could be tested on another sube? I THINK, there are
> 4 protocols for OBDII and the reader must read the ISO/w'ever style to
> read a sube. I think a few cheaper readers won't read subes - but then
> it seems unlikely it could clear the computer. weird.
>
> I think it takes a number of heat up/cool down drive cycles to acheive
> 'readiness'. If you drove only short distances, perhaps that's why the
> readiness hasn't completed?
>
> Carl
>
>

Yup, I've used this reader before on my Subaru to diagnose an
intermittent misfire due to a defective coil pack that was eventually
replaced under warranty about 3 years ago. I also use this reader on my
wife's Hyundai with no problems.

The driving I did after I reset the computer was a combination of
city/expressway for about 10 days with most trips being my 20 minute
commute with speeds up to ~60 mph, and some longer trips (about 45-60
minutes) at least one of which was about 20-30 minutes on an interstate.
This kind of a driving pattern in the past has been enough to bring the
monitors to readiness. I'm really puzzled by this and I really don't want
to go visit the wallet-vac at the Subaru dealership. Luckily my emissions
inspection was just last month so I've got nearly a year to figure this
out.

- Snuffy -

--
Feeding the trolls since 1989.
 >> Stay informed about: 2003 Forester: CEL but no code 
Back to top
Login to vote
Carl 1 Lucky Texan

External


Since: Jan 20, 2004
Posts: 647



(Msg. 5) Posted: Sat May 31, 2008 1:06 am
Post subject: Re: 2003 Forester: CEL but no code [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Mike Bender wrote:

> Carl 1 Lucky Texan <alckytxn.TakeThisOut@swbell.not> wrote in
> news:CwK%j.2314$uE5.2214@flpi144.ffdc.sbc.com:
>
>
>>dnoyeB wrote:
>>
>>>On Thu, 29 May 2008 00:55:04 +0000, Mike Bender wrote:
>>>
>>>
>>>
>>>>Hi all,
>>>>
>>>> About 2.5 weeks/300 miles ago my '03 Forester (US) started
>>>> showing a
>>>>check engine light. I hooked up my OBDII code reader and when I read
>>>>the display, there was not code recorded. I thought that maybe there
>>>>was some noise in the system, so I used the code reader to clear the
>>>>CEL, which it did. Shortly after I started the car the next day, the
>>>>CEL came back again with no code recorded. I've started leaving my
>>>>code reader connected while I'm driving to see if it can pick up a
>>>>transient code, but nothing has been recorded. Some other things to
>>>>note:
>>>>
>>>>- the car runs great and my fuel mileage is normal
>>>>
>>>>- when I reset the CEL, the I/M readiness monitors were also reset.
>>>>In
>>>>the two weeks or so since then, the oxygen sensor, catalyst and
>>>>evaporative system monitors have yet to come ready
>>>>
>>>>- don't know if it matters, but about 6 weeks ago, I had the pistons
>>>>replaced under warranty for piston slap. At the same time, they
>>>>replaced the cam belt tensioner, cam belt and various seals.
>>>>
>>>>I've done some googling about this, but everything I've found (none
>>>>of it Subaru specific) was basically "your computer is fried, buy a
>>>>new one". It seems to me that if the computer was actually gone, the
>>>>car wouldn't run normally.
>>>>
>>>>Ad<thanx>vance for any assistance...
>>>>
>>>>- Snuffy -
>>>
>>>
>>>Anytime there is a code, it should be recorded. Maybe there is
>>>something wrong with your code reader. Hopefully its set to read
>>>both active codes and codes stored in history!?
>>>
>>>
>>>CL
>>
>>Yep, very curious. Has this reader worked before on your car? Any
>>chance the reader could be tested on another sube? I THINK, there are
>>4 protocols for OBDII and the reader must read the ISO/w'ever style to
>>read a sube. I think a few cheaper readers won't read subes - but then
>>it seems unlikely it could clear the computer. weird.
>>
>>I think it takes a number of heat up/cool down drive cycles to acheive
>>'readiness'. If you drove only short distances, perhaps that's why the
>>readiness hasn't completed?
>>
>>Carl
>>
>>
>
>
> Yup, I've used this reader before on my Subaru to diagnose an
> intermittent misfire due to a defective coil pack that was eventually
> replaced under warranty about 3 years ago. I also use this reader on my
> wife's Hyundai with no problems.
>
> The driving I did after I reset the computer was a combination of
> city/expressway for about 10 days with most trips being my 20 minute
> commute with speeds up to ~60 mph, and some longer trips (about 45-60
> minutes) at least one of which was about 20-30 minutes on an interstate.
> This kind of a driving pattern in the past has been enough to bring the
> monitors to readiness. I'm really puzzled by this and I really don't want
> to go visit the wallet-vac at the Subaru dealership. Luckily my emissions
> inspection was just last month so I've got nearly a year to figure this
> out.
>
> - Snuffy -
>
> --
> Feeding the trolls since 1989.

WEll, I think it may be time to find an Autozone or 'friendly mechanic'
to see if their reader can get a code. I'd say there could be merit to
the 'fried computer' (at least the scanner interface port) IF a
different reader fails in a similar manner.

good luck

Carl


--
to reply, change ( .not) to ( .net)
 >> Stay informed about: 2003 Forester: CEL but no code 
Back to top
Login to vote
Display posts from previous:   
   car problems (Home) -> Subaru All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]