33 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFlashing Check Engine Light
Leading reported evidence
Check codes....nada
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Check codes....nada' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check codes' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I was riding hard on the autobahn and while going for top speed at about 310 km/h the check engine flashed.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
The only diagnostics I've done is check the oil level, which is fine.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The Turbo uses wide band sensors for more precise fuel control so these want to be operating in top form to ensure the more precise fueling actually happens.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
33 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
they reset all error codes and 600 miles later including a track day, no more codes or issues.
Got home tonight from a spirited drive. When I slowed down my check engine light started to flash. I parked the car outside. About 20 minutes later I started the car again and pulled it into the garage. The check engine light did not flash at that time.
The only diagnostics I've done is check the oil level, which is fine. Was my car just telling me "nice drivin' Tex"?
You need to use a scanner (a generic OBDII will do) to retrieve the code(s) and go from there. Also, if the CEL is flashing, it means you will damage the cats if keep driving. Let us know what you find.
I'm not aware of a blinking CEL suggesting anything in particular regarding your cats, but it does mean the car needs immediate attention and the fault it found isn't just something to drive around with. As Ahsai suggested, you need to pull the codes to figure out what's going on.
A blinking CEL technically means the engine is misfiring. Damage to the cats can occur when the fuel in the cylinder is not ignited properly and a significant amount makes it into the exhaust system (where it may ignite and cause damage).
Depends on price range
$20 mini obdII Bluetooth + the "Torque" app (you need an android phone though). Real-time data, reads and resets codes.
$50 actron, no real-time data
$75 innova 3040 real-time data
$290 durametric, Porsch specific and most powerful including airbag reset, cam deviation reading, etc.
You would need real-time data to diagnose any further than just reading the codes.
Hi guys,
picking up this post. My car had a flashing cell too the other day. I was riding hard on the autobahn and while going for top speed at about 310 km/h the check engine flashed. No weird sound, smoke nothing. I decelerated and after about like 15 endless seconds the light were gone. I checked codes....nada. My mech said the lambda probes wont last forever. So i guess in my case one probe is getting old.
My car (996 turbo) got 200 cell cats and tune
If one O2 sensor getting old they all are getting old. Replace in sets. The ones in my 2003 Turbo lasted around 130K miles. Some get more miles, but most get fewer miles out of these.
The Turbo uses wide band sensors for more precise fuel control so these want to be operating in top form to ensure the more precise fueling actually happens.
Plugs too don't last for long in these Turbo engines. Be sure the plugs are not past their change by miles or date. At the same time check the coils. There are some who believe the coils should be replaced on a regular or semi-regular basis, and this applies also to the MAF. I've always been a don't fix it if it ain't broke type but a Turbo is hard on its coils. The turbo heat plays a role I think.
The MAF runs hotter and because the Turbo makes so much HP which requires a lot of air the MAF is working harder than it would on a NA 3.6 engine. As a result the MAF can have a shorter life span.
Also, a tune makes more demands on the engine and its subsystems and can bring out a weakness that the stock tune didn't.
I really don't know how you go from flashing CEL (which is not good) to everything is perfect, without ever reading the codes or having any knowledge what caused the flashing cel. Keep on truckin' I guess.
Flashing CEL is a rich misfire. If the CEL goes dark the misfire condition is gone and there will be no active error codes stored. There might be permanent ones -- that is errors that can only be erased by the DME after it has counted enough warm up cycles with the error condition absent -- and there might be pending codes.
It seemed very ironic, but while driving my 03 C4S to my indy shop for some other repairs, how opportunistic that it threw a Blinking CEL and said to drive directly to dealer for diagnostic.
their Porsche OBDII reader showed RH cat had thrown a code. they reset all error codes and 600 miles later including a track day, no more codes or issues.
My 996 Turbo check engine light has been on and off. Took it to mechanic and couldn't find any fault code. He reset it and was fine for a few days then came back on. Second time he diagnosed the fault code read camshaft solenoid. He said it might be due to car sitting too long not driven. Timing is off. He reset it and now it's back on.
Any advice?
What are or were the code or codes?
The 996 Turbo can experienced a cracked solenoid bracket which can cause VarioCam related error codes.
Here is a link to a thread and post #34 has a parts diagram with the brackets circled.
https://rennlist.com/forums/996-turb...and-6-a-3.html
My Turbo has never had a problem with its brackets or solenoids/actuators, but my 2002 Boxster had a solenoid/actuator fail and both were replaced.
So if the brackets are good and the error code or codes come back and they point to the solenoid/actuator you mght need to have the one pointed to by the error code replaced.
But worry about this when/if the time comes.