Ck Engine due to unplugging exhaust flap?
05-30-2009, 01:50 PM
#1
Rennlist Member
Thread Starter
Ck Engine due to unplugging exhaust flap?
I just picked up my car from the dealer.
Check engine light came on last week.
It was no warranty, (Paid for a rental car only.) because I unplugged the plug for the exhasut control, but I did that 7000 mile ago in September last year when I bought the car?
Anyone else had the check engine light come on because of that.
I like the sound better at low RPM and I have it unplugged again to see if the check engine light comes on again...
Check engine light came on last week.
It was no warranty, (Paid for a rental car only.) because I unplugged the plug for the exhasut control, but I did that 7000 mile ago in September last year when I bought the car?
Anyone else had the check engine light come on because of that.
I like the sound better at low RPM and I have it unplugged again to see if the check engine light comes on again...
05-30-2009, 07:22 PM
#3
Rennlist Member
Thread Starter
just make sure you plug it back in before taking it in next time.
05-30-2009, 11:24 PM
#5
Rennlist Member
Thread Starter
So what was the "fault" that triggered the CEL???
I could not find it via Google, etc; It says on my invoice:
"Tuning flap selenoid disconnected VAL. OBDII performed: DTC P1682 Output stage exh flap control/exh. flap pressure sensor fault no signal/communication"
Seems logical when disconnected, but why no warning sooner? Why no warning now?
06-02-2009, 11:41 AM
#6
Burning Brakes
This is odd. I know of a similar experience where a car throw a CEL and needed to be evaluated by Porsche. The owner had the flap sensor disconnected for quite a while but the code was thrown while it was on a dyno.
Somehow the sensors on the car noticed the flap during the dyno run. Running on the street was not an issue.
Were you on a dyno or on-track at the time when the CEL was thrown?
Somehow the sensors on the car noticed the flap during the dyno run. Running on the street was not an issue.
Were you on a dyno or on-track at the time when the CEL was thrown?
06-02-2009, 10:22 PM
#7
Rennlist Member
Thread Starter
The only thing unusual was that I forgot to turn of the ignition and push started the car.
After that the fuel gauge stopped working, I just put gas in, so I knew I was OK.
After running for 4 days with the needle on empty the CEL came on. One day later, after 5 days and 100 miles, I refueled and the gauge started working again, but the CEL stayed on.
Seems all unrelated?
No Dyno, not even driven hard or anything?
After that the fuel gauge stopped working, I just put gas in, so I knew I was OK.
After running for 4 days with the needle on empty the CEL came on. One day later, after 5 days and 100 miles, I refueled and the gauge started working again, but the CEL stayed on.
Seems all unrelated?
No Dyno, not even driven hard or anything?
Trending Topics
06-03-2009, 01:42 PM
#8
Rennlist Member
"It was no warranty, (Paid for a rental car only.) because I unplugged the plug for the exhasut control, but I did that 7000 mile ago in September last year when I bought the car?"
I would like to unplug mine, but don't know where to unplug them. Can you explain how to do unplug them?
I would like to unplug mine, but don't know where to unplug them. Can you explain how to do unplug them?
06-03-2009, 03:22 PM
#9
Burning Brakes
The only thing unusual was that I forgot to turn of the ignition and push started the car.
After that the fuel gauge stopped working, I just put gas in, so I knew I was OK.
After running for 4 days with the needle on empty the CEL came on. One day later, after 5 days and 100 miles, I refueled and the gauge started working again, but the CEL stayed on.
Seems all unrelated?
No Dyno, not even driven hard or anything?
After that the fuel gauge stopped working, I just put gas in, so I knew I was OK.
After running for 4 days with the needle on empty the CEL came on. One day later, after 5 days and 100 miles, I refueled and the gauge started working again, but the CEL stayed on.
Seems all unrelated?
No Dyno, not even driven hard or anything?
It sounds like the car doesn't monitor the exhaust flap until something triggers the ecu to read for it. Perhaps your push start caused the computer to run some sort of system check above and beyond what happens when you typically start your car. Would make sense since my friend's car started throwing codes due to ABS and being on the dyno. Both are situations outside the "norm" and appears to trigger some sort of fault search, leading it to the exhaust flap switch disconnect getting noticed.
Who knows...
