GE Security Automation Module Protocol
GE Security Automation Module Protocol
TABLE OF CONTENTS
Revision History 1
Definition of Terms (used in the context of this document) 2
Overview 3
Configuration / Physical Interface 4
Configuring the Automation Module 4
Serial Port LED Behavior 4
Serial Port Physical Interface 4
Serial Port Protocol 5
Start of Message 5
Data 5
Checksum 5
ACK (06h) (Acknowledge) 6
NAK (15h) (Negative Acknowledge) 6
Communication Rules for Behavior 6
Automation Module, Implementation Perspective 7
Outbound Messages 7
Inbound Messages 7
Action Request Confirmation 8
Panel and Automation Device Interaction Example 9
Decimal to Hex to ASCII Conversion List 10
Panel to Automation Commands 12
COMMAND: Panel Type (01h) 12
COMMAND: Automation Event Lost (02h) (CONCORD ONLY) 13
COMMAND: Clear Automation Dynamic Image (20h) 13
COMMAND: Zone Status (21h) 14
COMMAND: Arming Level (22h/01h) 15
COMMAND: Entry/Exit Delay (22h/03h) 16
i
COMMAND: Alarm/Trouble (22h/02h) 17
Alarm (General Type = 1) 18
Alarm Cancel (General Type = 2) 18
Alarm Restoral (General Type = 3) 18
Fire Trouble (General Type = 4) 19
Fire Trouble Restoral (General Type = 5) 19
Non-Fire Trouble (General Type = 6) 19
Non-Fire Trouble Restoral (General Type = 7) 19
Bypass (General Type = 8) 19
Unbypass (General Type = 9) 19
Opening (General Type = 10) 20
Closing (General Type = 11) 20
Partition Configuration Change (General Type = 12) 20
Partition Event (General Type = 13) 21
Partition Test (General Type = 14) 21
System Trouble (General Type = 15) 21
System Trouble Restoral (General Type = 16) 22
System Configuration Change (General Type = 17) 23
System Event (General Type = 18) 23
COMMAND: Siren Setup (22h/04h) 24
COMMAND: Siren Synchronize (22h/05h) 24
COMMAND: Siren Go (22h/06h) 24
COMMAND: Touchpad Display (22h/09h) 25
Text Token Table 26
COMMAND: Siren Stop (22h/0Bh) 29
COMMAND: Feature State (22h/0Ch) 29
COMMAND: Temperature (22h/0Dh) 30
COMMAND: Time and Date (22h/0Eh) 30
COMMAND: Lights State Command (23h/01h) 31
COMMAND: User Lights Command (23h/02h) 31
COMMAND: Keyfob Command (23h/03h) 32
AUTOMATION TO PANEL COMMANDS 33
COMMAND: Full Equipment List Request (02h) 33
COMMAND: Single Equipment List Request (02h/[Equipment List Parameter]) 33
COMMAND: Send Equipment List - Zone Data (03h) 33
COMMAND: Send Equipment List - Partition Data (04h) 35
COMMAND: Send Equipment List - SuperBus Device Data (05h) 36
COMMAND: Send Equipment List - Output Data (07h) 38
COMMAND: Send Equipment List - User Data (09h) 39
COMMAND: Send Equipment List - Schedule Data (0Ah) 40
COMMAND: Send Equipment List – Scheduled Event Data (0Bh) 41
COMMAND: Send Equipment List – Light to Sensor Attachment (0Ch) 42
COMMAND: Equipment List Complete (08h) 42
COMMAND: Dynamic Data Refresh Request (20h) 43
COMMAND: Keypress (40h) 43
COMMAND: Reserved 45
ii
Revision History
Date Who Changed Description
Changed
5.23.2000 Rob H, Terry T, First Revision
Mark H, Dave
M
7.20.2000 Kris S Concord updates
9.12.2000 Kris S Updated for Qubit_b Concord software
10.5.2000 Kris S Updated for Con25_P1 software
10.26.2000 Kris S Updated for Con25_P3 software
10.31.2000 Kris S Added checksum byte
11.16.2000 Kris S Added backspace token to touchpad display table,
communication protocol section, and table of contents
12.06.2000 Kris S Updated for Con25a software and PAM 0339 software
02.05.2001 Mark H Advent details added
03.07.2001 Kris S Updated for PAM 0341 software
04.13.2001 Kris S Added notes for Concord maximum inbound packet size
04.19.2001 Tim B Added notes for embedded ACK/NAK in Outbound
Messages, Clarified Communication Rules for Behavior
05.07.2001 Tim B Clarified that message Zone Status (21h) is sent for open
(non-restored) zones in response to a Dynamic Data Refresh
request.
02.11.2002 Kris S Added changes for Concord 2.6 and removed Concord
Express definitions.
05.07.2002 Kris S Added changes for Concord 2.53
? ? ?
03.03.2005 Tim B Removed Concord 2.x, generalized into Advent and
Concord, changed to GE document, added reserved
commands
05.10.05 Bryan P Removed reference to the Automation Monitor Program
(Automon). We cannot support customer use of this
program. Also removed references to PHAST, which is no
longer supported
12.15.05 Bryan P Removed “Confidential” from footer
1
Definition of Terms (used in the context of this document)
Term Definition
Automation An aftermarket product intended to monitor/control a Panel.
Device
Automation Interlogix SuperBus 2000 peripheral which provides a gateway between the Panel
Module and the Automation Device.
Autonomous A device performing an action while not under direct control of another device.
The Automation Module does something on its own – not under direct control of
the Panel.
Full Duplex Permits transmission of data in two directions, both ends can transmit at the same
time, and the receiver at the opposite end will not have any interference or
distortion due to its own transmissions.
Host Processor The PIC16C77 microcontroller found on the Automation Module. It is in a 44-pin
PLCC (Plastic Leaded Chip Carrier).
Inbound Message originating at the Automation Device and sent to the Panel.
Inbound Buffer Buffers incoming messages, the size is 82 ASCII characters. See the section titled
"Automation Module, Implementation Perspective" for more information.
Last Index Indicates the number of bytes following the last index byte. The last index is equal
to the byte count minus one (in a three-element array, the last index is two).
Outbound Message originating at the Panel and sent to the Automation Device.
Outbound Buffer Buffers outgoing messages, the size is 82 binary bytes. See the section titled
“Automation Module, Implementation Perspective for more information.
Panel Interlogix Advent, Concord or future alarm Panel.
Physical The physical interface between the Automation Module and the Automation
Interface Device: is either RS-232 or PHAST. The physical interface between the Automation
Module and the Panel is RS-485.
UART Processor The PIC16C63 microcontroller found on the Automation Module. It is in a 28-pin
DIP (Dual In-line Package).
List of Acronyms
Acronym Definition
ACK ASCII Acknowledge character (control-F), 06h.
LF ASCII Linefeed character (control-J), 0Ah.
NAK ASCII Negative Acknowledge character (control-O), 15h.
2
Overview
The purpose of this document is to explain the ‘how’ of the Panel, Automation Module and
Automation Device Interaction and provide a list of supported commands.
Interlogix strongly recommends that -- prior to writing any software -- serial port Automation
Developers familiarize themselves with the Automation Protocol by reading this document
completely, then interacting with the Panel via a terminal emulation application, or serial
data monitor to observe outbound message formatting. Note that each outbound message
will be retransmitted until it is acknowledged.
Additionally, an almost indispensable tool for software development is a serial data line monitor (either stand-
alone, or PC-based.)
3
Configuration / Physical Interface
The Automation port supports either the proprietary PHAST interface or a standard 3-wire RS-
232 interface. From the Panel's point of view, the physical interface is unknown, both are
simply "Automation."
4
Serial Port Protocol
The message consists of four parts sent in the following order:
1. Start of Message
2. Data
3. Checksum
4. Acknowledge or Negative Acknowledge
Start of Message
A single Line Feed (0Ah) is used to signal the start of a message. The line feed character
should reset the Host Processor's message parsing pointer as it always indicates the start of a
new message.
Data
An 8-bit binary value is sent as two upper-case ASCII digits (‘0’...’9’, ‘A’...’F’).
Example:
To expand the 8 bit binary value 3Ch into its ASCII representation:
NOTE: Control characters (ACK, NAK, and LF) are sent as a single byte, and not converted
into ASCII pairs.
The use of control characters and ASCII data permits software flow control. Only sixteen ASCII
characters '0'...'9', 'A'...'F' are used to transfer "data." If binary data were transmitted, the use
of hardware flow control, timing specifications, or a byte-stuffing scheme would be required.
The control characters and ASCII data protocol was chosen because its advantage in
simplicity outweighs the slight loss of efficiency.
Checksum
A checksum is appended to each message. It is the sum of the binary interpretation of all the
preceding bytes in the message (control characters and ignored characters excluded),
taken modulus 256. The checksum is computed on the 8-bit binary representation of the
ASCII pair, rather than the values of the individual ASCII characters. An example checksum
calculation, with an overflow, is shown below:
Example
Calculate the checksum for the message: 03h (Last Index), 7Ah, character, and 9Bh. The Last
Index is three because the message will contain three bytes: data byte: 7Ah, data byte: 9Bh,
and the checksum byte. The checksum calculation is a byte wide, sum of the binary data
(excluding the control characters).
5
Therefore:
Sent autonomously by the Automation Module to indicate that the message was well formed
(enough bytes were received, and the checksum was correct) and that the message has
been successfully transmitted to the panel. An ACK sent by the Automation Module does not
mean the Panel understood/acted on the message.
An ACK may be issued asynchronously with regard to any Outbound message in progress.
This means that an ACK may occur in the middle of an Outbound message.
A NAK may be issued asynchronously with regard to any Outbound message in progress. This
means that a NAK may occur in the middle of an Outbound message.
6
• If an ACK or a NAK is not received by the Automation Device within 500ms of
sending an Inbound message, something has gone awry. The proper error recovery is
to re-send the original Inbound message beginning with the CR/LF.
Note: An ACK or NAK may be issued asynchronously with regard to any Outbound
message in progress. This means that an ACK or NAK may occur in the middle of an
Outbound message.
Note: The automation module will not process Incoming messages until a prior message
has been responded to.
Outbound Messages
Outbound message processing is handled by the UART processor in real-time sending
characters passed to it by the Host.
The firmware allows the Automation Device to request the last Outbound message be re-
sent. The Automation Module handles this request autonomously.
One of the following three things must occur for each Outbound message:
1. ACK. The Automation Device receives a well-formed message and sends the
acknowledge character to the Automation Module.
2. NAK. The Automation Device detects a discrepancy in the message and asks for the
message to be re-transmitted by sending the negative acknowledge character.
3. Timeout. If the Automation Device sends neither an ACK nor a NAK within 2 seconds, the
Automation Module considers this to be an implied NAK and will re-transmit the
message.
Inbound Messages
The Automation Module has a 64 character buffer for the binary interpretation of Inbound
messages from the Automation Device. The LF and checksum are not stored. This means
that the maximum byte count for an inbound message is 64 (40h). For example, the largest
keypress command that can be sent is: 40 40 01 00 [60 keys] [CS]
NOTE: The maximum byte count for an inbound message to a Concord panel is limited by the
panel’s internal buffer size. The maximum byte count sent is limited to 58 (3Ah). For example,
the largest keypress command that can be sent to a Concord panel is: 3A 40 01 00 [54 keys]
[CS].
7
Action Request Confirmation
The Automation Device will receive feedback from messages sent to the Panel, but the
Automation Device may have to request status updates to confirm that a requested action
was completed.
Example
The user attempts to arm the security system using an Automation Device
1. The Automation Device sends a message to the Automation Module to arm the Panel.
2. The Automation Module will perform the following tasks:
a. Receives the message
b. Verifies the message is correct
c. Sends the message in Superbus 2000 format to the Panel
d. Sends an ACK the Automation Device
3. The Panel interprets the arm the system request based on the following conditions:
a. If the security system has open sensor(s) or other system troubles:
i. The system will not arm
ii. Message/s describing the open sensor(s) or other system troubles will be sent to
the Automation Device
b. If the security system does not have open sensor(s) or system troubles
i. The system will arm
ii. Message/s describing arming level will be sent to the Automation Device
8
Panel and Automation Device Interaction Example
This example shows the Equipment List Request command and how it would appear to a serial port Automation
Device and the Panel.
Example:
Send the Equipment List Request command from the Automation Device to the Panel:
1. Send the Start of Message information to the Automation Module, ASCII Linefeed character (control-J), 0Ah
1. Send the Last Index, 02h
a. Calculate Last Index. The Last Index is the remaining number of bytes (ASCII pairs) to follow in the
message. Therefore; the Last Index is 02h (data byte, 02h and the checksum, 04h).
b. High nybble of the Last Index (30h) is sent to the Automation Module.
c. Low nybble of the Last Index (32h) is sent to the Automation Module.
2. Send the data byte, 02h
a. High nybble of the data byte (30h) is sent to the Automation Module.
b. Low nybble of the data byte (32h) is sent to the Automation Module.
3. Send the checksum, 04h
a. Calculate the checksum. The checksum calculation is a byte wide, sum of the hexadecimal
representation of each ASCII pair (excluding the control characters).
Checksum High Nybble Low Nybble Hexadecimal
calculation: Representation
Last Index ‘0’ ‘2’ 02h
Data ‘0’ ‘2’ + 02h
Checksum (one ‘0’ ‘4’ 04h
byte wide)
b. High nybble of the checksum (30h) is sent to the Automation Module.
c. Low nybble of the checksum (34h) is sent to the Automation Module.
The 02h 02h 04h message was received by the Automation Module as shown below:
NOTE: The line feed (LF) character MUST precede the message.
4. The Automation Module has received the expected number of message bytes. The Automation Module will
decode the ASCII text into the original hexadecimal message and verify the checksum. Then the Automation
Module will send the message to the Panel and ACK the Automation Device.
5. The Panel receives an Equipment List Request from the Automation Module wrapped in the SuperBus 2000
protocol.
6. The Panel will send the Equipment List to the Automation Module, which passes the information to the
Automation Device.
9
Decimal to Hex to ASCII Conversion List
10
46 2E . 110 6E n
47 2F / 111 6F o
48 30 0 112 70 p
49 31 1 113 71 q
50 32 2 114 72 r
51 33 3 115 73 s
52 34 4 116 74 t
53 35 5 117 75 u
54 36 6 118 76 v
55 37 7 119 77 w
56 38 8 120 78 x
57 39 9 121 79 y
58 3A : 122 7A z
59 3B ; 123 7B {
60 3C < 124 7C |
61 3D = 125 7D }
62 3E > 126 7E ~
63 3F ? 127 7F DEL
11
Panel to Automation Commands
This section outlines the commands that are sent from the security panel to the Automation Module.
Format: 0Bh 01h [PT] [HRh] [HRl] [SRh] [SRl] [SN4] [SN3] [SN2] [SN1] [CS]
1
xxyy=4-digit hardware revision defined as xx=numeric representation of board revision letter a-z; (ex.
xx=01=a, 00<xx<27,), yy=the board revision number; (yy=00-09). Example: revision ‘C2’ would equate to
xxyy=’0302’
2
4-digit firmware set which includes all finished microcontrollers and eeproms
3
7-digit board serial number indicating serially the number of the manufactured panel in a product code family
12
COMMAND: Automation Event Lost (02h) (CONCORD ONLY)
This command is sent if the panel’s automation buffer has overflowed resulting in the loss of
system events. This command should result in a Dynamic Data Refresh and Full Equipment List
request from the Automation Device.
4
This is done instead of sending a message for each item as it is changed (user code deleted, etc.). The
Automation Device should perform an Equipment List and Refresh when the Clear Image command is received.
13
COMMAND: Zone Status (21h)
This command is sent whenever there is a change in zone state (e.g. trip, restore, alarm,
cancel, trouble, restoral, bypass, unbypass). Also, if the Automation Module requests a
Dynamic Data Refresh Request this command will be sent for each zone that is not normal
(i.e. any zone that is open (non restored), in alarm, troubled or bypassed). The remote device
should assume that all zones are normal unless told otherwise.
5
Partition number is 1-8 if partitions are enabled, 0 if areas are enabled.
6
Could go to 8 in later revisions.
7
Area number is 1-8 if areas are enabled, 0 if partitions are enabled.
14
COMMAND: Arming Level (22h/01h)
This command is sent whenever there is a change in the arming level. Also, if the Automation
Module requests a Dynamic Data Refresh Request this command will be sent for each
partition that is enabled.
Format: 08h 22h 01h [PN] [AN] [UNh] [UNl] [AL] [CS]
Note: For user number, UNh byte is 00 and UNl is the user number as listed in the table above.
For a keyfob, UNh is 01 and UNl is the zone number for the keyfob.
* First regular user code for 4 partition versions of Advent is 6, for 8 partition versions is 10.
15
COMMAND: Entry/Exit Delay (22h/03h)
This command is sent whenever an entry or exit delay is started or ended.
Format: 08h 22h 03h [PN] [AN] [DF] [DTh] [DTl] [CS]
16
COMMAND: Alarm/Trouble (22h/02h)
This command is sent to identify alarm and trouble conditions as well as several other system
events. Events are specified by three numbers; General Type, Specific Type, and Event
Specific Data. The lists below show all the events, categorized by General Type.
Format: 0Dh 22h 02h [PN] [AN] [ST] [SNh] [SNm] [SNl] [GT] [ST] [ESh] [ESl] [CS]
17
Each list below contains the Specific Type codes for the General Type shown in the heading. For
example, if GT = 1, and ST = 3, the event is a Police Alarm. Most events do not use the Event Specific
Data byte. The underlined events apply only to Advent. For definition of user number, see description in
18
COMMAND: Arming Level (22h/01h)
19
Fire Trouble (General Type = 4)
4.0 Unspecified
4.1 Hardwire
4.2 Ground Fault
4.3 Device
4.4 Supervisory
4.5 Low Battery
4.6 Tamper
4.7 SAM
4.8 Partial Obscurity
4.9 Jam
4.10 Zone AC Fail
4.11 n/u
4.12 NAC Trouble
4.13 Analog Zone Trouble
4.14 Fire Supervisory
4.15 Pump Fail
4.16 Fire Gate Valve Closed
4.17 CO2 Pressure Trouble
4.18 Liquid Pressure Trouble
4.19 Liquid Level Trouble
20
Opening (General Type = 10)
10.0 Normal Open ES = user number
10.1 Early Open ES = user number
10.2 Late Open ES = user number
10.3 Fail To Open
10.4 Open Exception ES = user number
10.5 Open Extension ES = user number
10.6 Open Using Keyfob/Keyswitch
10.7 Scheduled Open
10.8 Remote Open ES = user number
21
Partition Event (General Type = 13)
13.0 Schedule On ES = schedule number
13.1 Schedule Off ES = schedule number
13.2 Latchkey On
13.3 Latchkey Off
13.4 Smoke Detectors Reset
13.5 Valid User Access Code Entered ES = user number
13.6 Arming Level Changed ES = user number
13.7 Alarm Reported
13.8 Agent Release
13.9 Agent Release Restoral
13.10 Partition Remote Access
13.11 Keystroke Violation in Partition
13.12 Manual Force Arm ES = user number
13.13 Auto Force Arm
13.14 Auto Force Arm Failed
13.15 Arming Protest Begun ES = arming level attempted
13.16 Arming Protest Ended ES = current arming level
22
15.10 Bus Low Power Mode
15.11 Phone Line 1 Failure
15.12 Phone Line 2 Failure
15.13 Remote Phone Tamper
15.14 Watchdog Reset
15.15 RAM Failure
15.16 Flash Failure
15.17 Printer Error
15.18 History Buffer (almost) Full
15.19 History Buffer Overflow
15.20 Report Buffer Overflow
15.21 Bus Device Failure
15.22 Failure To Communicate
15.23 Long Range Radio Trouble
15.24 Module Tamper Trouble
15.25 Un-enrolled Module Trouble
15.26 Audio Output Trouble
15.27 Analog Module Trouble
15.28 Cell Module Trouble
15.29 Buddy 1 Failure
15.30 Buddy 2 Failure
15.31 Buddy 3 Failure
15.32 Buddy 4 Failure
15.33 SnapCard Trouble
15.34 Analog Loop Short
15.35 Analog Loop Break
15.36 Analog Address 0
15.37 Un-enrolled Analog Head
15.38 Duplicate Analog Head
15.39 Analog Module Initializing
15.40 Microphone Switch Trouble
15.41 Microphone Trouble
15.42 Microphone Wiring Trouble
15.43 JTECH Premise Paging Trouble
15.44 Voice Siren Tamper Trouble
15.45 Microburst Transmit Failure
15.46 Microburst Transmit Disabled
15.47 Microburst Module Failure
15.48 Microburst Not In Service
15.49 Automation Supervisory Trouble
15.50 Microburst Module Initializing
15.51 Printer Paper Out Trouble
23
System Configuration Change (General Type = 17)
17.0 Program Mode Entry
17.1 Program Mode Exit Without Change
17.2 Program Mode Exit With Change
17.3 Downloader Session Start
17.4 Downloader Session End Without Change
17.5 Downloader Session End With Change
17.6 Downloader Error
17.7 Downloader Connection Denied
17.8 Date/Time Changed
17.9 Module Added
17.10 Module Deleted
17.11 Speech Tokens Changed
17.12 Code Changed
17.13 Panel First Service (cold reset)
17.14 Panel Back In Service (warm reset)
17.15 Installer Code Changed
24
COMMAND: Siren Setup (22h/04h)
This command is sent whenever there is something to output with the interior siren output,
status beeps, siren sounds, etc. There are 4 cadence bytes. Each bit specifies a 125 mSec
time slice, 1=on, 0=off, beginning with the most significant bit of the first cadence byte. The
combined cadence is repeated RP times (if RP = 0, the cadence is repeated continuously).
The actual outputting of the cadence is not begun until either the Siren Go or the Siren
Synchronize command is received (See commands below). If alarm sirens are active, Advent
also sends the Siren Setup in response to a Dynamic Data Refresh Request (20h).
Format: 0Ah 22h 04h [PN] [AN] [RP] [CD1] [CD2] [CD3] [CD4] [CS]
25
COMMAND: Touchpad Display (22h/09h)
This command sends the touchpad display text tokens to the Automation Module. Advent
also sends the Touchpad Display in response to a Dynamic Data Refresh Request (20h).
26
Token Token Value
Text Token Table ------- --------------
ACCESS 31
Token Token Value ACCOUNT 32
------- -------------- ALARM 33
0 00 ALL 34
1 01 ARM 35
2 02 ARMING 36
3 03 AREA 37
4 04 ATTIC 38
5 05 AUTO 39
6 06 AUXILIARY 3A
7 07 AWAY 3B
8 08 BACK 3C
9 09 BATTERY 3D
# 0C BEDROOM 3E
: 0D BEEPS 3F
/ 0E BOTTOM 40
? 0F BREEZEWAY 41
. 10 BASEMENT 42
A 11 BATHROOM 43
B 12 BUS 44
C 13 BYPASS 45
D 14 BYPASSED 46
E 15 CABINET 47
F 16 CANCELED 48
G 17 CARPET 49
H 18 CHIME 4A
I 19 CLOSET 4B
J 1A CLOSING 4C
K 1B CODE 4D
L 1C CONTROL 4E
M 1D CPU 4F
N 1E DEGREES 50
O 1F DEN 51
P 20 DESK 52
Q 21 DELAY 53
R 22 DELETE 54
S 23 DINING 55
T 24 DIRECT 56
U 25 DOOR 57
V 26 DOWN 58
W 27 DOWNLOAD 59
X 28 DOWNSTAIRS 5A
Y 29 DRAWER 5B
Z 2A DISPLAY 5C
Space 2B DURESS 5D
' 2C EAST 5E
- 2D ENERGY SAVER 5F
_ 2E ENTER 60
* 2F ENTRY 61
AC POWER 30 ERROR 62
28
Token Token Value Token Token Value
------- -------------- ------- --------------
TEST C7 WEST D3
TIME C8 WINDOW D4
TIMEOUT C9 MENU D5
TOUCHPAD CA RETURN D6
TRIP CB POUND D7
TROUBLE CC HOME D8
UNBYPASS CD carriage return F9
UNIT CE pseudo space FA
UP CF carriage return FB
VERIFY D0 backspace FD
VIOLATION D1 blink next token FE
WARNING D2
29
COMMAND: Siren Stop (22h/0Bh)
This command is sent to stop any cadence being output.
Format: 08h 22h 0Dh [PN] [AN] [TM] [ESL] [ESH] [CS]
Format: 08h 22h 0Eh [HR] [MN] [MM] [DD] [YY] [CS]
31
COMMAND: Lights State Command (23h/01h)
This command is sent whenever a light state change occurs or in response to a Refresh
command. THIS COMMAND IS NOT CURRENTLY SUPPORTED BY ADVENT
Format: 0Bh 23h 02h [PN] [AN] [ST] [SNh] [SNm] [SNl] [LN] [LS] [CS]
32
COMMAND: Keyfob Command (23h/03h)
This command is sent whenever the panel receives a keypress from a keyfob.
Format: 08h 23h 03h [PN] [AN] [ZNh] [ZNl] [KC] [CS]
33
AUTOMATION TO PANEL COMMANDS
EP Description
03h Zone Data
04h Partition Data
05h SuperBus Device Data
06h SuperBus Device Capabilities Data
07h Output Data
09h User Data
0Ah Schedule Data
0Bh Scheduled Event Data
0Ch Light to Sensor Attachment
This command is sent for each zone programmed, in response to an equipment list request
from the Automation Module.
Format: [LI] 03h [PN] [AN] [GN] [ZNh] [ZNl] [ZT] [ZS] [text] [CS]
34
PN Partition 0-8 1-6
Number
AN Area Number 0-8 0
GN Group Number 0-35
ZNh Zone Number
high
ZNl Zone Number 1-96
low
ZT Zone Type 0 = sensor 0 = hardwired
1 = keyfob 1 = RF
2 = touchpad 2 = RF touchpad
ZS Zone Status bit 0: 1 = tripped8 (! same)
bit 1: 1 = fault
bit 2: 1 = alarm
bit 3: 1 = trouble
bit 4: 1 = bypassed
text Zone Text bytes See Text Token Table (! same)
CS Checksum Sum of all preceding (! same)
bytes in the
message, taken
modulus 256
8
When sent in response to an equipment list request this bit will always be ‘0’.
35
COMMAND: Send Equipment List - Partition Data (04h)
This command is sent for each enabled partition, in response to an equipment list request
from the Automation Module.
9
Either dealer or user sensor test.
36
COMMAND: Send Equipment List - SuperBus Device Data (05h)
This command is sent for each enrolled bus device, in response to an equipment list request
from the Automation Module.
Format: [LI] 05h [PN] [AN] [ID1] [ID2] [ID3] [DS] [UN] [text] [CS]
37
COMMAND: Send Equipment List - SuperBus Device Capabilities Data (06h)
This command is sent for each capability for each enrolled bus device, in response to an
equipment list request. For each capability present there will be one byte specifying a
capability number and possibly one or more bytes of capability dependent data that consists
of the elaboration of the capability.
38
COMMAND: Send Equipment List - Output Data (07h)
This command is sent for each programmed output in response to an equipment list request.
Format: [LI] 07h [ONh] [ONl] [OS] [ID1] [ID2] [ID3] [ID4] [ID5] [text] [CS]
Advent
---------------
Superbus output ID1-ID3 = device ID
ID4 = output page
ID5 = output bit mask
39
COMMAND: Send Equipment List - User Data (09h)
This command is sent for each user in response to an equipment list request.
40
COMMAND: Send Equipment List - Schedule Data (0Ah)
This command is sent for each schedule in response to an equipment list request. . THIS COMMAND IS NOT
CURRENTLY SUPPORTED BY ADVENT.
Format: [LI] 0Ah [PA] [AA] [SN] [SH] [SM] [PH] [PM] [DY] [SV] [CS]
41
COMMAND: Send Equipment List – Scheduled Event Data (0Bh)
This command is sent for each scheduled event in response to an equipment list request. THIS
COMMAND IS NOT CURRENTLY SUPPORTED BY ADVENT.
Note: If an event is not attached to any schedules, it will not be sent in this list.
Format: [LI] 0Bh [PN] [AN] [ET] [S1] [S2] [S3] [S4] [CS]
42
COMMAND: Send Equipment List – Light to Sensor Attachment (0Ch)
This command is sent for each light in response to an equipment list request. THIS COMMAND
IS NOT CURRENTLY SUPPORTED BY ADVENT.
43
COMMAND: Dynamic Data Refresh Request (20h)
Automation Module requests data refreshing with this command. Panel sends Arming Level,
non-normal Zone Status, Alarm/Trouble Status commands in response. Concord will also
respond with the Panel Type (01h), Feature State (22h/0Ch), Temperature (22h/0Dh), Light
State (23h/01h), and Time and Date (22h/0Eh) commands. Advent will also respond with the
Siren Setup command (22h/04h) if there is an active alarm siren and the Touchpad Display
command (22h/09h) to refresh the displays.
44
00h 0
01h 1
02h 2
03h 3
04h 4
05h 5
06h 6
07h 7
08h 8
09h 9
0Ah *
0Bh #
0Ch Police Panic
0Dh Aux. Panic
0Eh Fire Panic
10h Lights On
11h Lights Off
12h Lights Toggle
13h Keyswitch on
14h Keyswitch off
15h Keyswitch toggle (not implemented)
16h <undefined>
17h <undefined>
18h <undefined>
19h <undefined>
1Ah <undefined>
1Bh <undefined>
45
COMMAND: Reserved
The following commands are reserved for special use.
Message format:
03 60h xx CS
03h 99h xx [CS]
03h 98h xx [CS]
46