5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHTiptronic (722.6) Shifting Out of Sync on my 996
Leading reported evidence
Reset tiptronic adaptations through piwis and everything was fine
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
Last time it did that, I reset the tiptronic adaptations through PIWIS and everything was fine for a week.
Leading evidence: 'Reset tiptronic adaptations through piwis and everything was fine' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check actual values in piwis' (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
These two sensors measure the rotational speeds of different internal shafts and are used by the TCU to determine the actual gear ratio.
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
Quick update after checking the actual values in PIWIS:
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
Any ideas on what to check first would be greatly appreciated.
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
The engine gets heavier as if the gearbox has already changed gear, and after a moment the display finally updates�but by then it seems to have already shifted again to 4th, causing the whole car to shake.
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
The engine gets heavier as if the gearbox has already changed gear, and after a moment the display finally updates�but by then it seems to have already shifted again to 4th, causing the whole car to shake.
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
If N2 and N3 don’t match the expected values for a given gear, the TCU thinks the gear change hasn’t completed, which can cause exactly what I’m experiencing:
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.
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: 20261027T011819Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi everyone,I�m dealing with a strange issue on my 996 equipped with the Mercedes 722.6 Tiptronic and I�d appreciate some feedback.
About 3,000 km ago I had a full transmission service done (ATF + filter), following the correct procedure and temperatures. Everything worked perfectly until recently. Now it feels like the gearbox is out of sync with the engine. For example, in 2nd gear it feels like it shifts into 3rd, but the cluster still shows 2nd. The engine gets heavier as if the gearbox has already changed gear, and after a moment the display finally updates�but by then it seems to have already shifted again to 4th, causing the whole car to shake.
Last time it did that, I reset the tiptronic adaptations through PIWIS and everything was fine for a week. Now it is the second time this happened... If I drive it manually through the steering wheel, all is fine.
Has anyone experienced similar behavior with the 722.6 in a 996? Any ideas on what to check first would be greatly appreciated.
Thanks in advance.
George
It sounds like you are feeling the "lock-up Convertor" lock,, it literally feels like a gear shift ...( and is normal )
If you have PIWIS you can watch or Log the shifts and Lock-up to verify , but hundreds of Tip Owners have had the same question ...
To me the TIP in Auto always shifts to a higher gear and lock-up too soon at too low an RPM and is why I drive 100% of the time in Manuel Mode fo the last 17 years...
Quick update after checking the actual values in PIWIS:
I have two strange behaviors:
Firstly, I monitored the internal speed sensors of the tiptronic. The “Transmission RPM Wheel 2” and “Transmission RPM Wheel 3” correspond to the N2 and N3 speed sensors inside the gearbox. These two sensors measure the rotational speeds of different internal shafts and are used by the TCU to determine the actual gear ratio.
If N2 and N3 don’t match the expected values for a given gear, the TCU thinks the gear change hasn’t completed, which can cause exactly what I’m experiencing:
– delayed gear indication on the cluster
– the engine feeling like it shifted even though the display hasn’t updated
– sudden jump into the next gear
– vibration/shudder when the box “catches up”
This behavior strongly points to an issue with one of the internal speed sensors (N2 or N3) rather than a hydraulic or mechanical failure. On the other hand, can a 0 value in Wheel 3 be correct? See the image below:
Secondly, at specific random times and while driving, it seems that PIWIS cannot connect to the gearbox and I get these values:
Does it point to an electrical problem. And how can it be fixed just by resetting adaptations? Because I reset them once more, and the car is now fine again...
