4 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH2001 996 double beep/locking woes
Reported or suspected cause
alarm board
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
In my case it was the alarm board that had to be replaced.
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 was beginning to suspect the alarm module when the input status was being shown incorrectly and was not updating and also activations were not working coupled with the Duramatic software locking up every so often requiring disconnecting the cable from the PC and/or turning the key off and then back on.
Leading evidence: 'alarm board' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'alarm board' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Disconnect cable' (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
I initially replaced both locks (and became pretty good at doing that part as they went in and out a few times!) but the problem was not with my locks or the programming of my original alarm board.
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 was beginning to suspect the alarm module when the input status was being shown incorrectly and was not updating and also activations were not working coupled with the Duramatic software locking up every so often requiring disconnecting the cable from the PC and/or turning the key off and then back on.
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 was beginning to suspect the alarm module when the input status was being shown incorrectly and was not updating and also activations were not working coupled with the Duramatic software locking up every so often requiring disconnecting the cable from the PC and/or turning the key off and then back on.
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 am thinking (and hoping) that there is nothing wrong with the alarm module and the issues I was running into with the wrong input states, freeze up, actuations not working are all Duramatic software issues but my real problem is either a microswitch inside the lock mechanism (perhaps on the passenger side door as that is not locking even when using the key in the door) or something in the lock assembly on that side?
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Disconnect cable
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 was beginning to suspect the alarm module when the input status was being shown incorrectly and was not updating and also activations were not working coupled with the Duramatic software locking up every so often requiring disconnecting the cable from the PC and/or turning the key off and then back on.
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
I initially replaced both locks (and became pretty good at doing that part as they went in and out a few times!) but the problem was not with my locks or the programming of my original alarm board.
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 am thinking (and hoping) that there is nothing wrong with the alarm module and the issues I was running into with the wrong input states, freeze up, actuations not working are all Duramatic software issues but my real problem is either a microswitch inside the lock mechanism (perhaps on the passenger side door as that is not locking even when using the key in the door) or something in the lock assembly on that side?
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 was beginning to suspect the alarm module when the input status was being shown incorrectly and was not updating and also activations were not working coupled with the Duramatic software locking up every so often requiring disconnecting the cable from the PC and/or turning the key off and then back on.
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.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
I started having these issues recently with my 2001 996. No water issues or accidents. All OEM equipment. Car sits unlocked in the garage most of the time plugged into a Porsche battery mender. Drove it twice within the last week after having not driven it in a while and drove fine. One of the drives was to get an oil change. The day after it was last driven, started getting an occasional double beep while in the garage every few hours and heard the locks buzz on their own too. The light inside the frunk goes on and off on its own as well.
Read these fault codes using Duramatic:
I can clear the error codes but they come back.
61: Central locking limit position Unlock not reached
47: Control locking synchronization
The following work correctly:
-Open outside driver door handle, window drops down
-Open driver door, window remains down
-Open outside passenger door handle, window drops down
-Open passenger door, window remains down
-Both inside door handles lower the window the same way as the outside ones and if I open either door from inside, the window stays down
These things below are not working correctly:
-If I use the fob to open the frunk then it unlocks but is accompanied with a double beep.
-Try to lock using fob and get the double beep and hear the buzz of the locks trying to lock but both doors remain unlocked as does the gas cap door
-I have tried pulling the locking pin out into the locked position on the gas cap door but it does not seem to actuate on its own when I lock.
-Turn key in driver side door lock once to lock and get a single beep and driver door locks but and passenger door and gas cap remain unlocked.
-Doing emergency locking procedure (3 quick CW turns) results in no beep but again only the driver side door locks and NOT the passenger door or the gas cap.
-Once locked with either of the two previous approaches, I can unlock the driver door using the fob but get the double beep
-I can open the frunk using the fob or inside switch. When opening using the fob, I get the double beep.
-I can open engine compartment flap using switch.
Using my enthusiast i.e. cheapskate version of Durametric, I see most of the status shown are wrong and do not change state to reflect the true state of the doors etc. Found an old post saying the earlier version of Duramatic v6.3.1.7 that I was using was not correctly decoding this data. The current version 6.6.3.5 no longer appears to have an input status indication as you can see in the snapshot below. Also this current version lists an AIarm I32 and Alarm I48. I am guessing this car has an I32 as that is all the older version of Duramatic listed but these two different options being listed in the current version was confusing along with the absence of the Input Signals option:
The activations in either version only seem to result in a double beep and buzzing sound of the locks
I was beginning to suspect the alarm module when the input status was being shown incorrectly and was not updating and also activations were not working coupled with the Duramatic software locking up every so often requiring disconnecting the cable from the PC and/or turning the key off and then back on. So I removed the alarm module and inspected both sides of the circuit board (see pic below) and all appears fine. Tested the one electrolytic 220uF capacitor while in circuit using an ESR tester and it read 200uF and .18 ohms so appears to be fine (no signs of bulging or leaking of electrolytic fluid). So I put it all back and had to do the emergency locking to get anything to work again but now I am back to exactly the problems I originally had.
I am thinking (and hoping) that there is nothing wrong with the alarm module and the issues I was running into with the wrong input states, freeze up, actuations not working are all Duramatic software issues but my real problem is either a microswitch inside the lock mechanism (perhaps on the passenger side door as that is not locking even when using the key in the door) or something in the lock assembly on that side?
What is the best way to troubleshoot this? Is there a pinout for the connectors on the alarm module so one can try and test if a microswitch is bad?
Thanks.
Danix, I did finally get this issue resolved. In my case it was the alarm board that had to be replaced. I initially replaced both locks (and became pretty good at doing that part as they went in and out a few times!) but the problem was not with my locks or the programming of my original alarm board. Also my original alarm board had no water damage either. It just developed this weird issue. You can see more details on my saga under this post:
Help - 996 door locking and frunk light issues - 996 Series (Carrera, Carrera 4, Carrera 4S, Targa) - RennTech.org Community
The
Utah$man
post was me too.
Good luck
