Cooper Security 9853 won't reboot.

We have just purchased a property that has been empty for 5 years and the batteries were all dead after the electricity was disconnected from the Cooper Security 9853.


The main 9853 box has a 17ah battery and this has been changed and the separate power supply has also had its battery changed. I haven't changed or looked at either of the 2 external alarm boxes yet.


To reset the access codes I have followed the manual and (1) disconnected the mains and battery, (2) linked the NVM and kick start pins, (3) reconnected the battery, (4) remove the links, (5) replace the lid and (6) switch the mains back on.


Both keypads display "Ver 4.00 Feb15 2007" (this happens as soon as you reconnect the battery) which I assume is the software and it's build date but nothing else. It chimes twices when it powers up and responds to the keypresses. The first 6 keypesses are greeted with normal beeps and after that the beeps turn louder and deeper like errors. A couple of times the countdown timer beeps have started but it never alarms it just keeps beeping.


So it has had new batteries, the reset procedure has been followed but will it reboot? Will it heck as like reboot. Any ideas peeps.....

Sounds like there is a data issue between the keypads and the main control panel. The keypads will display the version number when they have power but can't communicate with the panel. Did you ever have anything on the display other than what it shows now? IE before the reset was attempted?

It's worth checking that the clock and data connections to the keypads are sound in the control panel and keypads. May also be worth removing one of the keypads and connecting it up to the panel on a short piece of alarm cable to rule out any cabling issues. If not, you may have to replace the control panel (the 9853 is no longer manufactured)

Hi it could be data line as above but iv had 4 last year go down with the NVM (chip) if it was me id throw it in the bin, pour petrol on it and strike a match, pull up a stool, crank open a beer and watch it burn, good in its day but cant compete with a Pyronix

Have you tried 123456 as the code ? It may be set at 6 digits

Thanks guys and it was the key pad in the Annexe stopping the comms, I disconnecting Data and Clock from it and the others came back to life. When you exit installation mode it flags Z13 open which is the smoke alarm next to the faulty keypad. I popped the top off and it has clearly had water in it. I suspect the bathroom above had a leak at some point and did for them both.

Because of the open fault on Z13 I can't go any further. I have ordered a new detector and keypad but can I link out Z13 with a wire or resistor?

Thanks again I am chuffed it lives.

If it was resistor wired ! 2.2k

There are 2 resistors in series in the smoke detector base. One is a 2.2k and the other a 4.7k. Picture attached with all the lovely rusty bits. do I just put a 2.2k across the sensor pins in the controller? Thanks again.

Picture is at https://drive.google.com/file/d/14IOeiInARlYfss2qMw3Itsr4yDbpNxE5/view?usp=drivesdk

Get a connector block and strip back the blue and yellow ( if it's corroded ) and terminate with the 2.2k resistor to bypass the smoke detector for now ...or put 2.2k resistor across the zone in the panel ...
That's a texecom smoke detector

All sorted now with a new smoke detector and a good clean up of the keypad. Thanks again for the tips.