Honeywell VISTA-128BPEN Installation And Setup Manual page 16

Vista-128BPEN Installation and Setup Guide
b. The common lobby cannot be armed unless every
partition selected to affect the lobby is armed.
1*19 Arms Lobby (must be programmed by
partition)
Setting this field to 1 for a specific partition causes that
partition to affect the operation of the common lobby as
follows:
a. The common lobby cannot be armed unless every
partition selected to affect the lobby is armed.
b. Arming a partition that is programmed to arm the
lobby causes the system to automatically attempt
to arm the lobby. If any faults exist in the lobby
partition, or if another partition that affects the
lobby is disarmed, the lobby cannot be armed, and
the message "UNABLE TO ARM LOBBY
PARTITION" is displayed.
You cannot select a partition to "arm" the lobby
unless it has first been selected to "affect" the
lobby. Do not enable field 1*19 without enabling
field 1*18.
The following chart sums up how the common lobby
partition will operate.
1*18 1*19 Disarms
Affects Arms when
Lobby Lobby partition
disarms?
0 0 NO
1 0 YES
1 1 YES
0 1
Example
Here is an example of how the lobby would react in a
typical setup.
OFFICE 1
User #1 has access to Office #1 and the Common Lobby.
User #2 has access to Office #2 and the Common Lobby.
Office #1 is set up to affect the Common Lobby, but not
arm it.
Office #2 is set up to affect and arm the Common Lobby.
2-2
Attempts Can be armed
to arm if other
when partitions
partition disarmed?
arms?
NO YES
NO NO
YES NO
---ENTRY NOT ALLOWED---
OFFICE 2
COMMON LOBBY
MAIN ENTRANCE
V128BP-001-V0
NOTE: In the tables below, the notations in
parentheses ( ) indicate the current status of the other
partition when the user takes action.
Sequence #1:
Office 1
User #1: Disarms
User #2: (Disarmed)
User #1: Arms
User #2: (Armed)
Sequence #2:
Office 1
User #2: (Armed)
User #1:
Disarms
User #2: (Disarmed)
User #1: Arms
Notice that in sequence #1, because Office #2 was the
last to arm, the lobby also armed (Office #2 is
programmed to affect and arm the lobby). In sequence
#2, the lobby could not arm when Office #2 armed,
because Office #1, which affects the lobby, was still
disarmed.
When Office #1 armed, the lobby still did not arm
because Office #1 was not programmed to arm the
lobby. User #1 would have to arm the lobby manually.
Therefore, you would want to program a partition to
affect and arm the lobby if the users of that partition
are expected to be the last to leave the building.
How User Access Codes Affect the Common Lobby
Codes with Global Arming
If a code is given "global arming" when it is defined (see
SECTION 9: User Access Codes), the keypad prompts
the user to select the partitions they want to arm. Only
the partitions the user has access to are displayed. This
allows the user to choose the partitions to be armed or
disarmed, and so eliminates the "automatic" operation
of the lobby. Keep in mind, however, that if a user
attempts to arm all, and another "affecting" partition is
disarmed, the user cannot arm the lobby, and the
message "UNABLE TO ARM LOBBY PARTITION" is
displayed.
Codes with Non-Global Arming
If a user arms with a non-global code, the lobby
partition operation is automatic, as described by fields
1*18 and 1*19.
Other Methods of Arming/Disarming
Common Lobby logic remains active when arming or
disarming a partition that affects and/or arms the
common lobby in one of the following manners:
•
Quick-Arm
•
Keyswitch
•
Wireless Button
•
Wireless Keypad
Office 2 Lobby Action
(Armed) Disarms
Disarms No Change
(Disarmed) No change
Arms Arms
Office 2 Lobby Action
Disarms Disarms
(Disarmed) (No change)
Arms No Change
(Armed) No Change