11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFault code P0021 timing is off?
Reported or suspected cause
but it wasnt huge....i seriously cant recall the fix
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
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 report identifying 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.
Reported cause
cant recall right now what the culprit was but it wasnt HUGE....I seriously cant recall the fix.
Leading evidence: 'but it wasnt huge....i seriously cant recall the fix' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'but it wasnt huge....i seriously cant recall the fix' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Adjust camshafts' (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.
Check sources and all i have is what 911slow posted
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.
Performed · outcome unconfirmed
I checked my sources and all I have is what 911Slow posted.
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.
Performed · outcome unconfirmed · Original poster
* One set of chain tensioners have been replaced at about 109.000 km in April 2011
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.
Performed · outcome unconfirmed · Original poster
* The AOS was replaced at about 105.500 km, also by Albert Motorsport
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.
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.
11 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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T192637Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hello!
I've had my C4S for about 4 weeks and I'm starting to get a pretty accurate picture of the car and considering that I paid about US $10k under market price for a C4S in Norway, its not so bad :-).
However, I do have this one thing I'm trying to figure out and that its the P0021 fault. Please se attached pictures from Durametrics on my car.
Been reading up on all I've been able to find on this, but the more info and input I can get the better I think. Some information:
* There is no CEL. There was one and I took the car to Porsche locally, they found this error and a lambda error. Cleared the codes and the lambda one has not returned.
* The car runs fine as far as I can tell
* As far as I know, it's not running especially rough either (actually my voltage regulator is a bit wonkey so its kind of rough when the voltage drops up and down but it "feels" electrical and not mechanical, but who knows)
DME 7.8
P0021
Position of Camshaft in Relation to Crankshaft, Bank 2
– Below Limit
Diagnosis conditions
• Idle speed
• Reference mark recognized
• Engine speed between 600 rpm and 1200 rpm.
• Engine temperature greater than 40 �C
• No fault in camshaft position sensors
• Reference mark OK
• No fault in camshaft adjustment
• No fault in engine temperature
• No fault in camshaft adjustment output stage
Possible fault cause
♦ Allocation of camshaft to inlet camshaft incorrect
Affected terminals
-
Diagnosis/Troubleshooting
This fault is stored if the engine was disassembled and the allocation of the camshaft to the inlet camshaft was
incorrectly set.
Work instruction Display OK If not OK
1 Set camshafts ♦ To
adjust the camshafts
, please
refer to the 911 Turbo (996) or
911 Carrera (996)
I have seen that before.
cant recall right now what the culprit was but it wasnt HUGE....I seriously cant recall the fix. i would not drive it though and get it fixed asap - if I remember i will post
Cheers, please do
.
As for the fault, with timing it's sort of a "hit and miss" (Quite litterally, do mind) thing. The original P0021 came, according to Porsche, at about 105.000 km. The car has now done ~115.000 km. If the timing has been messed up to the point where the valves has kissed the pistons it's been doing it for a very long time (relatively, for an error like this anyway).
That is the only reason I'm not all that worried about driving it still. Porsche was not all that worried about it either, but then again - they could possibly see a future new engine in it for them ;-).
It's a 3.6 X51, yes.
At a friend in the car just now, hooked up the laptop and at least the deviation stays more or less the same all the time. Do note "more or less", it's not jittery or anything indicating IMS failure, but there's definately not the 100% same value while going through the revs.
I'm a bit reluctant to define it as idling issues, but as soon as the secondary air thingamajingey has done its thing and it lowers down towards 800 rpm its *not* rock solid at 800.
I checked my sources and all I have is what 911Slow posted. No test/diagnostics steps.
Based on the absence of any test/diagnostics steps and the absence of any other symptoms, I'd suggest -- if you want to go to the trouble -- is to find the related electrical wiring harness connectors for the actuator solenoid and sensors and carefully disconnect them then reconnect them. The fault could be do to a marginal electrical contact.
Also, almost always when something inexplicable like this pops up related to the valve timing especially with a car that is unknown to the owner I like to as about the oil. I assume the oil level is correct and the oil is of the proper type/grade and doesn't have too many miles on it?
Sincerely,
Macster.
Sometimes we tend to over-think things.
This could be a hall sender or it's wiring going wonky, as Macster has pointed out.
Or the "computer" is right and it could be the timing is off some how, perhaps the ims tube sprocket has slipped over time on bank 2 (according to Jake I've read this can happen), or it skipped a tooth somehow, or for some inexplicable reason the camshafts were not allocated properly during removal and re-installation.
You did mention idle not normal right? Could indicate timing is not 100%, but the DME is "good enough" to compensate for a serious discrepancy (-12.7 degrees on bank 2).
Anyhow, have it checked out. A lot "less expensive" to address now rather than later when you have misfires and/or piston/valve contact.
Also I hate to bring up oil as well to avoid oil wars, but agree with Macster's suggestion.
Thank you all for the feedback and suggestions.
I see that I have managed to forget to mention a few quite possibly important facts here.
* The car has now done ~115.000 km
* The engine was rebuilt at Albert Motorsport in Germany at about 104.000 km (new block, cylinders and pistons if I don't remember it wrong)
* The AOS was replaced at about 105.500 km, also by Albert Motorsport
* One set of chain tensioners have been replaced at about 109.000 km in April 2011
As for oil; the car is running on 5w40 and should have been replaced when the tensioners where replaced about 6000 km ago so the oil
should
be pretty much ok. It's currently sitting at the "max" level, ie one "bubble" away from max in the cluster which pretty much correlates with the dipstick as well.
Considering the work that has been done to the engine over the last ~11.000 km, having the timing being wrong is technically possible. The strange thing is though; when I had the car at Porsche locally before I got my durametric, they got this same P0021 and they claimed it had been there since about 105.000 km.
This is for all intents and purposes a bit strange as the car has been diagnosed by Albert Motorsport since then (last time was at 109k as mentioned above), but what do I know.
I'd love to check the electrical connections for the solenoid, I'll try to look into it and figure out where it is.
This is a source reference. Confirm exact model applicability in the original material.