Appendix A. Implementing Partitions
You can define up to 16 true partitions. Each partition is consisted of several zones, and is
normally a defined area, such as a building floor, a store, or a compartment. Every partition can
have its own subscriber ID no., user codes, keypads, peripherals, etc.
Partitions’ event reporting is subject to the following:
All the partitions IDs to which the zone is allocated
• If the zone is allocated to more than one partition, a separate report
will be sent on each partition.
• If only partition #1 ID is defined, any event will carry that number.
Zone, keypads, users, and contacts can be allocated to more than one partition. In such a case,
the following will apply:
1. Arming a zone is subject to all the partitions that the zone is allocated to: it will only be
armed when all its partitions are armed.
2. An armed zone becomes disarmed, as soon as one of the partitions it is allocated to is
disarmed.
3. Arming and disarming via a keypad is subject to both the keypad and the user’s partitioning.
For example, if a user that is allocated to partitions 1, 3 & 5, enters its code in a keypad that
is allocated to partitions 4, 5 & 7, only partition 5 will either be armed or disarmed.
4. A keypad can only display and control the partition/s to which it is allocated. The
Armed
LED stays on only when ALL the keypad’s partitions are armed, and flashes when only some
partitions are armed.
To Next Page
Loading...
Need help?
General
