4 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHStrange alarm beeps!
Reported or suspected cause
loose connection, or a faulty alarm control unit
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
If not, then I would suspect a loose connection, or a faulty alarm control unit.
Leading evidence: 'loose connection, or a faulty alarm control unit' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'loose connection, or a faulty alarm control unit' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check carefully)' (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
If it is single-beeps you are getting, then it probably won't have any codes stored, but is still worth checking, just in case.
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.
Porsche Club GB: 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: 20261027T013556Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi
Hopefully someone can help with this. This morning I was putting something in the front (bonnet open) and I heard 2 beeps from the alarm (similar to when you try and lock with a door etc open). I assumed it was because I had my keys in my hand and had accidentally pressed the button. I then shut the bonnet and started the car. A few seconds later the car beeped twice again. I stopped the car, turned off the engine, got out, opened and closed the bonnet, locked and unlocked the car (manually with the key and via the remote) and carried on. Then it did it again about a min later and 5 mins down the road it did it again. I arrived at the station about 5 mins later with no further beeps and on locking it at the station car park, nothing further.
It may well be going off all day, but I don't know!
A while ago when I had an issue with the drivers door lock not functioning correctly (not keeping the window dropped when the door was open), the alarm sometimes did a few beeps when driving (in a similar way to this).
Any thoughts, or previous experience of this?
Any help would be appreciated.
Cheers
Dazz
A double-beep indicates a fault in the central locking/alarm. It should have stored the fault codes in the control module, so you really need to get the codes read by someone. It is unusual to get beeps while driving though. What year is your car? It looks a later model from your avatar, but if it is pre-facelift it might be related to the tilt sensor, which is a common problem on early 996's.
Cheers Richard.
It's actually a single beep and then another about 20 secs later. Did it again last night. I started and drove off. After about 5 mins, Beep and then after 20 secs Beep. I noticed that the lock button light (on the dash) was on too, but wouldnt turn off when the button was pressed. I stopped, opened both doors (both required 2 opens of the handle to open door) and carried on with no further probs. When locking the car last night all fine and I opened and locked again this morning with no probs.
Its a facelift 2001 (51).
Any more ideas?? I gyess I could take it to Paragon on Sat to get the codes checked.
Cheers
Dazz
If it is single-beeps you are getting, then it probably won't have any codes stored, but is still worth checking, just in case. What you describe is really wierd, as it sounds like the car is auto-locking, and I presume you haven't got auto-locking set. I don't suppose the carpet is wet under the passenger seat, is it? (Check carefully). If not, then I would suspect a loose connection, or a faulty alarm control unit.
This is a source reference. Confirm exact model applicability in the original material.
