ZCP

ZCP2
Communications
Protocol
ZITON
ZCP2
Communications Protocol
Document no. GA 280
Issue 2.0
Published 6 May
This document is copyright by Ziton, and all rights are reserved. It may not be photocopied,
translated, or reduced to a machine readable form, in whole or in part, without the prior written
consent of Ziton Ltd. It may not be distributed with changes or omissions which have not been
authorized by Ziton Ltd.
Although Ziton has reviewed and checked this documentation, and believes it to be accurate,
Ziton gives no warranty or representation, either expressed or implied, with respect to accuracy,
completeness, or errors.
For further information, please contact Customer Support at one of the following Ziton Centres.
Ziton Ltd
8 Newmarket Court
Chippenham Drive, Kingston
Milton Keynes MK10 0AQ
United Kingdom
Ziton SA (Pty) Ltd
555 Voortrekker Road
Cape Town
8000
South Africa
Telephone:
Fax:
Email:
Telephone:
Fax:
Email:
+44 (0)1908 281981
+44 (0)1908 282554
[email protected]
+27 (0)21 5066000
+27 (0)21 5066100
[email protected]
ZCP2
Communications Protocol
Table of Contents
Introduction
1.1.
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Application
2.1.
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Connections
3.1.
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Communications Overview
4.1.
4.2.
4.2.1
4.2.2
4.2.3
4.2.4
4.3.
Communications Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZP3 panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZP5 Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time Constaints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Panel Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1
4-2
4-2
4-2
4-4
4-4
4-5
RS232 Control Line
5.1.
5.2.
5.3.
Line Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Flow control: Panel to Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Flow control: Computer to Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Protocol
6.1.
6.2.
Control Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Other Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Blocks
7.1.
7.1.1
7.1.2
7.2.
7.2.1
7.2.2
7.2.3
Block Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Block Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extended Data Block Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Block Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
"Comms Test" Message Panel to Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fire Event Message Panel to Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computer Sends Instruction to Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1
7-2
7-3
7-4
7-5
7-5
7-6
Code Interpretation
8.1.
8.2.
8.3.
8.4.
Defined Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sender/Target I.D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Panel Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checksum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-1
8-1
8-1
8-2
Appendices
9.1.
9.2.
9.3.
9.4.
9.4.1
9.4.2
9.5.
9.6.
9.7.
Priority Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Job Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Info Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
ZP5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
ZP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Info Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Info Codes (Menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Type Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
ZCP2
Communications Protocol
Version 2.01
Section 1
Introduction
Document GA 280.1
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Introduction
1.1.
Introduction
The protocol described in this document is that used in the RS232 and RS422 Communications
Boards, which are optional add-on boards to the Ziton ZP Control Panel.
These units enable bi-directional communication between a ZP Panel and an external computer via
its serial port.
The purpose of this document is to provide sufficient information to enable a suitably skilled
person to design and produce a computer programme for use in the external computer which will
receive data from the fire alarm system for the purpose of integrating the fire system into building
management or other systems, and for display and logging of alarms and control of the system
from the computer.
ZCP2 v2.01 Communications Protocol
GA 280.1 Iss 2.0 (06/06/2000)
Page 1 - 1
1
This page intentionally left blank.
ZCP2
Communications Protocol
Version 2.01
Section 2
Application
GA 280.2
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Application
2.1.
Connectivity
The ZCP-2 protocol is applicable to Ziton ZP fire detection systems. It applies to both stand-alone
single panel systems, or to multi-panel systems, where the panel connected to the PC acts as a
portal to other panels on the network.
Standalone panel
control unit
ZPC2 communication
protocol between
master panel and
external computer
External
computer
Field devices, sensors,
sounders, relays etc.
Example of a Standalone Panel System
ZCP2 v2.01 Communications Protocol
GA 280.2 Iss 2.0 (06/06/2000)
Page 2 - 1
2
ZCP2 Communications Protocol
Application
2.1.
Connectivity (multi-panel systems)
In the case of multi-panel systems the external computer is connected via Serial Port (RS232 or
RS422) to a communications board fitted into a panel setup as a Master Panel. This is illustrated
below.
This panel
configured as
a master panel
ZPC2 communication
between panel and
external computer
External
computer
ZP3 panels
connected in
Peer to Peer
system
Example of a Multi-Panel Peer to Peer System
ZPC2 communication
between master panel
and external computer
Satellite panel
Master panel
External
computer
Satellite panel
Example of a Multi-Panel Master/Slave System
2
Page 2 - 2
ZCP2 v2.01 Communications Protocol
GA 280.2 Iss 2.0 (06/06/2000)
ZCP2
Communications Protocol
Version 2.01
Section 3
Connections
Document GA 280.3
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Connections
3.1.
Connections
This section considers the connections for the cable between the ZP Panel and the external
computer.
Cable Connections
(Ziton RS232 Type A Cable)
1
6
Computer
(9 pin) (25 pin)
ZP3 Panel
(9 pin)
5
9 Pin ‘D’
Connector
9
2
RX
TX
3
2
3
TX
RX
2
3
4
DTR
DTR
6
6
5
GND
GND
5
7
6
DSR
DTR
4
20
7
RTS
CTS
8
5
8
CTS
RTS
7
4
1
6
5
9
9 Pin ‘D’
Connector
1
14
13
25
25 Pin ‘D’
Connector
External
computer
ZP3AB-RS232 Board
ZP3 Panel RS232 Communication Wiring
External
computer
ZP-CB232-2
comms board
Z-CEN
ribbon
cable
1
2
3
4
5
6
7
20
SHIELD
TD
RD
RTS
CTS
DSR
GND
DTR
1
2
3
4
5
6
7
20
1
2
3
4
5
6
7
20
25 pin D type
male connector
SHIELD
TD
RD
RTS
CTS
DSR
GND
DTR
25 pin D type
male connector
1
3
2
7
8
6
5
4
9 pin D type
male connector
ZP5 Panel RS232 Communication Wiring
Normal RS232 protocol is followed.
Control of the communication is in the hands of the ZP5 panel.
ZCP2 v2.01 Communications Protocol
GA 280.3 Iss 2.0 (06/06/2000)
Page 3 - 1
3
ZCP2 Communications Protocol
Connections
3.1.
Connections
External
computer
ZP-CB422-2
comms board
Z-CEN
ribbon
cable
3
4
5
GND
TX+
TX-
3
4
5
3
4
5
GND
TX+
TX-
3
4
5
8
9
RX+
RX-
8
9
8
9
RX+
RX-
8
9
9 pin D type
male connector J1
9 pin D type
male connector J2
RS422 Communication Wiring
Normal RS422 protocol is followed. No RTS or CTS is used.
Control of the communication is in the hands of the ZP5 panel.
3
Page 3 - 2
ZCP2 v2.01 Communications Protocol
GA 280.3 Iss 2.0 (06/06/2000)
ZCP2
Communications Protocol
Version 2.01
Section 4
Communications Overview
GA 280.4
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Communications Overview
4.1.
Communications Initiation
A transfer may be initiated from either the Panel or the External Computer.
Under normal operating conditions the panel will only advise the occurrence of an EVENT apart
from regular polling checks being done to ensure that communication link to the external
computer is still present.
There are six ways in which communication can be initiated:
1.
Periodic Comms Test Message the panel to the computer.
During normal operation, the Panel periodically (approximately once per minute, but always
within two minutes) will initiate a Comms Test Message, provided that no other data
telegrams are available to be sent. The computer must acknowledge within a time-out
interval of approximately 4 seconds. If no acknowledgment is received by the Panel, the
Comms Test Message is repeated up to 10 times, after which a Communications Fault is
registered by the Panel. After the computer boots up, as soon as it receives its first
intelligent message from the panel, the computer should take this as confirmation that
communication has been established.
2.
Panel reports to the Computer on the Occurrence of an Event.
If an 'event' occurs (i.e. fault, fire, evacuate, reset, etc...) the Panel initiates a Status
Report and the External Computer replies with Acknowledge or Negative Acknowledge.
3.
Request by Computer for Information from the Panel
During operation of the computer program, particularly after a period when the computer
has been offline, update information may be required from the Panel. This is accessed by
the computer requesting information from the Panel according to a predetermined Job
Code.
4.
Basic Instructions Communicated from the Computer to the Panel.
Certain basic instructions may be given by the computer to the panel also in the form of a
Job Code. These are sometimes in response to the operation of a key at the computer, the
most common commands being Reset, Acknowledge, and Evacuate.
5.
Request by the Computer for Repeat Information.
If information has been requested by the computer from the panel in the form of a Job
request, and the reply is corrupted or not received (time-out approx. 4 seconds), then the
computer must repeat its request.
6.
Non-acknowledgment of Event Report from Panel to Computer.
If an event report is initiated by the Panel and if a transfer is not positively acknowledged
by the computer (time-out approx. 2 seconds), the report is re-transmitted. If transfer fails
10 successive times, the Panel records a Communications Fault.
ZCP2 v2.01 Communications Protocol
GA 280.4 Iss 2.0 (06/06/2000)
Page 4 - 1
4
ZCP2 Communications Protocol
Communications Overview
4.2.
Timing
The ZP5 and ZP3 panels scan devices on line and process data approximately once every 2
seconds. A period is allocated during each scan for communication with an external computer, so
this occurs approximately once every 2 seconds also.
When this communication period occurs, the panel executes the following sequence of events
depending upon the type of ZP panel, and the type of communications port installed in the panel.
4.2.1
ZP3 Panel
Communications Port: ZP3AB-RS232 (Part No 48601)
This is an optically coupled RS232 board which fits into the ZP3 panel. The ZP3 panel utilises
interrupt driven communications hardware and provides full software buffering which provides
more relaxed timing constraints.
1.
Once every 2 seconds, the panel checks if the computer has a message waiting to be sent
by monitoring the DSR signal (J1 Pin 6). If yes, the panel retrieves the buffered data and
checks for a valid end-of-message character. If the whole message has not arrived within
the 2 second timeout interval, it will be discarded and the computer must re-send it. If DSR
is low, step 3 is entered.
If data has been sent from the computer to the panel, the panel will prepare and send an
ACK or NAK, after monitoring the handshake lines as detailed in section 5.1.
If the panel has a message to send to the computer, it will go through the "panel transmit
to computer routine" detailed in section 5.2. If the transmission of the message takes
longer than the 2 second scan time (i.e. for long multi-telegram messages at slower baud
rates), the transmission is interrupted during the line scan, after which the remaining part of
the message is sent.
If the panel has sent a message to the computer and expects an acknowledgment, then it
will again check the DSR signal to await the reply in the next 2 second time interval
(step 1).
2.
3.
4.
4.2.2
ZP5 Panel
A number of different communications boards are available for the ZP5 panel. The
communication technique for each is described below.
Communication Port: ZP5-RS232 (Buffered)(Part No 16300)
This is an addressable RS232 board for use with the ZP5 Mk4 and ZP5 Mk 5 panels.
1.
2.
Once every 2 seconds, the panel checks if the computer has a message waiting to be sent
by monitoring the DSR signal (J1 Pin 6). If yes, the panel retrieves the buffered data and
checks for a valid end-of-message character. If the whole message has not arrived within
the 2 second timeout interval, it will be discarded and the computer must re-send it. If DSR
is low, step 3 is entered.
If data has been sent from the computer to the panel, the panel will prepare and send an
ACK or NAK, after monitoring the handshake lines as detailed in section 5.1.
4
Page 4 - 2
ZCP2 v2.01 Communications Protocol
GA 280.4 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Communications Overview
4.2.
Timing
4.2.2
ZP5 Panel
3.
4.
If the panel has a message to send to the computer, it will go through the "panel transmit
to computer routine" detailed in section 5.2. If the transmission of the message takes
longer than the 2 second scan time (i.e. for long multi-telegram messages at slower baud
rates), the transmission is interrupted during the line scan, after which the remaining part of
the message is sent.
If the panel has sent a message to the computer and expects an acknowledgment, then it
will again check the DSR signal to await the reply in the next 2 second time interval
(step 1).
Communication Port: ZP5-RS422 (Part No 25601)
This is an addressable RS422 board for use with the ZP5 Mk4 and ZP5 Mk 5 panels. No
handshake lines are available with this card.
1.
2.
3.
4.
Once every 2 seconds, the panel checks if the computer has a message waiting to be sent
by monitoring the FIFO buffer for data received. If data has been received, the data bytes
are appended to the end of a receive buffer, after which the panel checks if a whole
message has been received. If so, the message is then processed. If not, step 3 is entered.
If data has been received from the computer in step 1, the panel will immediately prepare
and send an ACK or NAK message before resuming other panel tasks.
If the panel has a message to send to the computer, it will transmit the information on a
byte-by-byte basis before resuming other panel tasks.
If the panel has sent a message to the computer and expects an acknowledgment, it will
again check the FIFO buffer for a message in the next 2 second time interval (step 1).
Communication Port: ZP5-RS232 (Non-Buffered) (Part No 024700)
This is an addressable board for use with the ZP5 Mk1 and ZP5 Mk2 panels. It is currently
obsolete, but a number of these panels still exist in the field. This card has the tightest timing
constraints since it is not equipped with any data buffering.
1.
2.
3.
4.
Once every 2 seconds, the panel checks if the computer has a message waiting to be sent by
monitoring the DSR signal (J1 Pin 6). If yes, the panel receives a data byte and continues to receive
data until a valid end-of-message character is received or a timeout of approximately 100ms elapses. If
the whole message has not arrived within this 100ms timeout interval, it will be discarded and the
computer must re-send it. If DSR is low, step 3 is entered.
If data has been sent from the computer to the panel, the panel will prepare and immediately send an
ACK or NAK, after monitoring the handshake lines as detailed in section 5.1.
If the panel has a message to send to the computer, it will go through the "panel transmit to computer
routine" detailed in section 5.2.
If the panel has sent a message to the computer and expects an acknowledgment, then it will again
check the DSR signal to await the reply (step 1). Note that in this instance the first byte of the reply
must arrive within approximately 10ms, and the whole acknowledge message must be received with
the 100ms timeout, failing which the panel will re-send the message.
ZCP2 v2.01 Communications Protocol
GA 280.4 Iss 2.0 (06/06/2000)
Page 4 - 3
4
ZCP2 Communications Protocol
Communications Overview
4.2.
Timing
4.2.3
Timing Diagram
4.2.4
Timing Constraints
Timing Constraints by Interface Hardware
Panel / Card Type
Tstart (min) Tstart (max)
0
2s - n
-
2s
ZP5-RS232 (Buffered) (Part No 16300)
0
2s - n
-
2s
5ms
2s - n
-
2s
0
10ms
-
100ms
ZP5-RS232 (Non-Buffered) (Part No 024700)
2.
Tend (max)
ZP3AB-RS232 (Part No 48601)
ZP5-RS422 (Part No 25601) (see note 1)
1.
Tend (min)
RS422 has no handshake lines, however the timings shown apply. The minimum start time
is to allow for settling on the line (if 2-wire RS485 is used) and driver/buffer settling.
Tstart (max) times have a variable component n based upon the message length and the baud
rate.
4
Page 4 - 4
ZCP2 v2.01 Communications Protocol
GA 280.4 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Communications Overview
4.3.
Panel Numbering
Each panel in the system is allocated a unique panel number. In addition, for the purpose of
establishing communications between the Panel and the External Computer, the computer must
assume a number, which may be the same or different to the number of the panel to which it is
connected.
If the computer's number is not set to 1, the panel must learn the number of the computer. The
receipt of an otherwise valid command message from the computer, for example, "Reset Panel",
accomplishes this. In this command, the target I.D. is the panel number whilst the sender I.D. is
the computer's assigned number. On receipt of this message, the panel will assume that the
number of the computer to which it is connected has the number in the sender I.D. field and will
acknowledge accordingly.
Until this transaction has occurred, the panel will assume that the computer's number is 1 and
will continue to attempt to send data messages with the target I.D. number set to 1. Note that
for an acknowledge or negative acknowledge message to be recognized by the panel, the correct
target and sender I.D. numbers (according to the panel) must be used.
ZCP2 v2.01 Communications Protocol
GA 280.4 Iss 2.0 (06/06/2000)
Page 4 - 5
4
This page intentionally left blank.
ZCP2
Communications Protocol
Version 2.01
Section 5
RS232 Control Line
Document GA 280.5
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
RS232 Control Lines
5.1.
Line Definition
Communication takes place using a full-duplex RS232 system with transmit, receive, and 4
control lines and ground.
Connections
Direction
Rx data (RXD)
input
Tx data (TXD)
output
Data Terminal Ready (DTR)
output
Data Set Ready (DSR)
input
Request To Send (RTS)
output
Clear To Send (CTS)
input
Ground
---
Control Line Operations
Description
Panel Actions
Computer Actions
RTS
DTR
RTS
DSR
Panel Busy
OFF
OFF
X
X
Panel Ready to TX
ON
X
X
X
X
X
X
ON
Transmit (P - C)
ON
X
X
ON
Computer Busy
X
X
OFF
OFF
Computer Ready to TX
X
X
ON
X
Panel Ready to RX
X
ON
X
X
Transmit (C - P)
X
ON
ON
X
Computer Ready to RX
X = "Don't care"
Data Format is 7-bit ASCII, 1 stop-bit, even parity.
Baud rate is adjustable as follows:
ZP3 panels: 9600 - 57000 Baud
ZP5 panels: 300 - 9600 Baud
ZCP2 v2.01 Communications Protocol
GA 280.5 Iss 2.0 (06/06/2000)
Page 5 - 1
5
ZCP2 Communications Protocol
RS232 Control Lines
5.2.
Flow Control: Panel to Computer
5.3.
Flow Control: Computer to Panel
5
Page 5 - 2
ZCP2 v2.01 Communications Protocol
GA 280.5 Iss 2.0 (06/06/2000)
ZCP2
Communications Protocol
Version 2.01
Section 6
Protocol
Document GA 280.6
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Protocol
The communication is coded using 7-bit ASCII, in one of two possible ways:
6.1.
Control Codes
Information such as Job Code, Priority, Repetition and Block markers use a single ASCII code to
convey the information. For example, if the instruction from the computer to panel is to instruct
the panel to reset (See Appendix for Job Codes), then a job code "$" is to be sent. Reference to
ASCII tables identifies "$" as decimal ASCII code 36. In 7-bit binary the representation would be
as follows:
64
32
16
8
4
2
1
0
1
0
0
1
0
0
= 36
Block markers use the following decimal ASCII control codes.
Control Code
ASCII Decimal
Abbreviation
Start of Heading
1
SOH
Start of Text
2
STX
End of Text
3
ETX
End of Transmission
4
EOT
Enquiry
5
ENQ
Acknowledge
6
ACK
21
NAK
Negative Acknowledge
ZCP2 v2.01 Communications Protocol
GA 280.6 Iss 2.0 (06/06/2000)
Page 6 - 1
6
ZCP2 Communications Protocol
Protocol
6.2.
Other Data
Other data to be communicated is made up of three representative numerals. For example the
address of a sensor may be communicated as sensor number 102, or the line number as 003.
The data is coded into three consecutive ASCII decimal codes. For example sensor number 102
would be coded as :
1 is represented by ASCII code decimal 49 as follows.
64
32
16
8
4
2
1
0
1
1
0
0
0
1
=49
0 is represented by ASCII code decimal 48 as follows.
64
32
16
8
4
2
1
0
1
1
0
0
1
0
=48
2 is represented by ASCII code decimal 50 as follows.
64
32
16
8
4
2
1
0
1
1
0
0
1
0
6
=50
Page 6 - 2
ZCP2 v2.01 Communications Protocol
GA 280.6 Iss 2.0 (06/06/2000)
ZCP2
Communications Protocol
Version 2.01
Section 7
Blocks
Document GA 280.7
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Blocks
7.1.
Block Structure
More than one event may be reported within a block, with the events separated by control
character ENQ = ASCII Decimal 5. Because of buffer size the maximum transmission size from
panel to computer is limited to 1024 Bytes per telegram transfer.
The following table illustrates the structure of a block.
BLOCK STRUCTURE
Byte
1
JOB
REQUEST
OR
REPLY
Comment
SOH
2-3-4
Sender I.D.
5-6-7
Target I.D.
8
Repetitions
(0..9)
9
Priority
(0..9)
10
STX
11..n
Data Block
n+1
ETX
n+2..n+6
n+7
ACKNOWLEDGE
Description
Checksum
See next page for structure
5 Digits
EOT
1
ACK / NAK
2-3-4
Sender I.D
e.g. “master”
5-6-7
Target I.D.
e.g. “External Computer”
8..12
Checksum
5 Digits
13
ZCP2 v2.01 Communications Protocol
GA 280.7 Iss 2.0 (06/06/2000)
EOT
Page 7 - 1
7
ZCP2 Communications Protocol
Blocks
7.1.
Block Structure
7.1.1
Data Block Structure
The following table illustrates the structure of a block.
DATA BLOCK STRUCTURE
(Byte 11 of Block Structure)
Message Type
Byte
1
INFORMATION
REPLY
COMMAND
REQUEST
7
Comment
Job code
“1”
2-3-4
Status code
e.g. “fire” = 041
5-6-7
Panel code
Panel number
8-9-10
Line code
Loop number
11-12-13
Device code
Device address
14-15-16
Info code
e.g. Zone no. (see 9.6)
17-18-19
Superzone code
Superzone number
20-21-22
Device type code
e.g. Ion detector = 012 (see
9.3)
23-24-25
Date: year
080~099 = 1980~1999
000~079 = 2000~2079
26-27-28
Date: month
001~012
29-30-31
Date: day
001~031
32-33-34
Date: hour
000~023
35-36-37
Date: minute
000~059
38-39-40
Date: second
000~059
41
ENQ or ETX
ENQ = another report follows
ETX = End of data block
42-43-44
Status code
Next event (if one exists)
1
INFORMATION
REQUEST
Description
Job code = E
2-3-4
Line code
5-6-7
Device code
8-9-10
Panel code
11
Not used
12-13-14
Not used
1
Job code
Page 7 - 2
For Individual Status Report
Request
“C”, “D”, “S”, “%”, “&”, “9”
ZCP2 v2.01 Communications Protocol
GA 280.7 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Blocks
7.1.
Block Structure
7.1.2
Extended Data Block Structure
The following table illustrates the extended structure of a block.
EXTENDED DATA BLOCK STRUCTURE
Message Type
COMMAND
REQUEST
(EXTENDED)
REQUEST
ISOLATE
STATUS
TIME SETTING
Byte
Description
1
2-3-4
Job code
Target panel
1
2-3-4
5-6-7
8-9-10
11-12-13
1
2-3-4
5-6-7
Job code
Panel code
Not used
Not used
Not used
Job code
Day of week
Date: year
8-9-10
11-12-13
14-15-16
17-18-19
20-21-22
1
2-3-4
5-6-7
Date: month
Date: day
Time: hour
Time: minute
Time: second
Job code
Panel code
Line code
8-9-10
Device code
DEVICE/ZONE
ISOLATE/
DE-ISOLATE
(DISABLE/
ENABLE)
11-12-13
Panel code
14-15-16
Line code
17-18-19
Device code
20-21-22
Device type
ZCP2 v2.01 Communications Protocol
GA 280.7 Iss 2.0 (06/06/2000)
Page 7 - 3
Comment
“$”, “%”, “&”, “9”
000 = All
Target ID = Master only
001~127 = Satellite only
“I”
Target panel number
“T”
001 = Sunday
080~099 = 1980~1999
000~079 = 2000~2079
001~012
001~031
000~023
000~059
000~059
“J” or “K”
Start panel number
Start loop number
001~008 = loops
009 = Group 9
010 = Group 10
013 = Zone
Start address
Loops = 001~127
Group 9 = 000~128
Group 10 = 000~128
Zones = 001~128
End panel number
(must match start number)
End loop number
001~008 = loops
009 = Group 9
010 = Group 10
013 = Zone
End address
Loops = 001~127
Group 9 = 000~128
Group 10 = 000~128
Zones = 001~128
000 = All (future)
7
ZCP2 Communications Protocol
Blocks
7.2.
Block Examples
The following are typical examples of text connected with information requests and replies.
RS232 relies on handshake lines CTS, RTS, DSR and DTR for communication control, while
RS422 assumes that both parties are always ready to receive.
7.2.1
"Comms Test" message panel to computer
Assume panel No 4 reporting its presence to computer No 1 on a 30-60 second routine. Neither
panel has any event message or instruction in queue.
As above the panel checks whether the computer has anything to say (J1 pin 6 (DSR) high in the
case of RS232). The check is negative.
The "Panel send to computer" routine is then followed (in the case of RS232 the procedure of
paragraph 5.2 is followed: the panel sets high on J1 pin 4. After the panel gets a positive "Clear
to Send (CTS)" response from the computer (high on J1 pin 5) then data is transmitted from the
panel on J1 pin 2). Data is transmitted in the coded format outlined in sections 6 and 7.
The data will read as below:
(SOH) 004 001 1 1 (STX) 0 000 000 000 000 000 000 000 093 007 001 010 040 030 (ETX)
02345 (EOT)
NOTE: In practice the data does not have gaps in the data stream as illustrated above: the gaps
are shown for clarity of illustration.
The data between (SOH) and (STX) indicates address of sending panel (= 004), address of
computer addressed (= 001), repetition number and priority.
Between STX (Start of Text) and ETX (End of Text) the information text is transmitted as
interpreted below.
The message is started with a 0 = Comms Test.
The rest of the data is filled with 0's up to
Date year = 093
Date month = 007
Date day = 001
Time seconds = 030
Between (ETX) and (EOT) a 5 digit checksum is transmitted.
7
Page 7 - 4
ZCP2 v2.01 Communications Protocol
GA 280.7 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Blocks
7.2.
Block Examples
7.2.1
"Comms Test" message panel to computer
On receipt of this communications test message the computer should acknowledge within a few
milliseconds. (In the case of RS232 the computer will take J2 pin 6 high and assuming that the
panel is ready to receive it will respond by taking J1 pin 20 high at which stage the computer
should communicate as per paragraph 5.3).
The acknowledge message data sent from computer to panel should read as below:
(ACK) 001 004 00299 (EOT)
In this example the information between (ACK) and (EOT) can be interpreted as follows:
Sender ID = 001 (computer No)
Target ID = 004 (panel No)
00299 represents the checksum as per paragraph 8.4.
7.2.2
Fire event message panel to computer
Assume panel No 4 reporting a fire event to computer No 1. Assume the panel to be a ZP5 Mk2
panel which does not have superzones. The event relates to a fire detected by an ionization
sensor (type 12) addressed as 32 on line 3, which is zoned to zone 6. The event occurred at 17h
59m 25s on 30th Nov 1989.
As above the panel checks to see whether the computer has anything to say (it checks J1 pin 6
(DSR) in the case of RS232). The check is negative.
The "Panel send to computer" routine as per paragraph 5.2 is then followed (In the case of
RS232, J1 pin 4 is taken high and after the panel gets a positive CTS response from the
computer being a high on J1 pin 5 then data is transmitted from the panel. Data is transmitted in
the coded format outlined in Sections 6 and 7). The data will read as below (without gaps):
(SOH) 004 001 1 1 (STX) 1 041 001 003 032 006 000 012 089011 030 017 059 025 (ETX)
02392 (EOT)
The data between (SOH) and (STX) indicates address of sending panel, address of computer
addressed, repetition number and priority.
Between STX (Start of Text) and ETX (End of Text) the information text is transmitted. In this
example the information can be interpreted as below.
Job Code = 1 (status report)
Status Code = 041 (fire)
Panel Code = 001 (panel No)
Line Code = 003 (line No)
Device Code = 032 (sensor address)
ZCP2 v2.01 Communications Protocol
GA 280.7 Iss 2.0 (06/06/2000)
Page 7 - 5
7
ZCP2 Communications Protocol
Blocks
7.2.
Block Examples
7.2.2
Fire event message panel to computer
Info Code = 006 (zone No)
Superzone code = 000 (No superzoning)
Device Type Code - 012 (Ionization sensor)
Date year = 089
Date month = 011
Date day = 030
Time hours = 017
Time minutes = 059
Time seconds = 025
Between (ETX) and (EOT) a 5 digit checksum is transmitted.
On receipt of this communications test message the computer will immediately reply with an
acknowledge as outlined in at the end of paragraph 4.1.
7.2.3
Computer sends instruction to panel
Assume computer No 1 is connected to panel No 4. The "SILENCE" key is depressed on the
computer. The computer software stores this information and transmits it to the Panel. (In the
case of RS232 it takes J2 pin 20 DTR high to indicate that it has a message to communicate and
at the time of the next scan the panel will detect a high on J1 pin 6 DSR and will respond by
taking J1 pin 20 high DTR. When the computer detects a high on DSR it will transmit its
message)
Data is transmitted in the coded format outlined in Sections 7 and 8. The data will read as below
(without gaps):
(SOH) 001 004 0 1 (STX) % (ETX) 00433 (EOT)
The data between (SOH) and (STX) indicates address of sending computer (=001), address of
panel (= 004), repetition number and priority.
Between STX (Start of Text) and ETX (End of Text) the information text is transmitted. In this
example only a job code instruction % is sent ie Silence.
Note that some of the commands from the computer to the panel have additional characters after
the job code when specific data has to be sent to the panel. An example would be setting the
panels time and date.
7
Page 7 - 6
ZCP2 v2.01 Communications Protocol
GA 280.7 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Blocks
7.2.
Block Examples
7.2.3
Computer sends instruction to panel
Panel acknowledges instruction
On receipt of this communication the panel will acknowledge within a few milliseconds. (In the
case of RS232, the panel will take J1 pin 4 high. Assuming that the computer is ready to receive
it should respond by taking CTS high at which stage the panel will communicate as per paragraph
5.2).
The acknowledge message data sent from panel to computer will read as below:
(ACK) 004 001 00299 (EOT)
In this example the information between (ACK) and (EOT) can be interpreted as below.
Sender ID = 004 (panel number)
Target ID = 001 (computer number)
00299 represents the checksum.
ZCP2 v2.01 Communications Protocol
GA 280.7 Iss 2.0 (06/06/2000)
Page 7 - 7
7
This page intentionally left blank.
ZCP2
Communications Protocol
Version 2.01
Section 8
Code Interpretation
Document GA 280.8
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Code Interpretation
8.1.
Defined Codes
Priority Codes
Section 9.1
Job CodesSee
Section 9.2
Status Codes
Section 9.3
Info Line
Section 9.4
Info Code
Section 9.5
Info Code (Menu access)
Section 9.6
Info Type
Section 9.7
8.2.
Sender/Target I.D.
Sender ID and Target ID address ranges in the block structure shown in Section 7.
External Computer/s
Address Range 001..127
Master/Central Panel/s
Address Range 000, 128..255
Fire Alarm Panel/s
Address Range 001..127
8.3.
Panel Code
See Panel Code in the Data Block Structure shown in Section 7.
Master/Central Panel/s
Address Range 000, 128..255
Fire Alarm Panel/s
Address Range 001..127
ZCP2 v2.01 Communications Protocol
GA 280.8 Iss 2.0 (06/06/2000)
Page 8 - 1
8
ZCP2 Communications Protocol
Code Interpretation
8.4.
Checksum
Sum of bytes from SOH to ETX (inclusive), excluding the checksum itself and EOT. The
checksum is transmitted as five consecutive ASCII characters, representing the decimal digits of
a number from 00000 to 65535 of which the most significant digit is sent first.
Considering the data sent in Section 7.2.2 the checksum is calculated as follows:
Data
SOH
001+
001
048+048+049+
001
048+048+049+
1
049+
1
049+
STX
002+
1
049+
041
048+052+049+
001
048+048+049+
003
048+048+051+
032
048+051+050+
006
048+048+054+
000
048+048+048+
012
048+049+050+
089
048+056+057+
011
048+048+049+
030
048+051+048+
017
048+049+055+
059
048+053+057+
025
048+050+053+
ETX
003
TOTAL = CHECKSUM =
8
Represented by ASCII Code
02389
Page 8 - 2
ZCP2 v2.01 Communications Protocol
GA 280.8 Iss 2.0 (06/06/2000)
ZCP2
Communications Protocol
Version 2.01
Section 9
Appendices
Document GA 280.9
Issue 2.0
06/06/2000
This page intentionally left blank.
ZCP2 Communication Protocol
Appendices
9.1.
Priority Codes
Messages are assigned different priorities as follows:
0 - setup/commissioning
1 - fire/evacuate/gas release
2 - pre-alarm
3 - security
4 - fault
5 - service
Note: this feature is for future use. At present only Priority Code "1" is used.
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 1
9
ZCP2 Communications Protocol
Appendices
9.2.
Job Codes
The following are the job codes transmitted in communication between the external computer (C)
and the panel (P)
Description
Code
Dirn
Comment
Comms Test
0
P-C
Tests communication channel. Computer
replies with an ACK message
All
Status Report
1
P-C
Data event (ie "fire", "fault" etc.) Panel
volunteers these messages as and when
they become available.
All
Service Report
C
C-P
Request for the panel to report all sensors
which require service. Service conditions
are only transmitted by the panel when
requested.
All
4
Pre-Service
Report
D
C-P
Request for the panel to report all sensors
which are in pre-service condition.
Preservice conditions are only transmitted
by the panel when requested.
All
4
Individual Device
Status Report
E
C-P
Request for a report of the status of an
individual sensor
Replies with Status Report telegram with
Job Code = E
All
3
P-C
Panel
Types
Notes
Reset
$
C-P
Instructs a reset of the panel. Equivalent
to pressing the Reset button on the panel
All
4
Silence
%
C-P
Instructs the panel to silence
(acknowledge) all audible alarms.
Equivalent to pressing the Accept (ZP5
Mk4) or Silence Alarms (ZP5 Mk 5) or
Accept (ZP3) button on the panel
All
4
Evacuate
&
C-P
Instructs the panel to activate all audible
alarms which are associated with this
function. Equivalent to pressing the
Evacuate(ZP5 Mk4) or Sound Alarms (ZP5
Mk5 and ZP3) button on the panel.
All
4
Gas Control
Status
9
C-P
Requests a current status report of all gas
control units.
All
4
Isolation Status
I
C-P
Requests a report of all sensors currently
isolated on the panel.
ZP5 Mk2
Master
ZP5 Mk4
ZP5 Mk5
ZP3
5
9
Page 9 - 2
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Appendices
9.2.
Job Codes
Description
Code
Dirn
Comment
Panel
Types
Notes
Time Set
T
C-P
Synchronises the Real Time Clock on the
panel to the PC RTC.
ZP5 Mk2
Master
ZP5 Mk4
ZP5 Mk5
ZP3
6
Isolate
Device/Zone
J
C-P
Request the panel to isolate a sensor or
zone.
ZP5 Mk2
Master
ZP5 Mk4
ZP5 Mk5
ZP3
7
Enable
Device/Zone
K
C-P
Request the panel to enable a sensor or
zone.
ZP5 Mk2
Master
ZP5 Mk4
ZP5 Mk5
ZP3
7
Notes:
1.
On receipt of a Job Code requesting an action or data, the panel replies with an ACK
message before carrying out the request. If data is to be returned in response, the panel
then proceeds to send the requested data.
2.
Certain software versions activate a local panel printer in the event of a communications
failure to the computer. If the panel is operating with it's own printer when it receives a
Job Code from the computer, it will reply with a "P" in place of the Status Report Code.
3.
Request device address and panel number. See section 7.1 "Information Request". The
reply message uses the Status Report structure, with the Job Code set to "E".
4.
These commands are modified by an additional field when used in a Master/Satellite system
to permit an individual panel to be controlled. This additional field follows the job code and
specifies the required panel to be controlled. The field is encoded like the target id. A value
of 0 implies all satellite panels, whilst a value equal to the master panel number implies
master only. If the field is omitted, all panels are affected.
5.
This command is modified by four additional fields to permit specific isolations status to be
requested. The fields are panel number, line or group number, device address and device
type. The fields are encoded as 3 representative numerals as described in section 6.2. At
present only the panel number field is significant, the other fields are set to 000. (Applies
to ZP5 Mk2 Master (FOB and later), ZP5 Mk4, ZP5 Mk5 and ZP3 panels only).
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 3
9
ZCP2 Communications Protocol
Appendices
9.2.
6.
Job Codes
The Time Set command has the following additional fields. (Applies to ZP5 Mk2 Master
(FOB and later), ZP5 Mk4, ZP5 Mk5 and ZP3 panels only).
Day of Week
Year
Month
Day
Hour
Minute
Second
7.
001 = Sunday, 002 = Monday, …. 007 = Saturday
80 to 099 = 1990~1999, 000 to 079 = 2000~2079
001 = January
001 - 031
000 - 023
000 - 059
000 - 059
These commands permit specific sensors or zones to be isolated or enabled. (Applies to
ZP5 Mk2 Master (FOB and later), ZP5 Mk4, ZP5 Mk5 and ZP3 panels only).
Start Panel
Panel number to control
Start Group
001~008=line 1 to 8, 009=group 9, 010=group 10, 013=zone
Start Address 001~127 for lines, 000~128 for group 9 & 10, 001~128 for zones.
End Panel
Set to same as Start Panel
End Group
001~008=line 1 to 8, 009=group 9, 010=group 10, 013=zone
End Point
001~127 for lines, 000~128 for group 9 & 10, 001~128 for zones
Device Type
Not used, set to 000
9
Page 9 - 4
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Appendices
9.3.
Status Codes
The following are the status codes which the panel returns to the external computer to indicate
the occurrence of the events and alarms indicated. The column marked "Device Code" indicates
the interpretation of the Device Type Code field in the Information Reply data block, (Refer to
section 9.7 for device type codes). The column marked "Info Code" indicates the interpretation of
the Info Code (bytes 14-15-16) in the Information Reply data block. (Refer to Section 9.5 for
more discussion of these codes).
Note: Not all of the status codes listed in this table have been implemented in all Ziton panel
products, or in all versions of such panels. Where a status code has not been implemented, the
external computer will not receive a message for that status code.
Device Codes:
D = Device Type
A = User Access ID
Info Codes:
Z
R
C
M
L
=
=
=
=
=
Zone Number
RDU Number
Last Device Number in range of devices
Menu Number (Refer section 9.6)
Menu Level (Maintenance, Configuration, Master)
Code
Status Description
Event Type
0
1
Device Failed Test
Device Disabled
Device fault
Device disable /
Zone partial disable
Device fault
Device fault
Device fault
Device fault
Device fault
Device fault
Device fault
Device fault
Device fault
Device fault
Device fault (older
systems only)
2
3
4
5
6
7
8
9
10
11
12
Maintenance Required : idle too high
Detector Sensing Faulty : idle too low
Device communications faulty
Open Circuit Fault
Device Short Circuit
Device Unaccepted
Line Relay failed to trigger or fault
Detector Removed from Base
Incorrect Device Type
Device Offine/No Power
Start of Units Offline
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 5
Device
Code
D
D
Info
Code
Z
Z
D
D
D
D
D
D
D
D
D
D
D
Z
Z
Z
Z
Z
Z
Z
Z
Z
Z
Z
9
ZCP2 Communications Protocol
Appendices
9.3.
Status Codes
Code
Status Description
Event Type
13
End of Units Offline
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Detection loop fault
Earth leakage fault
Alarm Fault
Manual Callpoint Loop
Halon Detonator Loop
Halon Bell Fault
T-Bar switchover recommended
No Sensors
External Line Fault
Fire Station Fault
RAM Fault
Power Fault
Battery Fault
Charger Fault
RAM Backup Battery Voltage Low
Panel Offline
Panel Online
Zone Disabled
Zone Enabled
Bell Fault
Door Open
RS422 Comms Failed
Panel Reset
Panel Alarms Accepted
Panel Sound Alarms
Printer Options Set
41
42
43
44
Fire Alarm
Pre-Alarm
Service Required
Alarm / Trigger
45
46
Initialising
Accepting
Device fault (older systems
only)
Panel fault
Panel fault
Panel fault
Panel fault (ZP4 only)
Panel fault (ZP4 only)
Panel fault (ZP4 only)
Panel status
Panel fault
Panel fault
Panel fault
Panel fault
Panel fault
Panel fault
Panel fault
Panel fault
Satellite panel offline
Satellite panel online
Zone fully disabled
Zone fully restored
Panel fault
not used - ignore
not used - ignore
User action response
User action response
User action response
User action response
Panel alarms/faults cleared
after reset
Alarm event
Alarm event
Device dirty
Alarm event (e.g. switch
interface)
internal only - ignore
internal only - ignore
9
Page 9 - 6
Device
Code
D
Info
Code
Z
-
Z
Z
-
D
D
D
D
Z
Z
Z
Z
-
-
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Appendices
9.3.
Code
Status Codes
Status Description
Event Type
47
48
Calibrating
Service Done
49
50
51
52
53
54
55
56
57
Testing
Framing
Overrun
Parity
Device Enabled
Panel Data Accessed/Changed
Spare
Spare
Control Switch Activated
58
Control Switch De-Activated
59
60
61
62
63
64
65
66
67
68
69
70
RDU Online
RDU Offline
RDU Alarm Fault
RDU Battery Fault
RDU Mains Fault
Spare
Spare
Memory R/W fault
Checksum Fault
Gas Dropped
Gas Unit General Fault
Door Error
71
72
73
Gas Unit Power Fault
Manual Mode
Auto Mode
74
75
76
77
78
79
Gas Unit Locked Off
Gas Relay Activated
Gas Unit Status Normal
Spare
Stack Fault
Ext. Computer Offline
internal only - ignore
Device idle count normalized
after cleaning
internal only - ignore
internal only - ignore
internal only - ignore
internal only - ignore
Disablement restored
User action response
spare - ignore
spare - ignore
Alarm event (e.g. Control
interface)
Alarm event (e.g. Control
interface)
RDU comms restored
RDU comms failed
Panel fault - RDU
Panel fault - RDU
Panel fault - RDU
spare - ignore
spare - ignore
Panel fault
Panel fault
Alarm event - Gas released
GCU fault alarm
door open in Auto mode or
door closed in Manual mode
GCU fault alarm
Gas control by GCU callpoint
Gas control by double-knock
sensors
GCU disabled by key
GCU relay triggered
GCU condition okay
spare - ignore
Panel fault
Panel fault
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 7
Device
Code
D
Info
Code
D
D
D
D
D
D
D
D
Z
D
D
D
-
Z
Z
Z
-
9
ZCP2 Communications Protocol
Appendices
9.3.
Status Codes
Code
Status Description
Event Type
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
Faulty Z-Input
Input On
Input Off
Offline Board
Test Finished
System Fault AGV
Dual Monitored Loop
Output Cancelled
Spare
Spare
High Sensitivity Smoke Fault
Text Area Full
Security Switch Activated
Spare
Lower Service Band
Sounders Silenced
Detector Fault Restored
System Fault Restored
EPROM Changed
I/O Disabled
I/O Enabled
Comms 2 Ext. Computer Responding
Addressable Comms Board Offline
Addressable Comms Board Online
Night Mode
Day Mode
Standard Mode
Line Sounder Unit Fault
Line Sounder Unit Ext. Charger Fault
Line Sounder Unit Ext. Supply Fault
Output Triggered
Watchdog
Menu Access Security Code
EEPROM Write Fault
Sounder Delay Start Timeout
Spare
Spare
Master No Slaves Online
Slave: Address Group Fault
Panel fault
Panel input switch
Panel input switch
Panel fault
internal only - ignore
Panel fault
Panel fault
Panel output relay
spare - ignore
spare - ignore
Device fault
obsolete
Security Alarm event
spare - ignore
Device pre-service
User action response
Device fault restored
Panel fault restored
Panel status
I/O device disablement
I/O device restored
Panel fault restored
Panel fault
Panel fault restored
Panel Status
Panel Status
Panel Status
Device fault
Device fault
Device fault
Relay output triggered
Panel Fault
Panel Status
Panel fault
Device Status
spare - ignore
spare - ignore
Panel fault
Device fault
9
Page 9 - 8
Device
Code
D
D
D
D
D
D
D
A
-
Info
Code
C
C
Z
Z
Z
Z
Z
Z
Z
L
-
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Appendices
9.3.
Status Codes
Code
Status Description
Event Type
119
120
121
122
123
124
125
126
127
128
129
130
131
132
High Sensitivity Smoke Pre-Alarm
Silence Disabled
Sounders Disabled
Comms Link Down/Modem No Carrier
Comms Link Up
Common Disable
Fire Station Disable
GCU Disable
Common Enable
Device Tamper (Radio Device)
Device Battery Low (Radio Device)
Processor Fault
Double Address Fault
Hardware Report (spurious interrupt)
Alarm event
Silence button disabled
Sounder button disabled
Panel fault
Panel fault restored
General isolate/enable
RMC relay disabled
GCU disablement
General deisolate/enable
Radio device fault
Radio device fault
Ancillary processors
Panel fault
Panel fault (ZP3 only)
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 9
Device
Code
D
-
Info
Code
Z
-
9
ZCP2 Communications Protocol
Appendices
9.4.
Info Line
These codes are used during both job requests and job replies to provide necessary information
which is not specified elsewhere in the protocol.
9.4.1
ZP5
CODE
000
001
002
003
004
005
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
9
INFORMATION
undefined
line 1 (of identified panel)
line 2 (of identified panel)
line 3 (of identified panel)
line 4 (of identified panel)
line 5 (of identified panel)
line 6 (of identified panel)
line 7 (of identified panel)
line 8 (of identified panel)
Z-Bus group 9 output triggered
Z-Bus group 10 output triggered
(future)
Mapped internal node triggered
Zone triggered
(future)
Central Panel: Satellite Common Alarm
(future)
(future)
Z-Input from input board triggered
(future)
Output to isolate zone triggered
Output to extend zone "Day Mode" triggered
Zone changed from night to day operation
External (interpanel) node output triggered
External (interpanel) node input triggered
Page 9 - 10
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Appendices
9.4.
Info Line
9.4.2
ZP3
CODE
000
001
002
003
004
005
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
INFORMATION
System/Panel internal event
line 1 (of identified panel)
line 2 (of identified panel)
line 3 (of identified panel)
line 4 (of identified panel)
Reserved
Reserved
Reserved
Reserved
System Bus group 9 outputs
I/O Bus group 10 inputs/outputs
Not used
Not used
Zone triggered
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 11
9
ZCP2 Communications Protocol
Appendices
9.5.
Info Codes
These codes are used during both job requests and job replies to provide necessary information
which is not specified elsewhere in the protocol. The interpretation of the code is dependent upon
the status of the code being described.
INFO CODE NOTATION
IN SECTION 9.3
Z
R
C
M
9
INTERPRETATION OF
INFO CODE
The Info Code represents the Zone number applicable to the
device
The Info Code represents the RDU number applicable to the
signal
This is used where a consecutive range of devices are involved.
The Device Code gives the first device involved and the Info
Code gives the last device involved
Indicates access to a menu. The Info Code interpretation is as per
section 9.6
Page 9 - 12
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Appendices
9.6.
Info Codes (Menu)
The interpretation of the INFO CODE when applicable to menu access (Notated "M" in Section
9.3) is as follows:
Code
54
55
57
58
60
61
63
64
65
66
68
69
71
72
73
82
86
88
89
91
99
105
106
121
122
125
129
133
134
137
138
139
140
141
142
143
144
147
153
Designation
Smoke Alert Enabled
Smoke Alert Delay
Gas Status Check
Setup Controls
Device Disable/Enable
Remote Disable/Enable
Sensitivity Set
Time Date Set
Accept Devices
Calibrate Devices
Set Net Comms Mode
Set Printer Options
Setup Line Isolators
Setup Service Configuration
Load Device Messages
Panel Super-zoning
Panel Zoning
I/O Mapping Inputs
I/O Mapping Outputs
Zone Disable
Set Access Codes
End Print Archives
Aborted Printing
Clear Custom Messages
Edit Custom Messages
Watchdog Access
Set Device A.V.F.
Set Comms Option
Set A.V.F. Configuration
Map Remote Sounders
Access Day/Night Configuration
Day/Night/Auto switch
Access: day-time table
Access: D/N mode/delay
Additional Investigation Time
Pre-Service Report
Checked EPROM Checksums
Self Test Selection
Output Disable
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 13
9
ZCP2 Communications Protocol
Appendices
9.6.
Info Codes (Menu)
Code
154
155
161
162
163
164
165
166
169
170
171
172
173
175
176
178
9
Designation
Edit Access Controls
Configure Zone Labels
Day Delay Configuration
RMC Relay Configuration
Sounders Silenced
Sensitivity Set
Configured Relays
Configure Disable
Address Group Verification Configure
Address Group Verification Record
Address Group Verification Test
Controls Select
Set Timeout Silence
Display Archives
Print Summary
Network Comms Selected
Page 9 - 14
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
ZCP2 Communication Protocol
Appendices
9.7.
Type Codes
These codes are used to identify sensor or other line device types. Note that not all Ziton Panel
products and also not all Panels versions support all listed device type codes.
Code
000
012
013
014
015
016
022
023
024
032
033
035
041
042
044
045
047
052
053
055
062
064
416
421
422
423
424
425
426
427
437
655
656
665
666
667
Description
Null Device
Ionization
Heat Fixed Temperature
Heat Rate of Rise
Optical Smoke
Dual Optic/Heat
Call-point
Interface Sprinkler
Interface General
Interface Conventional
High Sensitivity Aspirating Smoke Detector
Interface Conventional 4
ZP755 Line Sounder
Addressable Relay
Gas Control Unit
Sounder Driver
ZP754 Line Sounder
Interface Non Fire
Interface Control Switch
Addressable LED
Security Interface Latching
Security I/F Non-Latch
Paradigm Multi-sensor
Radio Base
Radio Optic/Heat
Radio Heat
Radio Call-point
Radio Optic
Radio Aux. Interface
Radio I/O Unit
Radio I/O Group
Ionization (Ex)
Heat (Ex)
Call-point (Ex)
Interface Fire (Ex)
Interface Non-Fire (Ex)
ZCP2 v2.01 Communications Protocol
GA 280.9 Iss 2.0 (06/06/2000)
Page 9 - 15
Type Code
2-12
2-13
2-14
2-15
2-16
2-22
2-23
2-24
2-32
2-33
2-35
2-41
2-42
2-44
2-45
2-47
2-52
2-53
2-55
2-62
2-64
4-16
4-21
4-22
4-23
4-24
4-25
4-26
4-27
4-37
6-55
6-56
6-65
6-66
6-67
Product Code
ZP710
ZP720
ZP725
ZP730
ZP732
ZP785
ZP540-3-23
ZP540-3-24
ZP570
ZP740ST
ZP5-574
ZP755
ZP550
ZP5-GCU
ZP752
ZP754
ZP540-3-52
ZP540-3-53
ZP753
ZP540-3-62
ZP540-3-64
ZP832
ZR400
ZR432
ZR420
ZR485
ZR430
ZP470
ZR454
I/O Group
ZP710Ex
ZP720Ex
ZP786Ex
ZP740Ex(F)
ZP740Ex(NF)
9

Download Report