fullymatted.
Back to search
Rennlist

Revolutions calling...

Add to repair workspace
Open repair workspace
Original source
2 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHRevolutions calling...

Reported or suspected cause

consistent

Reported cause

No successful repair reported for this finding.

1
Identified cause
0
Suspected cause
0
Reported fixes
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 report identifying 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.

Reported cause · Original poster

Although there were no air mass sensor faults it was suggested by my indy I change it as the problem was consistent with their previous experience with tip faults.

Revolutions calling...
Frequently discussed work

Check atf level

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

Did they check the ATF level to ensure it is filled to the proper level?

Revolutions calling...
Read full discussion summary

Leading evidence: 'consistent' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'consistent' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check atf level' (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.

Read captured replies

1 matching discussions · 2 captured posts examined · 0 partial discussions

Compare 1 other evidence results

Check atf level

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

Did they check the ATF level to ensure it is filled to the proper level?

Revolutions calling...
Frequently discussed actions (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Check atf level

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

Did they check the ATF level to ensure it is filled to the proper level?

Revolutions calling...
Reported and suspected causes (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

consistent

No successful repair reported for this finding.

1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that report identifying 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.

Reported cause · Original poster

Although there were no air mass sensor faults it was suggested by my indy I change it as the problem was consistent with their previous experience with tip faults.

Revolutions calling...
Coverage and how to read this overview

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.

2 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: 20261026T152433Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

My 98 C2 is throwing tiptronic clutch error codes, but diagnosed (reasonably) due to inconsistent torque through the rev range between 2500-3000. Although there were no air mass sensor faults it was suggested by my indy I change it as the problem was consistent with their previous experience with tip faults. So we changed it and....... it helped a bit (grrrr!) - better auto changes when warm and generally and hitting the 7,000 red line much more smoothly, so I think it was part of the problem - tiptronic button shift seems pretty much fine by the way. Stumped now - stuck with the same issue (but to a lesser extent) - you can feel the revs are all over the place between 2,500 -3,000 especially when the engine is cold/warming up- potter around below 2500 or toe it up above 3,000 and its sweet as a nut. Any ideas?

POST 2Original post

Did they check the ATF level to ensure it is filled to the proper level? Always a good starting point. But it sounds like a solenoid fault for the torque converter to me. Not uncommon and easy enough to fix for at a good transmission shop.

This is a source reference. Confirm exact model applicability in the original material.