5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHBahntech Q?
Leading reported evidence
Check $8000, i'll be sure
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
If you would just send me a cashiers check for $8000, I'll be sure to cut you in on the profit.
Leading evidence: 'Check $8000, i'll be sure' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check $8000, i'll be sure' (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.
Suggestion
On the "top up" operation I deliberately had the timing set 2 seconds beyond my timed manual results.
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
There goes using "one-mississippi, two-mississippi, ..."
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: 20261026T212127Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi gang,
I was out on the net last night doing some shopping and I finally bought the "one-touch cab top up/down" Bahntech mod. I received an email question this AM asking me to time the up and down operation on my Cab since they apparently vary, at least for the MY2000.
Has anyone else had to do this for their Bahntech order (I found the website by doing a simple "Bahntech" search here on rennlist)?
I'm curious, is this just my MY or every 996 Cab?
Thanks.
I think this is the reason some people have reported that the Bahntech unit burns out their CAB switch frequently.......
since it is programmed on a timer then it can engage the switch longer than it needs to be engaged thus resulting in overuse leading to premature switch burnout. This is one of the reasons I passed on this.
Whooa! Guess I'd better time my cab top up/down pretty accurately! There goes using "one-mississippi, two-mississippi, ..."
Hey LVDell, I'm almost done with my fold-able glass research. If you would just send me a cashiers check for $8000, I'll be sure to cut you in on the profit. ;-)
Cheers.
The Bahntech one-touch has worked flawlessly for me for the last year. I don't hesitate for one second to recommend it. (No connection with the company, just a happy customer)
LVDell: about your comment that the Bahntech switch burns out their cab switch... This seems very odd to me. The timer works the same as if you're manually holding the switch. If you hold the switch an extra second or two (and who doesn't, to insure that the top is actually at it's final destination) , does that burn out your controller? I doubt that the Bahntech switch could be the cause of the controller failing in those instances. Sounds more like a controller that was destined to fail in the first place.
If anything, having the Bahntech switch reduces the time you apply finger pressure to the switch so it should last longer!
I was very happy when Bahntech allowed me to customize the timing on the unit. This way, on "top down" operation, the top retracts and the movement stops exactly at the moment between the rear deck closing and the windows starting their upward movement. On the "top up" operation I deliberately had the timing set 2 seconds beyond my timed manual results. This way the windows are sure to get all the way up. (There is some minor variability to the operation speed of the cab/window motors, due I think to the current alternator voltage which wiggles with the engine speed).
Overall, this is "no brainer" upgrade that takes 10 minutes DIY.
Here's a link:
https://rennlist.com/forums/showthre...light=bahntech
This is a source reference. Confirm exact model applicability in the original material.
