10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCan you adjust the senesitivity of.....
Leading reported evidence
Adjust sensitivity of alarm system
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.
Leading evidence: 'Adjust sensitivity of alarm system' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'dropping the trunk lid' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Adjust sensitivity of alarm system' (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
While this is true, and dropping it may be exacerbating whatever is going on, I'm not sure I believe that the root cause is dropping the trunk lid...
Outcome qualification: Negation, uncertainty or missing explicit repair resolution overrides the raw extraction signal.
either the microswitch is gummed up or flaky
Suggestion or failed attempt
No successful repair reported for this finding.
0
Identified cause
1
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 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
I suspect either the microswitch is gummed up or flaky.
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
Dropping it will muck up the switch and probably the latch as well.
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
You finish loading the car and drop the trunk lid; its impact is sufficient to cause the sticky microswitch to change state and the alarm goes off.
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.
10 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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T053112Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Can you adjust sensitivity of alarm system?
When I drop my frunk cover from about 6 inches for initial closing the alarm goes off, BeepBeep.....
It never used to do that.
RBC
AFAIK the alarm is primarily an intrusion alarm - open any of the monitored points (doors, trunk, engine compartment, etc) when armed and the alarm will sound. There is also an interior motion detector...but I don't think there is any exterior motion detector, in other words, shake the car and nothing goes off so I'm not sure what's causing your alarm to sound when you close the trunk. Also, I'm not aware of any sensitivity adjustments other than deactivating the interior motion detector.
I'm not getting this. So you arm the car and then close the trunk lid and then the horn beeps? Or do you close the trunk lid (car unarmed) and the horn beeps? And no, there is no sensitivity adjustment. It is a simple matter of armed/not armed, or open/closed. There is a microswitch on the hood latch that detects if the trunk lid is open or closed. Possibly that is faulty.
Of course, now I can't reproduce it.
It would happen when returning to car from shopping. I would use key button to open frunk before opening car doors. Then dropping frunk last 6 inches would get alarm. I thought opening frunk would turn off alarm. When I try opening frunk now the interior alarm light goes off.
RBC
I suspect either the microswitch is gummed up or flaky. See Part No. 9 here
http://www.autoatlanta.com/porsche-p...section=803-00
Would not hurt to spray some WD-40 in there.
_if_ it's true that your alarm does not disarm when you open the front trunk, AND it's true that your alarm detects vibration, dropping the trunk lid when it's not meant to be dropped is believable as a cause for the alarm to sound.
I reviewed the alarm section of Essential Companion, and there's nothing in there about vibration detection...but it does explain some of the situations where the alarm system will re-arm after some amount of time has elapsed.
Here's one WAG/scenario/theory:
You're disarming the system by pressing the the front trunk button - but the front trunk microswitch is sticky, and sometimes the switch is not correctly detecting the change in state. Since the car has not detected the front trunk being opened, the central locking system rearms the system after 15 seconds. You finish loading the car and drop the trunk lid; its impact is sufficient to cause the sticky microswitch to change state and the alarm goes off.
This is just one possible theory, but if one or more switches aren't working right and the system is rearming unexpectedly, that could explain why the alarm is sounding when it shouldn't be.
While this is true, and dropping it may be exacerbating whatever is going on, I'm not sure I believe that the root cause is dropping the trunk lid...
Not all country setups use the same alarm sequence but for the US (2001 anyway--99 has no trunk release button):
There is no vibration sensor. There is an interior IR motion sensor.
Using the FOB to release the trunk will disarm the alarm and open the trunk. When you close the trunk, the alarm will start the same sequence as unlocking the door. That sequence turns off the alarm and waits a period of time, I believe somewhere around 30 seconds, for you to open either the driver's or passenger's door. If you do neither, the car re-locks and the alarm rearms.
Also don't drop frunk, the struts are supposed to allow it to gently close to around 6 inches. Close it by hand and press to right and left of hood emblem to latch. Dropping it will muck up the switch and probably the latch as well.
It sounds like you are opening the frunk and the alarm is working correctly. Then you slam the frunk but it does not latch. The car waits 30 seconds or so and rearms. The frunk is not properly closed so the beep-beep that signifies the car is armed but not properly locked (an open sensor--in the case the frunk).
Don't press on the badge. That will bend it like a potato chip and eventually cause the mounting studs to break free. Press the area between the badge and the front edge of the frunk lid above the latch.
schn3ll I like your theory the best about sticky switch.
I will try to find it and lube it, but not with WD 40.
I never slam the frunk, I bring it down to about 6 inches then usually drop it. Then I press on both sides of emblem.
Yes the shocks are probably worn and need to be replaced. Just low on my list.
thanks for all the replies.
RBC
This is a source reference. Confirm exact model applicability in the original material.
