15 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHAnother issue, it keeps beeping at me
Reported or suspected cause
interior monitoring sensor had given up
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.
Reported cause
Just to add my recent experience - 2 beeps after locking turned out to interior monitoring sensor had given up.
Leading evidence: 'interior monitoring sensor had given up' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'interior monitoring sensor had given up' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check value against the item' (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
Ever since I reconnected the battery whilst it was off the road for welding the car has started beeping at me.
Use piwis or autologic tester as ive lost patience
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
After that i use the Piwis or autologic tester as ive lost patience .
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 · Original poster
I'm wondering if the issue is the ignition switch although I replaced it last year with a new one as it wasn't returning from the start position.
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.
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: 20261027T005001Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Well it seems I'm on a roll with the car having issues at the minute. Ever since I reconnected the battery whilst it was off the road for welding the car has started beeping at me.
It beeps once when I get out of the car and then beeps twice when it's locked, I believe this is to signify an issue with the alarm/ locking system. I thought it'd be easy to check using durametric but I keep getting an error saying the cable can't be detected.
I'm wondering if the issue is the ignition switch although I replaced it last year with a new one as it wasn't returning from the start position.
Without durametric is there an easy way of testing what's causing the beeping?
Chris
Centre console cubby hole lid, thats the usual place for me. When I lean on it my elbow slightly pushes the button and releases the lid. I don't realise until I lock it and it starts complaining
Im going to be different just for the hell of it .. also i dont think its the center consol lid
Beep once .. something is not in a position that the alarm system likes .. it see something open basically ..
Beep twice and its a fault .. something is not doing what it should and not something thats open ..
Im going with a door lock ass. and probably the drivers side as thats the most common of the 2 to fail
You need a tester to check as its a 5 min job to diagnose .
The cable fault .. yup its a pain .. it seems when ever i use ours it does that .. i unplug and plug the lead back in then run the software again .. sometimes several times .. also try staying in the program and unplug/plug it then try accessing the system .
After that i use the Piwis or autologic tester as ive lost patience .
Now you mention locks demort, awhile ago I unlocked the car and the passenger door didn't open I had to cycle the locking a few times to get it to open could it be linked?
The beeping didn't start until quite awhile after that though.
Is there a way to test the locks without a tester incase my cable continues to refuse to play ball?
Yup it could well be the passenger lock .. but we are all guessing and there are several items that could cause this fault .
Its a quick job to diagnose with a tester .. you look at the values for all the items involved then lock the car .. the doors have a normal lock and a secured lock so it might say secured but not locked .. it may well be seeing a key barrel stuck on open .
you cant check a lock as such without a lot of work and a wiring diagram .. you would have to test each micro switch .. and then possibly the same for the other side ..
Its not worth the effort .
I had a chat at work about the cable fault .. boss says its normally the usb port on the computer , try another usb port and perhaps have a look at the cable usb .. contacts all ok etc .
You could also try reinstaling the software .
Need to get a tester on it basically .
@ JS1500 no arguments from me there :thumb:
Time to bump an old thread, I've now got a working durametric pro cable so how would I go about testing what's causing the issue?
I can say it's not the cubby hole latch I tested it with a multimeter and it's working properly, I'm going to remove the bonnet and engine bay switches next and check them with the meter as there easy access
There should be some actual values for the alarm system .. your looking for something that says front bonnet , door open , door secure etc etc
You then check the value against the item .. so does it say door closed on the tester when the door is closed .. does it say both doors are secured when you lock the car and so on .
Just to add my recent experience - 2 beeps after locking turned out to interior monitoring sensor had given up. Local Porsche centre wanted to charge me £188 for sensor plus minimum of 2 hours labour ( ' don't really know how long it will take we have never done one before!") for grand total of at least £392.
Purchased good second hand complete interior light unit ( where monitor is housed) for £45 and fitted in 10 minutes - result!
Demort I don't know if your work has a different version of durametric to me(v6.5.5.5) but I can't see an option for actual values in the alarm section?
the activations section allows me to lock and secure the doors and the other latches etc. but there's nothing I can see that shows what's activated/locked when I press the fob?
