3003 W CASINO RD BLDG 40-23 2018-09-21

ARIES NETLink DACT DC-OS and DC-03 Protocol Mapping This document describes how control unit information is mapped to the DACT transmissions to the central station Digital Alarm Communicator Receiver(DACR) data for the two supported protocols— DC-05 and DC-03. DC-05/Ademco The DC-05 protocol includes a three digit event code. The control unit uses these event codes when transmitting events to the central station via the Digital Alarm Communicator Transmitter (DACT). Normal Status is achieved by the clearing of all faults and alarms and transmission of those clear events to the DACR. Event codes (XYZ) (3 Hex digits 0-9) : see the table below. ��n�f[��s�ri��i�z��` �...`r, � :�.. 4,;.3° ` �V � ,��uera�w,Cod;��YZ � AC Failure 301 Low Batte Volta e 302 Alarm Per Point* 111 - 116 S stem Su erviso 200 S stem Trouble 300 Ground Fault 310 NAC Trouble 326 De raded o eration due to micro rocessor failure 308 Fault / Loss of phone line #1 (No Dial Tone, Loss of 351 Line Volta e, etc. Fault / Loss of phone line #2 (No Dial Tone, Loss of 352 Line Volta e, etc. Backplane communication lost with MCB 308 Event Codes Table *Alarm per Point event codes are expanded to the following by on the device that reports the alarm condition: 111 Smoke Alarms 113 Water flow Alarm 114 Heat Alarm 115 Pull Station Alarm 116 Duct Alarm Group or Partition number (GG) (2 decimal digits 0-9): This field is used to represent the node number of the event. A value 01 to 64 indicates the event is from a control unit on a networked system. Device number (CCC) (3 digits 0-9, B-F): This field represents the device address in the case of an Alarm. Device number equal to 000 indicates that no specific zone or user information applies, which is the case for all other event types. Since the DC-05 transmission protocol does not support enough digits and the hexadecimal value `A' is not supported, the alarm per point address information must be manipulated to cover Page 1