12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHTrouble shooting alarm fault on Turbo
Reported or suspected cause
rear brake light switch
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 · Original poster
turned out to be a faulty rear brake light switch.
Leading evidence: 'rear brake light switch' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'rear brake light switch' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check done' (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
The F***ING thing went off again about an hour later, then again and at about 2am I had enough, as did everyone in the road, so I disconnected the battery.
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
On facelift cars they fitted a new type of sensor under the passenger seat.
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
Also, the alarm stores the last 10 events, so would show what caused it to go off if you get a diagnostic check done.
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 you have an indy in your area, I would get a diagnostic check done first.
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
The F***ING thing went off again about an hour later, then again and at about 2am I had enough, as did everyone in the road, so I disconnected the battery.
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.
12 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: 20261027T003124Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi fella's,
Last night the alarm on my Turbo started going off for no reason. I went out to the garage, checked it over and everything was closed (All monitored contact points etc). What was strange was the fact that the alarm hadn't even been set as I had left it unlocked when I put it away last night (No self arm as driven straight in and left).
I left the car again and I guess you know what happens next. The F***ING thing went off again about an hour later, then again and at about 2am I had enough, as did everyone in the road, so I disconnected the battery.
When it was sounding the key fob would not turn it off. the car would lock and unlock but the alarm would keep sounding until it turned it self off. Once it had stopped the fob would lock it and arm and there was no beeps to state that something is a miss??
Any ideas guys? Bloody annoying as i don't have the radio code, it was miss laid when having something sorted on the car a while a go and I never chased it up, pants!!
Cheers
Jim
As Andrew says - get the battery checked, as a low voltage condition can cause the alarm to go off. Also, the alarm stores the last 10 events, so would show what caused it to go off if you get a diagnostic check done.
As for the radio code, I have a decoder which can give you the code from the serial number of the radio. It works 90% of the time. Assuming you have a CDR-22, you can get the serial number by:
Hold down the TP button for at least 10 seconds after you turn the radio on. "Becker 1" will be displayed. Rotate the right knob (slowly) and it will display the Becker model number. Then rotate it again and the serial number should be displayed on the radio.
Alternatively, if you get a diagnostic check done, the radio code is often stored in the DME vehicle data. If you are anywhere near me I'd be happy to do a check for you.
Thanks for the replies fella's.
Richard, thanks for the offer but I'm not local unfortunately. I will follow your instructions and try and obtain the number.
I hooked the battery up again this morning and luckily the alarm stayed off and didn't blow my ear drums to pieces, lol. Although I was prepared this morning and had put some ear plugs in.
The voltage read 12 and the car started instantly. Once running it read 14.
I armed and disarmed a couple of times and there was no beeps to say anything was a miss. I left it armed and will monitor it during the day. What's the betting it will go off late tonight!!
Thanks again
Jim
P.S. I love this forum.
Well that didn't last long :sad: It has just gone off so I have disconnected the battery again. I will book it in with rsj's this week as I think i have an ABS/wheel sensor fault anyway.
What a pain in the back side!!
Jim
All sorted, wahoo.
The alarm was siren backup battery was knackered!! Whilst at RSJ's I also had my ABS/PSM warning light fault sorted. turned out to be a faulty rear brake light switch.
Got to say RSJ (Joel, Darren and Sid) were great as per usual!!!!
James
Must say I have been having EXACTLY the same problem. Phoned the guys at RSJ (where I got my car from) and the guys mentioned that water can be the problem also as the battery tray drains can block and you can have wee swimming pool in there which is right next the alarm connections...
Anyway thought I had cracked it with this, but yet again it goes off so I leave the car unlocked in the garage..
Now I see the backup battery could also be the problem I will try that next... Does anyone know where it is before I start pulling apart the wrong area?
Cheers
The alarm siren is mounted to the right of the battery (as you look at it from the front of the car) under a plastic cover, which is held on by a single T20 Torx screw.
Before you disconnect the alarm siren, switch on the ignition, but don't start the engine. Otherwise (if the backup battery is OK) it might go off.
If you have an indy in your area, I would get a diagnostic check done first. It should show what's at fault. The alarm module also stores recent events, so will tell you what triggered the alarm.
Richard
Cheers for that, I found the alarm module and connector etc, but do you know where the backup battery is? Is it in the alarm unit itself I will remove or is it in the control module under the passenger seat?
I had error codes checked at OPC during last service, no codes were given on the alarm, hence why I am keen to look into this battery point.
Cheers
Hi fella's,
Just seen that this thread has been brought back up. Well, as it happens my alarm fault wasn't sorted. Shortly after typing my last reply it went off again :nooo: So I ended up taking the siren unit out, which luckily is very easy. The alarm then reverts to using the horn and indicators when it is triggered. Since i did this it hasn't gone off once, :thumbs:
Obviously I now have a brand new siren for nothing, lol. It would appear that for some reason there isn't enough charge going to the siren and the backup battery runs low and thus triggers the siren. Apparently the siren is an add on for the English market. This might explain why I didn't get any fault codes on the computer!!
I'm not going to get it looked at now until Service time as it is working fine without it.
Jim
996.618.237.01 is the part number of the siren itself. The backup battery it in the siren itself, as you have found.
Another common cause of false alarms on early cars is the tilt sensor filling up with water. On facelift cars they fitted a new type of sensor under the passenger seat.
This is the early type sensor, under the siren:
This is a source reference. Confirm exact model applicability in the original material.
