24 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCode Clearing?
Reported or suspected cause
muffler will need
Suggestion or failed attempt
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
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 suspect a cause
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.
Suspected cause
On the 996 I suspect the muffler will need to come off its bracket.
Leading evidence: 'muffler will need' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'muffler will need' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Recommend unit' (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 suspect a cause
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.
Suspected cause
Always a useful starting point for any issue, as the problem is often not what you think it is.
Outcome qualification: Negation, uncertainty or missing explicit repair resolution overrides the raw extraction signal.
Recommend unit
Suggestion or failed attempt
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 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 segue here is whether indeed I should invest in a code reader and if so, the recommended unit?
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
“The segue here is whether indeed I should invest in a simpler air cooled 911 and if so, the recommended unit?”
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
Definitely replace the coil packs if you get a chance.
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
First change, when the car would have only done 1500kms max (test drives around Sydney and then trip back to Tassie), the oil looked as if it had done 20,000kms.
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 solution advised by Autohaus to my mechanic was to do an oil change using an engine cleaner, replace and drive the ring out of it, and do it all again.
Outcome qualification: Negation, uncertainty or missing explicit repair resolution overrides the raw extraction signal.
Coverage and how to read this overview
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.
24 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Porsche Forum Australia: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 1 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
Same next time after 5000kms, then back to normal afterwards.
So the highlight of my 3000km trip to Luftwasser was a coil pack failure and CEL light 2 hours from home
😕
Big thanks to
@Port 911
and the Port Mac crew for fitting me into an already well loaded wagon and getting me home. The car enjoyed a night in the Heatherbrae Pies carpark and I retrieved it with a trailer the following morning. I was very lucky the failure was on the very back end of a wonderful week of driving.
Realistically the car has done well - the coil packs are the original 18 year old units and the last service noted that they would be due getting close to failure. And I did
drive
the car
. I have new coil packs ordered and on the way, but my question is whether I'll need a code reader to clear the CEL, or will it self clear with new coils?
The segue here is whether indeed I should invest in a code reader and if so, the recommended unit?
TIA
Luckily for me a good friend lives 5 mins away and has the Durametrics code scanner, it’s come in handy a few times... as I live about an hour from my preferred shop, so it has saved me a handful of 2 hour return journeys for a 5 min code scan.
I have been pleased with the iCarSoft device. Lots of info and choices and I don’t need to buy an old PC laptop to use it in the car, as on the more costly Durametric . I inherited a new set of Beru coil packs with the car and should probably fit those at the next service. It has only done 50K but I guess coil packs fail with time as much as use or heat cycles.
Definitely replace the coil packs if you get a chance. I upgraded mine to the newer 997 versions and NGK Ruthium plugs. Noticable difference in idle and start...
Any of you that have had the CEL and a failed coil pack - can you recall if the code needed clearing, or will it self-clear with the new coil packs (I have the newer 997# packs) - not really looking to drop another $300 for the iCarsoft just right now.
No worries John. They are good value for these cars IMO. Always a useful starting point for any issue, as the problem is often not what you think it is. I did the 'packs and plugs on my Boxster and I found a few useful videos on the process. On the 996 I suspect the muffler will need to come off its bracket.
On your trip how did you find the AWD?
Plugs can be done with the mufflers on, but access is a little easier with them removed. The right-rear pot is the most awkward (#4?), but on both sides the bits really in the way are the chassis rail and the muffler bracket that remains attached to the motor, so removing mufflers helps less than you might think. Once heat shields are removed, you're generally working from underneath, or reaching behind the muffler bracket, so the muffler itself isn't really in the way.
Interested re the scanner, I still haven't got around to buying one.
It was a noticeable advantage in 35kmh corners over 2wd compatriots. Shift into 2nd and hammer (don't let off) and the car really pulls itself through the corner.
Well I don't think my wrists have been this sore since I was 13...
I changed over all 6 packs this evening - plugs were only 3k old, so skipped replacing them. I left mufflers and bumper in situ and it was entirely doable with a stubby 1/4 ratchet.
@st3ve
- you're spot on, #4 was a bitch. Too late to start and test - hopefully issues are resolved though.
Looks like the change of coils has done the trick, engine is running well - though I'm a bit anxious and 'hearing' noises and pops etc... which I'm sure were probably there before. For the record though, the CEL remains on. Searching the net indicates it 'may' turn itself off over a few kilometers, but most recommend using a scanner and clearing the code directly, so I've ordered myself an iCarsoft Por V2 unit. Crossing fingers it puts my anxiety to bed!
John, just a secondary thought, your new car is a Tip? From a city area? I had problems with rough running in my old C2 Tip, with CEL light coming on fairly regulalrly. The problem diagnosed was clogging of the variocam actuators with oil. Common problem with Tips driven in city areas if they are driven fully in auto, on freeways where the transmission changes up at lower revs. Oil never really gets hot, and the hot oil doesn't get fully moved around the engine. If the oil is cooler, then it doesn't drain out fully when engine is turned off, and can gum up the works. The solution advised by Autohaus to my mechanic was to do an oil change using an engine cleaner, replace and drive the ring out of it, and do it all again. First change, when the car would have only done 1500kms max (test drives around Sydney and then trip back to Tassie), the oil looked as if it had done 20,000kms. Same next time after 5000kms, then back to normal afterwards. CEL light regularity improved significantly, although I did end up changing the variocam actuators in the end.
The car is a low mileage manual, and I suspect it's been driven quite gently - mostly in metro. My big drive put on 2600kms and I drove it pretty hard in a few places and I do believe under-driven cars come with their own issues.
My big fear was the variocam lifters - not catastrophic, but an expensive job to replace. Touch wood it's just the old coils but I'll monitor the lifters, cheers!
Thought I'd round this thread out (hopefully)
My iCarsoft arrived today and I ran the diagnostics - coil pack #4 had failed (which was the one I suspected after finding a hairline crack), there was also a camshaft position sensor (hall effect) code, but reading up it is likely as a symptom of the misfiring #4. I've cleared all codes and the CEL appears to have cancelled . I'm only able to idle in the garage at the moment due to the severe weather , so a proper drive is going to have to wait. But crossing fingers, it seems to have been resolved.
This is a source reference. Confirm exact model applicability in the original material.
