Master Keypad Setup And Operation - Honeywell VISTA-32FBPT Installation And Setup Manual

Sequence #2:
User #2:
User #1:
User #2:
User #1:
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.
Do not assign partition 1 as the common lobby if fire zones are being used in the system. All fire zones must be
assigned to partition 1 to ensure all Fire Test modes operate correctly.
How User Access Codes Affect the Common Lobby
Codes with Global Arming
If a code is given "global arming" when it is defined (see the SECTION 6: 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
•
Arming/Disarming Remotely
If a user arms or disarms remotely (through Compass downloading software), the lobby does not automatically follow
another partition that is programmed to arm or disarm the lobby. The lobby must be armed separately, after arming all
affecting partitions first.
Auto-Arming/Disarming
If scheduling is used to automatically arm and/or disarm partitions, the common lobby partition does not automatically
follow another partition that is programmed to arm or disarm the lobby. The lobby partition must be scheduled to
arm/disarm and must be scheduled as the last partition to arm.
If you are using auto-arming, make sure that the Auto-Arm Delay and Auto-Arm Warning periods, for the lobby
partition, (fields 2∗05 and 2∗06) combined are longer than that of any other partition that affects the lobby. This
causes the lobby to arm last.

Master Keypad Setup and Operation

Although this system has two actual partitions, it provides an extra partition strictly for the purpose of assigning
keypads as Master keypads for the system.
Assigning any keypad to Partition 3 in Device Programming in the #93 Menu Mode (Vista-32FBPT Programming Guide)
makes that keypad a Master keypad. A Master keypad reflects the status of the entire system (Partitions 1-2) on its
display at one time. This is useful because it eliminates the need for a building security officer to have to log on to
various partitions from one partition's keypad to find out where an alarm has occurred.
U L
In Commercial Fire installations, field 2∗18 (Log on from other partitions) must be disabled for partition 1.
Office 1 Office 2
(Armed) Disarms
Disarms (Disarmed)
(Disarmed) Arms
Arms (Armed)
Lobby Action
Disarms
(No change)
No Change
No Change
19