5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH2001 996 C4 Cab Data Quest
Leading reported evidence
Use screen record
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
No one tool seems to give accurate and thorough results, thus a video was the only good way to capture all this data from different sources using screen record.
Leading evidence: 'Use screen record' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Use screen record' (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.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Use screen record
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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
No one tool seems to give accurate and thorough results, thus a video was the only good way to capture all this data from different sources using screen record.
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.
5 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261026T174436Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
It still has warts, but this is a video I made combining CAN, ODB, cell phone GPS, and Oscilloscope data. It shows the car going into limp mode (when all the signals flatline on the scope). The CAN window wasn't expanded to show all data, so some things are cut off like the signal that shows limp mode being flagged.
The Porsche tester's OBD data looks suspect, but maybe it's actually showing a problem? The RPM clearly is off by some factor. Also, maybe the transmission input sensor isn't making it up high enough to reliably detect the shaft rotation?
Data Details:
I've been trying for months to collect the right data to show why my transmission is going into limp mode, but it has proven most challenging. No one tool seems to give accurate and thorough results, thus a video was the only good way to capture all this data from different sources using screen record. Example, the wheel sensor speeds read fine on multiple ODBII scanners until the car hits 30 MPH. After that, I believe the ODB bus is too slow to keep up and it loses synch..
I tapped into the CAN bus for more data. It reliably gives me the wheel sensor info, braking, RPM, what gear is selected by the Tip, and limp mode. It has a value which indicates whether the gear shifting is stable or still in progress and that seems to track. Another gives some indication on the torque converter status, but I'm not sure I have the interpretation correct for that one. I have the raw CAN data captured in addition to the video, but it is tedious to look through.
I also tapped into most of the raw Tip signals with an oscilloscope: Transmission input speed sensor, MV1-3 solenoids valves, and EDS 1-4 regulator/valves. The MV1-3 solenoids are either on or off. On the video, if they're off, they're 12 V and on if they're zero to a few volts. The pressure regulators are pulse width-modulated. When not actuated, but not in limp mode, they seem to give a low-duty-cycle (low energy) pulse to each regulator. When the regulator is active, that jumps up closer to 50% duty cycle. It's easy to see that on the scope signals OR on the measurements below. When in limp mod
I couldn't get the transmission input speed from the CAN bus, so I captured that, the RPM, and the output speed on another scanner. The transmission input sensor raw signal seems to track with what I see on the scanner.
Observations:
The valve signals seem to track the "Valve Body Signals.png" file I attached. EDS4 is supposed to be used to engage the TC clutch, but I don't see it getting turned on strongly. According to the chart, it shouldn't engage at all until 3rd or higher. Even in park or neutral, it's getting a small duty cycle but that seems normal.
This video shows 3 failures:
1) In second gear starting from a stop - Note the input signal starts slowing until it stops while the engine is revving.
2) In second gear, but you can see 3rd slipping right before - Same thing on the input signal falling off
3) It seems to go into limp mode in terms of shutting off all the valves, but the CAN data doesn't show full limp mode - it does show some value which seems related so maybe it knows it will be going there soon..
I didn't trap 5th gear slipping and going into limp mode this time, but have seen it in the past. It acts the same. It's stable and in 5th, then the engine starts revving higher (slipping), then it goes into limp.
Watch these in HD:
YouTube Limp Issues Full video
YouTube Limp Issues Slo Mo 1
YouTube Limp Issues Slo Mo 2
YouTube Limp Issues Slo Mo 3
This is a source reference. Confirm exact model applicability in the original material.