2 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHAlarm Faults and PIWIS
Leading reported evidence
Set 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.
Suggestion · Original poster
I'm figuring the "activation: secured via radio" is to note the fob remote was utilized to set the system?
Leading evidence: 'Set system' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Set 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 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 · Original poster
34 - Passenger compartment monitoring sensor, short-test - no answer, short circuit to B+/faulty
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.
2 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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T213932Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
This started on Sunday evening, when I heard the alarm on my car ('04 C4S Cab) going off. Turned it off and left it unlocked. Monday I scanned the car with Durametric and didn't see any faults. Cleared anyway, and locked it. Alarm went for a repeat. After repairing the VAS 6154 adapter (USB port broke off), I scanned the car tonight to see the following faults:
33 - Passenger compartment monitoring sensor, long-test fault, faulty
34 - Passenger compartment monitoring sensor, short-test - no answer, short circuit to B+/faulty
46 - Central locking synchronization, unsuccessful after safe locking
49 - K-line, short circuit to ground
54 - Radio receiver faulty
60 - Central locking limit position Locked not reached, switch position implausible
Events:
1 - Alarm actuated by passenger compartment monitoring - Activation: secured via radio
2 - Alarm actuated by passenger compartment monitoring - Activation: secured via radio
3 - Alarm actuated by expiry of entry delay - ---
4 - Alarm actuation by "locked" contact on passenger's side - Activation: secured via radio
5 - Alarm actuated by expiry of entry delay - ---
6 - Alarm actuated by expiry of entry delay - ---
7 - Alarm actuated by expiry of entry delay - ---
8 - Alarm actuated by expiry of entry delay - ---
9 - Alarm actuated by expiry of entry delay - ---
10 - Alarm actuation by oddments tray - Activation: secured via radio
I'm figuring the "activation: secured via radio" is to note the fob remote was utilized to set the system? Is the list in new-to-old order? Is the expiry actuation when it's unlocked and re-locks after the doors are unopened? I've cleared both the faults and events so I can start fresh and go from there. I did not lock it tonight and will try again tomorrow to see what the system records.
- The alarm module is dry, no moisture under the driver's seat
- Car starts up normally
- Key remote works normally (no beeps on engagement)
- I have a rigid sunshade in the windshield
- Ambient temperature around 80-85* with high humidity
- No standing moisture inside the car
- Door handles (exterior and interior) operate normally and have expected window drop activation
I'm planning to take the alarm module out and inspect it for any obvious signs of corrosion or failures. If the same activation events and fault codes reappear, would it be logical to determine there may be an issue with the interior sensors that warrants additional diagnostic effort?
While the existing threads for alarm issues did have similar codes, mine seems to be a little unique - as is this situation as I did not have any alarm issues in the nearly 14 years I had my '04 986.
Thanks in advance.
Yes, you have cleared the faults that are stored, now you can see what activated the Alarm after the Event reoccurs and you retest to see the newest code
This is a source reference. Confirm exact model applicability in the original material.
