Data Field Descriptions; Cross Zoning; Conditions That Affect Cross Zone Operation - Honeywell VISTA-128BPT Programming Manual

C C r r o o s s s s - - Z Z o o n n i i n n g g
UL Cross Zoning is not suitable
for use in a UL installation.
Cross Zone logic is only in affect when
the panel is armed and is designed so
that a combination of two zones must
be faulted within a 5-minute period of
each other. This prevents momentary
faults from one of the zones from
causing an alarm condition.
(Once the first zone trips, the cross
zoning window begins, and when the
2nd zone trips within that window, the
alarm for both zones will occur).
You can select four "sets" of cross-
zones (programmed in data fields
1∗22, 1∗23, 1∗24 and 1∗25), keeping
in mind the following:
• Both zones in each set must
protect the same area.
• When cross-zoning motion
sensors, both device's areas of
protection must be situated so
that both units will trip within
five minutes of each other if
their shared protected area is
violated.
• Both zones in each set must be in the same partition.
DO NOT cross-zone a fire zone with a burglary zone under any circumstance. A fire zone must only be crossed to
another fire zone and BOTH must be protecting the same physical area (no walls or partitions separating them).
Consult NFPA 72 standard for exact spacing requirements. As a guideline, we recommend that spacing between
fire cross-zones be no farther than 30 ft.
C o n d i t i o n s T h a t A f f e c
C o n d i t i o n s T h a t A f f e
1. DO NOT use the same zone number for different cross zone pairs, it will "confuse" the cross zoning logic and
produce unpredictable results.
2. In the event of a continuous fault (lasting at least 5 minutes) on one of the paired zones, a fault on the second zone
will cause an immediate alarm.
3. If one of the zones in a pair is bypassed or has a zone response type set to 0, the cross-zoning feature will not apply.
4. If an entry/exit zone is paired with an interior follower zone, be sure to enter the entry/exit zone as the first zone of
the pair. This will ensure that the entry delay time is started before the follower zone is processed.
5. If a relay is programmed to activate on a fault of one of the zones, the relay activates without the other zone faulted
(will not work on 24hr zone types).
6. If a relay is programmed to activate on either an alarm or trouble, both zones must trip before the relay will activate,
and both zones must restore for the relay to deactivate (if relay is programmed to deactivate on a Zone List
Restore).
7. Crossed zones will still chime (does not require both to fault).
8. The Event log shows and reports both zones.
• If one zone in the pair trips it is completely ignored.
• If the one of the zones trips and remains tripped, after the 5-minute period there will be no local notification,
but a trouble message is reported and logged.
• The Contact ID event code is E378 Cross Zone Trouble.
t C r o s s - Z o n e O p e r a
c t C r o s s - Z o n e O p e r a
t i o n
t i o n
27
SECTION 3: DATA FIELD DESCRIPTIONS