4 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHConvertible top problem
Reported or suspected cause
gone
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.
Leading evidence: 'gone' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'gone' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Install remotetop' (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
I have a SmartTop and just recently installed the RemoteTop.
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
I just squeezed it an moved it around a little, and then tested the top, and it worked!
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.
4 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 · 1 adjusted by outcome qualification.
2 acknowledgements have no verified action link; they do not establish a repair result.
The car is a 99 Cab C4.
A bit of history first...
I have a SmartTop and just recently installed the RemoteTop.
I just got the car back from a wash and detailing, and now the top refuses to latch close.
When I go to close it, it goes through the regular motions (windows down, top coming up), but when it gets to the final step where the center latch arm locks at the top the windshield, the system won't let the latch stay in the closed position.
The latch goes into the locked position, then comes out, then it tries again, and then comes out again. It tries 3 times before leaving the latch out halfway.
The top light stays solid, no flashing or anything. Is there a sensor in there that co-incidentally went dead, or something else could be up?
OR did water just get somewhere it wasn't supposed to and I just have to let things dry out?
Any help would be appreciated.
thanks,
Amir
Seems to be similar to this thread:
http://www.renntech.org/forums/index...hl=convertible
For future searchers:
hook cycling and windows not going up
Convertible cab top
thanks,
Amir
Yeah...figured it out last night...the link helped....
The latch cover looked fine. There was a crack along the top, but nothing that would stop it from working.
Then I thought maybe the little switch sensor in the base on the windshield may not be getting pressed properly.
So to test, when the latch went into the closed position, I took a screwdriver and pushed the switch arm on the base manually to see if that was the problem. It wasn't.
Then I thought maybe some water or something had gotten into the windshield base, so I pulled that out. 2 plastic covers, and 2 screws all it took.
Everything looked fine, but then I noticed that the 2-wire harness going to the switch was squished and one of the wires had lost some insulation. I just squeezed it an moved it around a little, and then tested the top, and it worked!
Now I'm not sure if it's because the wire was grounding or the wire has a broken connection. I couldn't think of a quick way to bypass that piece of wire without cutting splicing (etc). I just put some electric tape on it, and then repositioned it so it didn't get squished again when screwing the windshield cab-top base.
The problem is gone for now. I'll see how it goes for a little bit, if the problem comes back, then I'll do a more permanent fix of the wire.
Very weird....I think the previous owner (or dealer) must have pulled it off at some point, and then maybe didn't place the wires correctly when screwing it back in.
thanks,
Amir
This is a source reference. Confirm exact model applicability in the original material.
