M1EZ8 Installation and Programming
Page 19
[Effective w/Firmware 4.3.6]
3.1 Introduction
The Security functionality of the Control can be programmed either from an ELK-M1KP LCD Keypad OR from the ELK-RP PC
Software. The keypad features a menu-driven “Text” based interface with simple Yes/No answers for most options. After just
a short amount of experience the average installer will not even require an instruction manual to keypad program the control.
For the Automation functionality the ELK-RP PC Software is a requirement. The options and capabilities available for
automation are so unique and powerful that it takes a PC to make use of all the benefits. The control features a powerful
“Whenever/And/Then” RULES based programming that allows almost any imaginable operation.
3.2 Local Keypad Programming
There are two levels of operation for programming the control locally, user level and installer level.
- User level programming provides the ability to add, change, or delete user passcodes and names. It also allows custom
automation settings to be viewed and changed. A master user code is required to access the user code and custom settings
screens. User programming is explained in the User’s Guide.
- Installer level programming allows total customizing of the Security operating features. Only the installer code may access
this level. If the installer code is lost or forgotten, it is impossible to program the control locally. Anyone attempting installer
level programming should be familiar with the contents of this publication prior to programming the control panel. If remote
programming is used, it is possible to “lock out” or prevent takeover of a control by another installation company by selecting
“Lockout Local Prog.” This prevents the installer passcode from gaining access to programming via an LCD keypad. The
installer passcode may still be used for the non-programming functions described in Chapter 2. Lockout Local Prog does not
affect remote programming.
3.3 Local or Remote Computer Programming (ELK-RP) and Anti-Takeover
ELK-RP programming utilizes extensive error checking and security safeguards, including data encryption, password log-on,
serial number, and dealer assigned RP access code. The serial # identifies the control to RP while the RP access code
identifies the computer to the control prior to a programming session. RP loads the access code during the first connection. It
cannot be viewed or changed from local keypad programming. In addition to these safeguards, you can set an anti-takeover
option from RP which prevents certain keypad programming. Even a total default of the panel programming cannot reset the
anti-takeover option once it is set..
The Factory Default Elk-RP Access Code is: 2 4 6 8 0 1
3.4 Area Partitioning
The control may be divided into 1 to 8 independent areas (partitions). Each area appears as a full-featured system, allowing
one control to be shared by multiple, independent departments within a common structure. Zones, User Codes, and
Keypads may be assigned to any 1 area up to the maximum number available. An example is a single business divided into
separate departments, each department occupied by different employees. Mount the control in a secure area (common utility
closet) with dedicated and uninterrupted AC power and telephone service. Then assign zones, codes, and keypads to each
department.
The Alarm Output (Output 2) activates on all alarms, regardless of the area. The RP Software Rules can be used create
additional (separate) outputs. When reporting to the central station events like AC Power Failure, Automatic tests, Low Battery,
etc., are considered system reports and are transmitted using the Area 1 account number. If area partitioning is not desired,
simply designate all zones to a single area (Area 1) which is the factory default setting for zones 1-8.
COMMON AREA
- Another popular feature is the ability to have one or more areas made “common” to Area 1. This is often
referred to as a “Vestibule Feature”. Any of the Areas 2 thru 8 may be made common to Area 1. The result is: Area 1 cannot be
armed until all its common areas are armed. Once armed, Area 1 will disarm if any common area becomes disarmed. This
is good for lobbies or vestibules shared by two or more businesses. Each business must have their own area keypad.
NOTE: If you want Area 1 to automatically arm when all its common areas become armed, use a Whenever/And/Then rule
from the RP software to do this.
Section 3 - Programming The Control
WWW.DIYALARMFORUM.COM