Hi all, helping a neighbour not my car. Car went in for a service and within 50 miles or so got CEL and major misfire had to baby the car to get it home. Instead of taking it straight back to where it was serviced he plugged in OBD and got 7 pages of errors but didnt make a note :-( No errors were cleared. Following day car started normally and no CEL. I had a look and could see cylinder misfire on all cylinders. cleared errors and took out for drive and got the same eventually took a good 15mins of driving with all ODB cycles completed. He has took it back to where it was serviced and they can see the errors but are stumped to what is the cause. Now it could be that the misfires were always being logged the owner of the vehicle had not previously plugged in the diagnostics but does not explain the limp mode and having to baby it home. Cannot really feel the misfire if I am honest maybe a very slight stumble. Anyone had anything similar? Service carried out was not spark plugs so assume coils not disturbed was listed as major with drive belt fluid and oils. Is there anything in the service that would require stripping down and disturbance of crank sensor or such.
911 2011 model Carrera 2 s-a misfire on all cylinders - Page 1 - 911/Carrera GT - PistonHeads UK
Add to repair workspace
Discussion summary
YOUR RESEARCH911 2011 model Carrera 2 s-a misfire on all cylinders - Page 1 - 911/Carrera GT - PistonHeads UK
1 matching discussions were examined; no attributable action/outcome evidence was detected. No consensus or repair conclusion is claimed.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Read captured repliesInsufficient extracted evidence does not mean there is no answer in the original discussions.
1 matching discussions · 6 captured posts examined · 1 partial discussions
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.
6 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
- PistonHeads: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T150451Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Thanks so much wonder how we get access to this TSB? Seems odd how it would be so long after the production run. Think firstly we need to establish what is the logic behind a misfire is it missing crank teeth would a knock retardation event be classed as mis-fire. Granted the code reader so far connected was an ICarSoft basic unit. Sounds to me like need someone to get datalogging and see what events happen when ECU calls a misfire.
Unless its related, this seems too much of a coincidence http://www.911uk.com/viewtopic.php?t=150161 Edited by guyvert1 on Wednesday 8th June 16:16
Seems like there is quite a bit of evidence on early models of having issue with drive belt changes. Not found so far anything for this later model. However seems very much like could be on track
What's the battery voltage reading?
Hi through the OBD II reader was reading 14.54 from memory. Don't think think this basic obd reader has a logging function to see if there are any momentary dips
This is a source reference. Confirm exact model applicability in the original material.