15 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHhorn beeps once when i lock it?
Reported or suspected cause
security
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: 'security' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'security' (1 discussions; 1 report identifying it and 0 suggest it). 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
This could be a faulty switch, or more likely an actual "aperture" is open.
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
Probably the WD-40 either freed up or washed out the dirt.
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.
15 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261027T102108Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
An aperture microswitch has triggered.
This could be a faulty switch, or more likely an actual "aperture" is open.
These are doors, roof, bonnet lid, engine lid AND the armrest cubby hole lid and glove box.
99% of the time it is one of the last two.
:thumb:
if i'm correct and i think i am then it means your alarm isn't setting, it goes off as a warning to tell you that for some reason the car isnt secure so it wont set.
last time it happened to me was when i had MOT done and the bonnet was not closed fully. Also happens if a door slightly open or roof not fully closed.
Craig
My cab has always done it and I've never been able to track down which microswitch is causing it. But the alarm is set , although I am sure what GT4 says is correct in general. To be honest its kept in the garage and so its never overly bothered me.
I was being generous to the glove box crew.
As a 996.1 owner I do not possess such a thing, but then I don't have driving gloves and the armrest cubby is just the right size for my tin of driving sweets anyway.
Good point.
mathamb has an after-market Becker single DIN Nav/Radio/CD unit.
As Richard says, if the contact is grounded (ie touching the cage) the system thinks the headunit has been stolen. The OEM units have a tag that pushes the contact open when the headunit is fully home.
You need to find the brown/blue wire to the radio cage, cut and insulate (tape etc) so the alarm always thinks the radio contact is open circuit.
Richard H wrote
Have you got an aftermarket radio? Sounds like the alarm contact hasn't been insulated.
Yes I have a Becker Traffic Pro which is almost exactly the same as the oem unit but with sat nav (and very good it is too... PCM1 eat your heart out!) Where would I find the alarm contact and how best to insulate it.
Thanks
I'll work out how to do the quote thing later.
[/quote]
All you need to do on the TrafficPro is put some tape on the left hand side of the unit. This stops the alarm contact from touching the side of the case. (Bottom photo). The standard radio with insulating patch is shown in the top photo.
Or you can do what GT4 says and remove the brown/blue wire going to the left hand side of the cage.
The same thing happened to me.If I press the key fob the car would beep once and if I pressed it again it would lock normally.
I checked everything was closed but still beeped ones so I put up with it for about 3 months.
For some reason I decided to spray WD40 on the lock in the actual door.
Its never happened again.
