Securitron SABL INSTALLATION - Manual (Page 17)

PN# 500-19700
Page 17 Rev. C, 8/07
C. Troubleshooting
PROBLEM-- Keys do not operate but a beep is heard every five seconds
This is a diagnostic feature which indicates that one of the keys is being read as down
(always being pressed). In that condition, the CPU board will not be able to read any
other keys. It can happen because of mechanical failure within the switch element such
that the key really is down, or keypad wires that are shorted to each other. The latter
problem usually happens when insulation is scraped off some of the wires in the keypad
cable as it is being fed through the door. You may be able to restore operation by rapping
on all the keys. If this works, however, it is likely only a temporary fix and you should be
prepared to change the keypad. Next, check the wiring of the keypad cable into the
board. If you don’t see any problems, the keypad will need to be replaced.
PROBLEM-- A key isn’t echoed (no beep or LED flash)
This is the opposite of the above problem. A key is failing to be read when it is pressed.
This can happen because of mechanical failure within the switch element such that the
key will not close, or from a broken keypad wire. If, however, the problem is with a wire,
more than one key will be “dead”. If just one key is not being echoed, the problem is with
the key itself. You can, of course, use the unit for all operations that don’t require that
particular key but you will want to replace the keypad for full operation.
PROBLEM-- Unit beeps when keys are pressed but does not accept programming
If the problem occurs on initial installation, usually it's caused by misunderstanding the
programming instructions. Read them again carefully. Be sure you're not waiting more
than 5 seconds between hitting keys as if you are, the entry will be ignored.
PROBLEM-- Beeper doesn’t sound while the unit otherwise functions
Note that the beeper could have been deliberately silenced by the unit having been sent a
special command. Even on a new unit, this could have happened by factory error.
Attempt to restore the beeper by putting the unit into program mode and entering 7-2.
You should see the two red flash confirmations. If the beeper still doesn’t work, the
problem is either a wiring mistake, a defective beeper or a fault on the CPU board with the
output that drives the beeper.
PROBLEM-- One or more of the LED’s do not work while the unit otherwise
functions
This is either a wiring mistake, a failed LED in the keypad or a fault on the CPU board with
the output that drives the LED. The keypad will have to be replaced to restore operation
of the LED.
PROBLEM-- Error signal (one second long red pulse) received while programming
Anytime you receive an error signal, retry the programming operation. It’s easy to mis-
hit one key. If the error signal persists, it is almost always a misunderstanding of
programming procedures rather than a fault with the unit. A product fault that impaired
the operation of the microprocessor would generally prevent it from giving you the error
signal.
When programming the Hard Code, you directly enter the code once you are in hard
programming mode (slow yellow flash). Remember you must never pause for more than
five seconds while pressing keys. The only way to get an error signal while programming
the Hard Code is to enter an illegal one digit code or a subset code.
When in program mode, the most common error is to forget to enter the two digit
memory slot prefix when attempting to program a code. Valid prefixes are 00-59 and if
this step is forgotten in an attempt to enter the code directly, there are a lot of sequences
that will create an error signal. For example, any sequence that starts with 6 will be