Tyco RDU Mk2, Инструкция по установке и программированию, Страница: 69 / 178

Document No: LT0499 RDU Mk2 Installation & Programming Manual
Programming Part 1
Issue 1.02 8 April 2015 Page 6-15
6.4.1.2 Mimic
When mimic mode is enabled, the RDU never transmits on the RZDU bus and the RZDU
address assigned to it is "don't care". This might be useful if there are more than eight
devices connected to the RZDU bus. When mimic mode is enabled, the RDU cannot send
zone commands to the FIP, nor does it send fault indications to the FIP and the FIP does not
monitor the RDU. If an RDU with mimic mode enabled is powered off or communication with
the FIP is not working, there is no fault indication at the FIP. If the RDU loses
communication with the FIP, the RDU still indicates a system fault and turns its buzzer on (if
programmed to).
When mimic mode is disabled, the RDU must be assigned a unique address which it uses to
send commands and status to the FIP. The FIP monitors responses from each programmed
RDU and if an RDU stops responding, a fault is signalled.
6.4.1.3 Address
The RDU address can be set to a value from 1 to 8. The address must match the values
assigned at the FIP for the devices that are present on the RZDU bus. Each device on the
RZDU bus must be assigned a unique address, other than devices which don't reply, such
as an RDU in mimic mode. With some older FIPs, RZDU addresses must start at address
one and be assigned consecutively with no gaps.
6.4.1.4 Protocol
The RDU can be programmed with the protocol type to be used in communicating with the
FIP. There are three protocol types which can be selected - non-LCD, LCD-A, LCD-B. The
default is LCD-A, and the RDU can also operate with the "old style" LED only protocol (non-
LCD). With Non-LCD protocol the RDU has less capability than with LCD-A or LCD-B - it
does not receive "FFCIF alarm list" LCD type events from the FIP, and zone reset, isolate
and test commands cannot be done at the RDU. LCD-B protocol is a slight improvement
from LCD-A protocol and allows some more specific fault information to be sent to the FIP,
and for New Zealand operation it allows the state of the Building Services Restore input to
be sent to the FIP. It is currently not supported by any panels.
Not all types and versions of FIP and RDU currently in use allow all three types of protocol.
The selection of which protocol type to use depends on what choice of protocol is available
at the FIP and ALL of the RDUs connected to it since they must all use the same protocol
type, unless the FIP has the capability of programming the protocol type specifically per
each RDU connected. For some FIPs, the choice of protocol type is given as Non-LCD or
LCD (e.g., F4000 and F3200) - for these FIPs, "LCD" is the same as LCD-A protocol at the
RDU.
F4000 V2.00 onwards allow LCD or Non-LCD protocol. F4000 versions before V2.00 allow
only non-LCD protocol. F3200 V2.00 onwards allow non-LCD, LCD-A or LCD-B. F3200
versions before V2.00 allow non-LCD or LCD (LCD-A).
When the protocol type is Non-LCD, the RDU will still generate LCD FFCIF alarm list type
events when a zone goes into alarm, t the event description on the LCD will not have quite
the same information as the event at the FIP.