Honeywell Notifier ID3000 Manual page 123

ID3000/ID2000 Fire Panel Configuration Tool Manual
MASTER/SLAVE TO ID 2 NET CONVERSION
Always start with Slave 1 (change to ID
on Specification Tab then Save), then Slave 2
and so on in order - do the Master last. This
ensures that Slave 1 becomes Panel 1,
Slave 2 becomes Panel 2 etc. The Master
becomes Panel 8. Most of the Control Matrix
input statements then continue to refer to the
correct panel. However, 'Fallback' rules
(which on Master/Slave always apply only to
the Master) will continue to refer to Panel 0
2
(meaningless on ID net) instead of Panel 8.
These rules must be deleted. New 'Fallback'
rules can be configured if desired.
6.3 ID 2 net Peer-to-Peer Network
6.3.1 Introduction
This network is fault-tolerant and provides the
transmission path integrity required by
EN54-2: 12.5.3.
Up to 125 stations can be networked in a loop.
Panels can be assigned to the first 32 station
addresses in a non-filtered environment or the first
63 addresses with filtering. Repeaters can be
assigned to any address with or without filtering.
See overleaf and Section 6.3.3 Sector
Configuration for more details on filtering.
Each station has two independent peer-to-peer
networks, one to either adjacent station (see
illustration at left). A token-passing protocol is
2 net
used. Both nodes on a network have the same
status, but the one with the token is temporarily
the master and has the authority to transmit.
Thus there is no requirement to configure a panel
as a master or slave.
Each panel has an address on the network.
The addresses do not have to be sequential,
and gaps are allowed.
Up to 31 repeaters can be connected to a panel
via its Isolated RS485 port. These repeaters
can only repeat the panel to which they are
physically connected.
6 - 8 997-291, Version 3.05
November 2010