11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHOBD II code 1394 - coil replacement?
Leading reported evidence
Check code again playing
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 · Original poster
I checked the code again playing when playing around with the scanner and it's actually 1341 (I think I have 1394 stuck in my head from my PC/camcorder interface).
Leading evidence: 'Check code again playing' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check code again playing' (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 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
Others have used some other combos but this is a wobble socket on extension that is just the right size to work in a tight area of the 996 engine.
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
With that tool you can replace all six in 30 minutes....
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.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Check code again playing
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
I checked the code again playing when playing around with the scanner and it's actually 1341 (I think I have 1394 stuck in my head from my PC/camcorder interface).
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: 20261026T213932Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Ok. Short and sweet.
2000 911/2, 41K miles, 6sp. Check engine light comes on so I buy a Actron scanner and get the code.
1394 Engine misfire.
I read through Rennlist and determine coils are a common issue.
At $45 each, I wouldn't mind doing all six.
Now the question. Can I do this in my driveway?
Thanks.
Dale
Sure, it's easier than doing your plugs although I'd suggest doing them while you're at it too...The key to the process is having a very small ratchet with a 5mm hex tip. With that tool you can replace all six in 30 minutes....
By your reply I would summize that you are referring to a
1/4" drive ratchet with a 5mm hex allen drive bit?
And I further assume that this is to remove the bolt that holds these suckers in place?
Thanks,
Dale
Yes, you are correct in your assumptions, but the key is not to use the normal size 1/4" ratchet. The space is too tight. You want one with a handle that's only a few inches long at most and preferably very low profile at the socket. I can't find a good link to one but I purchased one at Sears and also found them at Advance Auto and Lowes.
I'd replace the plugs too, sometimes a bad plug will damage the coil. If you monitor the codes while you drive you might pick up a "pending" P030x misfire code, which tells you which cylinder is missing. Look for a code before you turn the car off, immediately after you notice the engine missing. If you drive a while without the engine missing P030x codes heal themselves and disappear.
The shop manual recommends Snap-On S9706 Spark Plug Socket and Snap-On FXW4 Extension.
I bought them and was glad I did. I have 40 years of tools but did not have a combination that would have worked. Others have used some other combos but this is a wobble socket on extension that is just the right size to work in a tight area of the 996 engine.
Ok. I have too many numbers in my brain. I checked the code again playing when playing around with the scanner and it's actually 1341 (I think I have 1394 stuck in my head from my PC/camcorder interface). It has the same description on my scanner but are there more subtle differences between these codes?
Thanks.
From 996TT manual
P1341
174 Camshaft Adjustment, Bank 1 � Signal Implausible
Diagnosis conditions
� Time elapsed after start-up greater than 5 seconds
� Engine temperature greater than -10 �C
� Engine speed between 680 rpm and 6.760 rpm
� No fault in camshaft adjustment output stage
� Reference mark OK
� No fault in camshaft position sensors
� No fault in engine temperature
Possible fault cause:
NOTE!: Camshaft does not reach early or late position OR Solenoid hydraulic valve is triggered, camshaft does not switch into early position OR Solenoid hydraulic valve is not triggered, camshaft does not switchninto late position
♦ Dirt in system
♦ Solenoid hydraulic valve mechanically blocked
Affected terminals
Diagnosis/Troubleshooting
Note!
Work instruction Display OK If not OK
1 Check solenoid hydraulic
valve camshaft adjustment
♦ Remove connector on solenoid
hydraulic valve
♦ Connect special tool 9675 to
the solenoid hydraulic valve and
to a power supply.
♦ Connect oscilloscope or engine
tester to the special tool 9675
♦ Set 12 V
♦ See Figure 1.
♦ Set switch on special tool 9675
to 1
See Figure 2
Step 2
Replace solenoid
hydraulic valve
→End
