9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHStrange Tranny Behavior
Reported or suspected cause
last run group of the day
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
Luckily, it was the last run group of the day, so I started home without those two gears.
Leading evidence: 'last run group of the day' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'last run group of the day' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check conections and cable' (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 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 · Original poster
So whether it was due to a linkage adjustment (I hope), or to the same coming and going behavior it was showing before, I'm not sure.
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
Check conections and cable for straightness, etc at both the shifte as well as right side of tranny.
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
However, I just now went out to run a couple of errands, during the course of which the two same gears decided to take a long lunch, or otherwise make themselves scarce.
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
Luckily, it was the last run group of the day, so I started home without those two gears.
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
However, I just now went out to run a couple of errands, during the course of which the two same gears decided to take a long lunch, or otherwise make themselves scarce.
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.
1 acknowledgements have no verified action link; they do not establish a repair result.
At the end of an otherwise excellent weekend at Mid-Ohio in my C2 cab, I missed a shift at the end of the back straight, and for one microsecond I started to go into 1st instead of 3rd. (ouch!) That was apparently enough to cause some transmission funkiness, which showed up as first gear and reverse going AWOL.
Luckily, it was the last run group of the day, so I started home without those two gears. (that's an interesting experience, particularly driving on back roads) Anyhow, about 1.5 hours into my trip home, the two gears came back, and the car has been fine since then. However, I just now went out to run a couple of errands, during the course of which the two same gears decided to take a long lunch, or otherwise make themselves scarce.
So, my question is, what is going on? What do these two gears have in common? Is there a common linkage? Or something else inside the tranny?
I have a short-shift kit I was getting ready to install, and I'm thinking that if it's just a linkage adjustment problem, maybe I could take care of it when I do the installation.
Anyone have any other thoughts or suggestions?
=Carlos=
Just bumping this up, in case someone missed it who might have some suggestions.
I was hoping that maybe after the car cooled overnight, the missing gears would return, but no luck. As it is now, I'll have to push it backwards out of the garage, and start off in second to get to my wrench.
Or I may dig into it myself -- that's why I'm searching for clues as to what could be wrong.
Anyone got any ideas?
My guess would be shifter linkage may have gotten screwed up slightly with the pressure you applied. Check conections and cable for straightness, etc at both the shifte as well as right side of tranny.
Thanks for all the comments. I am 75% of the way through the installation of the B&M short shift kit, enough so that I could drive the car around the block, and the problem seems to have gone away. So whether it was due to a linkage adjustment (I hope), or to the same coming and going behavior it was showing before, I'm not sure. But I'm cautiously optimistic this has fixed it. And if it is a cable linkage adjustment problem, I now know how to do that.
On the plus side, the short-shifter performance seems wonderful -- like everyone says, should have done it a long time ago!
