Electronic Alarms and Home Security Devices - DSC 5010 section 020 locked out?

I have a fault 5 on zone 1 that I can't seem to clear. I recently added an extra keypad and reassigned all 3 keypads to 11,12 and 13. I wanted to make sure the keypad zones are null to eliminate the possibility of zone 1 being associated with a keypad, but when I try to enter section 020 I get the long error beep. Is this a hardware issue, or have I somehow disabled this function?

Zone 1 is supposed to be a smoke detector but I have since disconnected the input wire and made it null (00), but the fault will not clear. Another issue is that I have set the front door for entry delay but it sets the alarm off immediately. I have re-entered the 30 second entry time, but still have problems.

Thanks in advance for any help!

Exactly what keystrokes did you enter to make the changes you described?

It's really easy to be one segment off and not realize it

Ron, thanks so much for responding - I have been reading a lot of your advice lately trying to figure this out, and had been hoping that you would come to my aid!

To assign the keypads, *8 5010 000 0 11 for the first keypad, then 12 and 13 for the 2nd and 3rd keypads (at each keypad).

My zones are:
1: Smoke detector
2: Back door
3: Basement door
4: Front door
5: 1st floor motion
6: Basement motion
7: Glass break

To set the zones I entered: *8 5010 001 07 01 01 01 04 04 03 00. Currently I have 00 for zone 1 in an attempt to clear the fault.

Any idea why I cannot enter section 020?

Thanks again!

Hmmm, if this was an ADT branded PC5010, they often have such specialty programming locations disabled from the programming.

Also, the very oldest versions of the PC5010 did not have the keypad zone feature.

What is the version number on the label on your main chip in the center of the motherboard?

It is a CPI unit, which seems to be standard (everything has always worked for me up until now anyway). The largest chip has the following: R2004, 06000464, 9708, L8 on it. Below the PC5010 number is Rev 4A(at least it looks like an 'A' but a solder pad obscures most of it). I'm considering a reset as a next step since there isn't much to do to get it back and running and I might clear whatever mistake I made.

OK, I decided to go for it and did a software reset. I still have a fault 5 showing zone 1 trouble, have toggled the EOL and NC option in section 013, no change.

I have a number '1' on the panel at all times, but the system clock has been set. Do I need to change something else? Master code has been changed too.

Thanks!

Simple test: Put a 5.6k resistor from zone 1 to common (if you have EOL enabled). Otherwise, simply jumper it closed.

If the zone closes, then it's a field wiring issue. If it doesn't, then you may have a failed zone input.

I will try the jumper trick in a second and report back.

A bit more testing with the bell unwired shows that everything behaves like it should, BUT.... when I reconnect the bell it goes off immediately when I open a door on a delay zone. The continuous beep from the keypad is correct, with a solid number on the LED for the zone. If I violate an instant zone such as the motion detector there is no beep from the keypad, just the zone number flashing and I would guess the bell would be sounding too (like it should).

Any ideas on why the bell goes off although during the entry delay period?

The jumper for zone 1 resulted in the 'Fire' LED coming on, and there was still a fault on zone 1. I don't know what this means......

I'm a bit worried that I have assigned zone 1 to a keypad but since I can't enter section 020 I can't '00' the keypad zones out. Is there a reset for the keypads?

To reset 'Fire' I had to do a software reset since it would not allow me to arm/disarm to make it go away. This time I started out by calling zone 1 '00' rather than '07' and it didn't give me a fault. The only remaining issue was a battery fault so I checked the voltage and it was 13.6V, which is too high. I had another battery with 11.9V that it seems to like - no faults now. No zone 1, but I have a bunch of smoke alarms anyway and do not have monitoring.

I tried the zone 4 door after arming and it behaved the same way - continuous beep at the keypads and the bell went off immediately. Soon my 'monitoring' neighbor is going to give up on me! What could be causing this lack of entry delay?

I would go into installer program and press 902 to reset the module list first. After 1 minute do 903 to confirm proper modules. I had the same thing happen to me a few days ago with a fire zone. I had programmed a zone for fire that wasn't, it went into trouble and wouldn't clear by reprogramming the zone. Apparently the panel needs to see fire zones clear normally before the trouble will clear. ??????? Reprogram backto fire, let it go into trouble, put the resistor across the zone then reset the keypad. Or default the panel programming and start over.

A fully charged battery is supposed to have about 13.25 to 13.75v. It's also the voltage that the charger puts out. (just like car alternators actually put out about 14.5v...) I think you may have swapped a good battery for a failing one.

My gut tells me that you are not programming the zone types that you _think_ you are programming.

The keystrokes you are writing out are the correct ones, but I don't think that's what you are actually entering.

It's really easy to get one segment off with one of these things.

Look in the installer manual in the section titled "How to program" The instructions are there on how to _view_ a programming location. View your zone types to make sure that they actually have the right settings.

I'm not sure why you are unable to access location 20. This all feels like you are a little off in your programming locations, somehow.

Well, I had a bit of time to play with it again so I re-entered the zone definitions like this:

*8 5010 001 00 02 03 02 04 04 03 00. I changed the 01's to 02's to see if it helped to use a different timer. I also changed the basement door to instant (03).

I also changed the times:

*8 5010 005 030 030 060 005

I still get no entry delay when I open the doors on zones 2 and 4 :-(

My keystrokes are very meticulous, I wait for the beeps to finish each time etc. To try and enter section 20, I enter *8 5010 020 and get a long beep.

I am leaning towards a dud board since I have performed hardware and software resets. Or could it be that my new keypad is not fully compatible with the system? It seems to be working as it should though an section 20 was accessible when I initially installed the keypad.

I'm starting to lean that way myself. If you have worked with this thing successfully before, and this is now new behavior, I'm thinking that this system has gone silicone senile (the chips _do_ fail; the laws of thermodynamics haven't been repealed).

Turn off light 6 in location 013. Test your entrance delay.

Success! Very simple really - I was not aware of the 4 second 'fault' period after the exit delay. I had been opening the door immediately after arming because I had a house full of kids and didn't want them to set off a motion sensor before I had a chance to check the door.

Thanks for all your help!

Now I can move on to getting it to page me and see if I can figure out how to get a keyfob to arm/disarm.

You sounded like you were familier with the system, so it never occurred fo me the check that you had let the exit delay time out...

You sounded like you were familier with the system, so it never occurred fo me the check that you had let the exit delay time out...

I am much more familiar with it now! Thanks again. Now I am going to get that communicator up and running......

hello
i have a fire security system bentel j524f and i cant find the instaler manual or usser manual please can anibody help my thx