ARC Communication Formats
Page 135
SIA 1, SIA 2, SIA 3 and Extended SIA 3
When using the SIA formats, the control unit transmits data from the event log to the ARC.
The four SIA formats differ in the amount of data transmitted with each message:
Type
Format
SIA1:
#AAAAAA|NCCcc
SIA2:
#AAAAAA|Nidnnn/rinn/CCcc
SIA3:
#AAAAAA|Ntihh:mm/idnnn/rinn/CCcc
#AAAAAA|AS
Extended SIA 3:
#AAAAAA|Ntihh:mm/idnnn/rinn/CCcc/AS
Where:
AAAAAA
6-digit programmable account code (e.g. 123456).
“N”
New Event (always N).
“ti”hh:mm/
time (e.g. ti10:23/).
“id”nnn/
user number, if applicable; otherwise not sent (e.g.
id123/ or id6/).
“ri”nn/
partition no. (e.g. ri12/ or ri3).
CC
event code (e.g. FA = Fire Alarm).
cc
zone number, if applicable; otherwise not sent (e.g. 23
or 5).
“A”S
text description of event, usually the log event
description.
(The control unit sends those characters
shown between “ and “ above literally as they
appear in the text.)
For example, if there is a fire alarm on zone 2 of partition 4 at 10:15 (partition 4 account
number is 10), the message would be:
SIA1:
#000010|NFA2
SIA2:
#000010|N/ri4/FA2
SIA3:
#000010|Nti10:15/ri4/FA2 #000010|AFire Zone 2
Extended SIA3:
#000010|Nti10:15/ri4/FA2/AFire Zone 2
Extended SIA3 V2
Some versions of the software that works in SIA receivers do not always recognise the “/”
text delimiter. This can cause problems with
spurious “Mains Fail” messages appearing to
the ARC when the control unit sets, unsets or goes into or out or installer mode.
In version 2 of Extended SIA3,
the “/” delimiter has been replaced by a “|”. So, for
example, the string: #000010|Nti10:15/ri4/FA2/AFire Zone 2
becomes: #000010|Nti10:15|ri4|FA2|AFire Zone 2
If you have experienced problems with spurious “Mains Fail” messages try using this
Extended SIA3 V2 option.
