17 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCam sensor and cam diviasion problems
Leading reported evidence
Check already
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 already' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'variocam u would still get a reading' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check already' (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 · Original poster
I have on bank 2 a camshaft position code P 1397 changed the sensor with a Bosch , checked wiring to DME it�s fine still code comes back.
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 have on bank 2 a camshaft position code P 1397 changed the sensor with a Bosch , checked wiring to DME it�s fine still code comes back.
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 think only the early 5.2 dme used the same wires.
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
Even if it was the variocam u would still get a reading.
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 po of my donor car must have had a ton of issues with the 02 syatem and i had to replace all the pins because the teath were all spred from a meter probe and caused intermitant signals.
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.
17 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: 20261027T005001Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I have a 2001 996.When I connect my Durametric scanner I can not read the camshaft diviation or cam angle, it just shows 0 on bank2 and on bank1 it shows everything. I have on bank 2 a camshaft position code P 1397 changed the sensor with a Bosch , checked wiring to DME it�s fine still code comes back. Bank 1 everything shows fine, Car runs great has good power and smooth. My question is: How come i can not read anything on my scanner for Bank 2 and why is the P1397 code still coming back on Bank 2.
Is your car a north america spec? Cause the ROW cars do not read bank 2. If its a na car i would make an assumtion that u have a wiring issue between the dme and the bank 2 sensor. U will need to check for continuety for all the wires that go to that sensor. Mice really like the soy based coating on our wiring?
Here is the wring diagram, the cam sensor has three wires, a power,a ground, and a signal back to pin 20 ( or 19) of the DME....
Test these wires for continuity...
But is the signal reporting to the dme? If not its wiring or even a bad pin in the dme plug. The po of my donor car must have had a ton of issues with the 02 syatem and i had to replace all the pins because the teath were all spred from a meter probe and caused intermitant signals.
I very technical read here. U may need to back pin the sensor and check the signal with an oscilascope
https://rennlist.com/forums/996-foru...e-p1397-2.html
Give us some back ground in the fault. Did it appear out of thin air? Has any work been done to the car lately, miles on motor? The more info the better.
Hi, thanks for your reply. According to the Porsche wiring bank 1 and 2 cam sensors are on the same wire going in to the DME signal 5volts and ground only Battery voltage is on a different pin. If it wouldn’t be a DME issue or wiring cam 1 wouldn’t work either I think. I have the feeling it’s mechanical with the variou cam adjuster maybe stuck or broken but I have no codes for it that is my dilemma that is why I am looking for some feed back if somebody had the same problem before i take the engine out and then find out it’s still a electrical problem.
I have no history of the car i just bought it and the guy told me everything is a1 with the car, nice guy.
Also can somebody tell me where to buy good used parts like ( cam adjuster and so on ) i am also new to this group and any help is very much appreciated.
U should verify what computer u have. I think only the early 5.2 dme used the same wires. Per that thread the signal is sent on 2 different "phases" if it is a single wire set up. Even if it was the variocam u would still get a reading. I would still try to verify u r getting signal at the dme before spending $1000s on parts and labor.
I have 1 used and 1, 300 mile variocam actualtor, (chains, pads and both selinoids also with 300miles) for a 3.4l that i would let go at a pretty good price if u need them. I have to check which side is the newish one but i think its bank 1.
Also to be clear its a new to u car and this problem was undisclosed or u have had it for a while and now u have the issue? Sorry for the basic question but it helps with how my mind problem solves.
Thanks for the advice about the DME. I am pretty sure I have a 7.2 DME. I have to see if my wiring diagram is for a 7.2. To buy a variocam i am still far away from it but nice to know you have one for sale. Thanks for now.
By the way where are you located if you don’t mind asking.
You have DME 7.2 on a 2001 model.
On the 7.2 each sensor has separate wires all the way to the DME for the SIGNAL wire
The POWER and GROUND wires are shared/spliced
Use the appropriate diagram that I sent you for DME 7.2
