Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
2007 Avalon Issue Resolved
0 views
Skip to first unread message
hls
May 9, 2012, 10:04:50 AM5/9/12
to
I thought this might be interesting enough to pass on.
Our Avalon has 80K miles, and suddenly the check engine
light came on, vehicle stability control light came on, and the
cruise controls (both laser and standard) stopped working.
Testing indicated the MAF might be bad (low airflow indicated),
and that was replaced.
Tests showed airflow back to specs, fault lights went away for
a while, but returned within 100 miles of driving.
MAF was replaced as "faulty", and air filter was replaced. This
time, mechanic noted that there is a filter in the housing above
the regular air filter and it was cleaned (seems to be integral
with housing).
This fixed all the problems.
Thought this might help someone.
Our Avalon has 80K miles, and suddenly the check engine
light came on, vehicle stability control light came on, and the
cruise controls (both laser and standard) stopped working.
Testing indicated the MAF might be bad (low airflow indicated),
and that was replaced.
Tests showed airflow back to specs, fault lights went away for
a while, but returned within 100 miles of driving.
MAF was replaced as "faulty", and air filter was replaced. This
time, mechanic noted that there is a filter in the housing above
the regular air filter and it was cleaned (seems to be integral
with housing).
This fixed all the problems.
Thought this might help someone.
Jeff Strickland
May 9, 2012, 11:45:58 AM5/9/12
to
As a general rule of thumb, never do anything before pulling codes when the
Check Engine light is on. That is the first step. It is ALWAYS the first
step.
Then, when discussing the symptom set in a newsgroup/automotive repair
forum, give the OBD II Code that was extracted when you pulled codes.
</top post>
"hls" <h...@nospam.nix> wrote in message
news:Admdnb42hNw45DfS...@giganews.com...
Check Engine light is on. That is the first step. It is ALWAYS the first
step.
Then, when discussing the symptom set in a newsgroup/automotive repair
forum, give the OBD II Code that was extracted when you pulled codes.
</top post>
"hls" <h...@nospam.nix> wrote in message
news:Admdnb42hNw45DfS...@giganews.com...
hls
May 9, 2012, 3:26:22 PM5/9/12
to
"Jeff Strickland" <crwl...@yahoo.com> wrote in message
news:joe3d0$o72$1...@dont-email.me...
> As a general rule of thumb, never do anything before pulling codes when
> the Check Engine light is on. That is the first step. It is ALWAYS the
> first step.
>
> Then, when discussing the symptom set in a newsgroup/automotive repair
> forum, give the OBD II Code that was extracted when you pulled codes.
>
The codes were pulled first of all, but I do not have them available.
> the Check Engine light is on. That is the first step. It is ALWAYS the
> first step.
>
> Then, when discussing the symptom set in a newsgroup/automotive repair
> forum, give the OBD II Code that was extracted when you pulled codes.
>
Since the problem was already solved, I wanted to show how one symptom
or problem can trigger other apparently nonrelated warning lights.
Jeff Strickland
May 10, 2012, 11:28:53 AM5/10/12
to
"hls" <h...@nospam.nix> wrote in message
unrelated systems can affect one another. I was not following along very
closely, and maybe I missed the original posting (this appears to be a
follow up), but just in case the codes were not mentioned, my point is that
they are important. Some people tend to troublshoot with a shot gun, and
this costs lots of extra money sometimes. The codes help one change the
troubleshooting techinque from a shotgun to a scalpel.
Many times there are no drivability problems, and it is a reasonable
diagnostic technique to pull the codes and jot them down, then clear them
and wait for the Check Engine light to come up again, then pull codes and
fix the ones that are on both lists. Occasionally CODE1 will be posted that
is not important, but it is held for a long time. You clear it when CODE2
comes along, and then you drive around for a while and CODE2 comes back, you
know that's the one you need to address.
hls
May 17, 2012, 11:37:10 AM5/17/12
to
news:jogmoe$8v8$1...@dont-email.me...
In this particular case, one item which Avalon owners need to focus on
is the "mystery" filter. It was possible to blow this clean(er) but it
could
not be removed and cleaned, nor could it be simply replaced.
Apparently one would have to replace the housing and filter as a unit.
If anyone has done this, or has found a replacement method, I would be
keen to hear about it.
>
> "hls" <h...@nospam.nix> wrote in message
> news:0IOdnb2V65afWDfS...@giganews.com...
Your testing points are well taken.
> "hls" <h...@nospam.nix> wrote in message
> news:0IOdnb2V65afWDfS...@giganews.com...
In this particular case, one item which Avalon owners need to focus on
is the "mystery" filter. It was possible to blow this clean(er) but it
could
not be removed and cleaned, nor could it be simply replaced.
Apparently one would have to replace the housing and filter as a unit.
If anyone has done this, or has found a replacement method, I would be
keen to hear about it.
0 new messages