8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHHow to test trunk solenoid?
Leading reported evidence
Replace previously
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
It may be that the solenoid was replaced previously with one for a Boxster.
Leading evidence: 'Replace previously' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace micro switch too' (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.
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
I'm not sure about replacing the microswitch - it appears to function properly - and seems to just be a normally open switch.
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
It might be easier just to replace the solenoid (I know it was swapped out before).
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
Since it was installed by a third party and should have a 2-year warranty, it can probably get replaced under warranty.
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.
8 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: 20261026T124918Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
In my continuing quest of figuring out my
alarm double beep issue
, I'm trying to determine whether my trunk release solenoid is acting up. Does anyone know what the correct resistance should be across its pins? I'm getting about 4.7 Ohms.
A replacement solenoid looks to be $70 from Pelican Parts. It might be easier just to replace the solenoid (I know it was swapped out before). You seem to be capable of the installation. The problem could be the latch which the solenoid replacement won't fix unless you get lucky on the reinstall. Ruling out the solenoid would simplify the diagnostic fishbone diagram.
Thanks ditto. I'm struggling a little with the part number. What's currently installed is 996-624-117-01 dated 2-Nov-01. According to the
Porsche parts manual
, it should be 996-511-127-00, and this matches what I see on
Pelican
when I search for "hood lock actuator" with my car info in the system. However, when I search for this part number on Sunset, it comes up with "
release cable
" and that looks rather like the manual linkage from a 996.1.
Also, I've verified the invoice for the replacement and it was actually the latch that was replaced and not the solenoid. It may be that the solenoid was replaced previously with one for a Boxster. Not sure if this would make a difference to be honest, but what we do know is that the solenoid is 15-1/2 years old from the date printed on it.
4.7 ohms doesn't sound bad but you never know. It should be a fairly low number. If it was 0 you would know it's shorted and if it was infinite you would know there's an open.
Regardless, for the low cost it's worth replacing at this point. Do you plan on replacing the micro switch too?
I picked up the new part. Interestingly, while the box has the 996 part number, the part itself has a 997 part number. It was sealed, so I assume that it is the correct part.
I'm not sure about replacing the microswitch - it appears to function properly - and seems to just be a normally open switch. Since it was installed by a third party and should have a 2-year warranty, it can probably get replaced under warranty.