9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHP1531 when HOT
Leading reported evidence
Check connections and cables) and go
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
I guess I will start with the easy stuff (checking connections and cables) and go from there.
Leading evidence: 'Check connections and cables) and go' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check connections and cables) and go' (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 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 · Original poster
It seems that visually inspecting the cam sensor and actuator wiring to start makes sense.
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
I have been doing some searching for good threads on this but could use some help on what to do next.
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.
9 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: 20261026T133652Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
So my '99 cab had its first taste of LA stop and go traffic over the weekend. Unfortunately the heat seemed to get to it and the check engine light came on. I guess it leads a spoiled life here in SF. Luckily I had my trusty OBDII reader with me and read out a P1531. The next day the check engine light was still on. I then proceeded to drive 300 miles and then filled up the gas tank (with cheap gas btw) and then the check engine light went off.
I have been doing some searching for good threads on this but could use some help on what to do next. It seems that visually inspecting the cam sensor and actuator wiring to start makes sense.
BTW - speaking of HOT - LA girls are amazing.
Have you checked Imo's thread?
https://rennlist.com/forums/996-foru...r-voltage.html
He had p1539 (bank2) and yours is bank1, similar code though. Not saying you have the exact problem but that shows it really takes quite a bit of exhaustive diagnostic to pinpoint the actual failure. Being intermittent will make diagnostic very difficult since even if the component passes the test, you cannot eliminate it. Maybe wait for the CEL to be ON more frequently?
Do you have Durametric?
Thanks Ahsai, I did find that thread. Unfortunately I don't have a Durametric. I guess I will start with the easy stuff (checking connections and cables) and go from there.
For months I've been chasing (with much help from others) misfiring problems and various related codes on my '02. In my experience the fault codes have been pretty much right on although we have gone on a number of scenic detours thinking we were smarter than the ECU. The ECU samples all its inputs over time and it knows when signals are correct and when they don't make sense.
It appears that the root causes of my problems have in fact been corroded ECU connections at the X59 connector pair in the engine compartment. Symptoms showed when the engine compartment gets hot. Even knowing this it is not easy to diagnose and repair because corrosion can reduce contact reliability even without visible signs.
IMHO the likely causes with an older car (10 years+) are going to be flaky connectors, sensor failures, or actuator failures. The ECU has its own connectors, through a wiring harness to the X59 connector, through the engine wiring harness to another connector, then finally into the sensor/actuator. Investigating each one of those for any wear or corrosion is worth the time.
Does anyone happen to know how the DME knows if the Variocam (via the solenoid) has successfully advanced the Cam or not (and throws a code) ? What sensors does it use to do this?
The crankshaft drives the exhaust cam (the lower one in the photo) via the double chain
http://p-car.com/996/diy/engine/DSC_2901.JPG
The exhaust cam then drives the intake cam via a smaller chain whose tension is controlled by the variocam actuator. Diff tension creates diff timing between the two cams. The cam sensor picks up the cam position generated by the reluctor on the intake cam.
You can actually see the reluctor ring and the cam sensor clearly in this photo
http://www.pelicanparts.com/techarti...mall/Pic07.jpg
This is a source reference. Confirm exact model applicability in the original material.
