> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/alarm-transmission/alarm-transmission-ademco-format.md). # Ademco format Reference Ademco Contact ID fields, DC-09 packet structure, and event codes. Command Centre transmits alarm events in the **Ademco Contact ID** format over both Analog (PSTN dialler) and IP (DC-09) transports. This page is the format reference. For how to set up monitoring and diallers, see [Alarm Transmission - Monitoring](/knowledge-hub/products/cc-software/configure/alarm-transmission/alarm-transmission-monitoring.md). *** ### Alarm Dialler format (PSTN) The Alarm Dialler (Dialer in the USA) is a component that uses an RS232 (serial) port to connect to a PSTN dialler and send messages using **ADEMCO Contact ID**, an industry standard across the world since 1999. The format of the message is: ``` ACCT MT Q XYZ GG CCC ``` | Field | Meaning | | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ACCT** | 4-digit account number (0-9, B-F). Set in either the System Properties or in the Alarm Zone itself. | | **MT** | Message Type. A 2-digit sequence identifying the Contact ID message to the receiver. Transmitted as either **18** (preferred) or **98** (optional). New receiver implementations accept either; some older receivers may not accept 98. | | **Q** | Event qualifier: **1** = New Event or Opening; **3** = New Restore or Closing; **6** = Previously reported condition still present (status report). | | **XYZ** | Event code (3 hex digits, 0-9, B-F). Decided by the event type selected at the Input Properties. See the addendum table below. | | **GG** | Group or Partition number (2 hex digits, 0-9, B-F). This is the Alarm Zone in Command Centre. Use **00** to indicate no specific group or partition applies. | | **CCC** | Zone number (event reports) or User # (open/close reports), 3 hex digits (0-9, B-F). Use **000** to indicate no specific zone or user applies. | *** ### IP Alarm Transmitter format (DC-09 packet) The IP Alarm Transmitter sends messages directly from the controller to a monitoring station over TCP/IP instead of a phone line. It has two protocol options, **CSV** and **DC-09**. The following explains how the DC-09 message is composed and how it relates to ADEMCO Contact ID. A controller's outgoing message, observable in the controller's debug webpage under **Parts Manager > Alarm Transmitter Part**, may look like: ``` "ADM-CID"0005L98765#001235[#001235|1423 44 777]_17:15:19,03-06-2026 "ADM-CID"0006L98765#001235[#001235|3423 44 777]_17:15:30,03-06-2026 ``` The format is: ``` ID SEQ LLLLL #RI [#ACCT | Q XYZ GG CCC ] _TIME,DATE ``` The second half (between `|` and `]`, which DC-09 calls the **DATA**) is almost identical to the Alarm Dialler format, except there is **no MT**. The ACCT is sent as **6 digits**, so an ACCT of 1235 in Command Centre is padded to **001235**. Aside from time and date, there are four new components: **ID, SEQ, LLLLL, RI**: | Field | Meaning | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **ID** | The format, always `"ADM-CID"` within Command Centre. Tells the receiver we are using ADEMCO Contact ID format in the DATA. | | **SEQ** | The sequence of messages (for example 0005, then 0006 on the next message). | | **LLLLL** | Line Card. In Command Centre this is called the **Prefix**. For American monitoring stations this is typically known as **DNIS**, despite that being an antiquated term. | | **RI** | Receiver ID. The field that causes the most confusion. | ### Receiver ID behaviour changed by version RI is intended to be an ID for the device sending the message (a panel ID, or a Transmitter ID as Command Centre calls it). However, Command Centre versions **v8.70.2078+ (MR3+), v8.80.1025+ (MR1+) and v8.90+** behave differently since the Prefix field was added: * If **Prefix is set to 0** then the old behaviour remains: the **Transmitter ID** is sent in this field. * If **Prefix is populated with something other than 0** then the **6-digit ACCT** is sent (as in the two examples above). How it looks in the Configuration Client: ![ADEMCO format configuration in the Configuration Client](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c4e2699a6daab47c0d49f716cc5f6bbbae5dc8f4%2FSECHUB-CCS-ADEMCO-01-config-client.png?alt=media) > **Note:** The Gallagher IP Alarm Receiver software is still able to receive messages, as long as the 6-digit value of ACCT is configured in the field the receiver software calls **Transmitter ID**. *** ### Addendum: XYZ event code list The following is the **internationally accepted** Contact ID event code list. Note that this is the standard list, **not necessarily the event Command Centre will transmit**. | XYZ | Name | Type | Description | | --- | ----------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 100 | Medical | Zone | A non-specific medical condition exists | | 101 | Personal Emergency | Zone | Emergency Assistance request | | 102 | Fail to report in | Zone | A user has failed to activate a monitoring device | | 110 | Fire | Zone | A non-specific fire alarm condition exists | | 111 | Smoke | Zone | An alarm has been triggered by a smoke detector | | 112 | Combustion | Zone | An alarm has been triggered by a combustion detector | | 113 | Water Flow | Zone | An alarm has been triggered by a water flow detector | | 114 | Heat | Zone | An alarm has been triggered by a heat detector | | 115 | Pull Station | Zone | A pull station has been activated | | 116 | Duct | Zone | An alarm has been triggered by a duct detector | | 117 | Flame | Zone | An alarm has been triggered by a flame detector | | 118 | Near Alarm | Zone | A near-alarm condition has been detected on a fire sensor | | 120 | Panic | Zone | A non-specific hold-up alarm exists | | 121 | Duress | User | A duress code has been entered by a user | | 122 | Silent | Zone | silent hold-up alarm exists | | 123 | Audible | Zone | An audible hold-up alarm exists | | 124 | Duress - Access granted | Zone | A duress code has been entered and granted at an entry door | | 125 | Duress - Egress granted | Zone | A duress code has been entered and granted at an exit door | | 126 | Hold-up suspicion print | User | A user has activated a trigger to indicate a suspicious condition | | 129 | Panic Verifier | Zone | A confirmed Hold-up condition exists | | 130 | Burglary | Zone | A burglary zone has been violated while armed | | 131 | Perimeter | Zone | A perimeter zone has been violated while armed | | 132 | Interior | Zone | An interior zone has been violated while armed | | 133 | 24 Hour (Safe) | Zone | A 24 hour burglary zone has been violated | | 134 | Entry/Exit | Zone | An Entry/Exit zone has been violated while armed | | 135 | Day/Night | Zone | An trouble by Day / alarm by Night zone has been violated while armed | | 136 | Outdoor | Zone | An outdoor burglary zone has been violated while armed | | 137 | Tamper | Zone | A burglary zone has been tampered with while armed | | 138 | Near alarm | Zone | A burg sensor has detected a condition which will cause it to go into alarm if the condition worsens | | 139 | Intrusion Verifier | Zone | The specified zone has verified that an intrusion has occurred | | 140 | General Alarm | Zone | The specified zone is in an alarm condition | | 141 | Polling loop open | Zone | An open circuit condition has been detected on a polling loop while the system was armed | | 142 | Polling loop short | Zone | A short circuit condition has been detected on a polling loop while the system was armed | | 143 | Expansion module failure | Zone | A general failure condition has been detected on an expansion module while the system was armed | | 144 | Sensor tamper | Zone | A sensor's tamper has been violated (case opened) | | 145 | Expansion module tamper | Zone | An expansion module's tamper has been violated (cabinet opened) | | 146 | Silent Burglary | Zone | A burglary zone has been violated while armed with no audible notification produced | | 147 | Sensor Supervision Failure | Zone | A sensor's supervisory circuit has reported a failure while the system was armed | | 150 | 24 Hour Non-Burglary | Zone | A non-burglary zone has been faulted | | 151 | Gas detected | Zone | The gas detector assigned to the specified zone has reported a fault condition | | 152 | Refrigeration | Zone | The refrigeration detector assigned to the specified zone has reported a fault condition | | 153 | Loss of heat | Zone | The temperature detector assigned to the specified zone has reported a fault condition | | 154 | Water Leakage | Zone | The water leak detector assigned to the specified zone has reported a fault condition | | 155 | Foil Break | Zone | The specified zone which is assigned to foil used as glass break detection has reported a fault condition | | 156 | Day Trouble | Zone | The specified zone which monitors trouble by day has reported a fault condition while disarmed | | 157 | Low bottled gas level | Zone | The gas level detector assigned to the specified zone has reported a fault condition | | 158 | High temp | Zone | The over-temperature detector assigned to the specified zone has reported a fault condition | | 159 | Low temp | Zone | The under-temperature detector assigned to the specified zone has reported a fault condition | | 161 | Loss of air flow | Zone | The air flow detector assigned to the specified zone has reported a fault condition | | 162 | Carbon Monoxide detected | Zone | The carbon monoxide detector assigned to the specified zone has reported a fault condition | | 163 | Tank level | Zone | The tank level detector assigned to the specified zone has reported a fault condition | | 168 | High Humidity | Zone | A High Humidity condition has been detected | | 169 | Low Humidity | Zone | A Low Humidity condition has been detected | | 200 | Fire Supervisory | Zone | The supervisory circuit of the specified fire zone has reported a fault condition | | 201 | Low water pressure | Zone | The water pressure sensor assigned to the specified zone has reported a fault condition | | 202 | Low CO2 | Zone | The CO2 pressure sensor assigned to the specified zone has reported a fault condition | | 203 | Gate valve sensor | Zone | The gate valve sensor in the fire sprinkler system assigned to the specified zone has reported a fault condition | | 204 | Low water level | Zone | The water level sensor assigned to the specified zone has reported a fault condition | | 205 | Pump activated | Zone | The pump activity detector assigned to the specified zone has reported an active condition | | 206 | Pump failure | Zone | A pump output monitor assigned to the specified zone has reported a fault condition | | 300 | System Trouble | Zone | A general system trouble condition has been reported by the specified zone | | 301 | AC Loss | Zone | AC power loss has been detected at a control or expansion module while the system was disarmed | | 302 | Low system battery | Zone | A battery has failed a load test while the system was disarmed | | 303 | RAM Checksum bad | Zone | A test of the system's memory has failed | | 304 | ROM checksum bad | Zone | A test of the system's executable memory has failed | | 305 | System reset | Zone | The system has reset and restarted | | 306 | Panel programming changed | Zone | The programmed configuration of the panel has changed | | 307 | Self-test failure | Zone | The system has failed a self-test | | 308 | System shutdown | Zone | The system has been shut down and has stopped functioning | | 309 | Battery test failure | Zone | The system backup battery has failed a load test while the system was disarmed | | 310 | Ground fault | Zone | The panel has detected a ground fault condition | | 311 | Battery Missing/Dead | Zone | The system has detected that the backup battery is either missing or completely discharged. | | 312 | Power Supply Overcurrent | Zone | The system power supply has reported an excessive current draw condition | | 313 | Engineer Reset | User | The specified service person has issued a system reset | | 314 | Primary Power Supply Failure | Zone | The system's primary power supply has failed a supervision test. Radio devices indicate this when the backup battery charging circuit has failed its supervision test | | 316 | System Tamper | Zone | The system has been tampered with and may have been compromised | | 320 | Sounder/Relay | Zone | A trouble condition exists in the system's sounder/relay circuit | | 321 | Bell 1 | Zone | A trouble condition exists in the primary bell circuit | | 322 | Bell 2 | Zone | A trouble condition exists in the secondary bell circuit | | 323 | Alarm relay | Zone | A trouble condition exists in the system's alarm relay circuit | | 324 | Trouble relay | Zone | A trouble condition exists in the system's trouble relay circuit | | 325 | Reversing relay | Zone | The specified TELCO reversing relay has reported a trouble condition | | 326 | Notification Appliance Ckt. # 3 | Zone | A trouble condition exists in the bell #3 circuit | | 327 | Notification Appliance Ckt. #4 | Zone | A trouble condition exists in the bell #4 circuit | | 330 | System Peripheral trouble | Zone | A system peripheral device has reported a trouble condition | | 331 | Polling loop open | Zone | An open circuit condition has been detected on a polling loop while the system was disarmed | | 332 | Polling loop short | Zone | A short circuit condition has been detected on a polling loop while the system was disarmed | | 333 | Expansion module failure | Zone | A general failure condition has been detected on an expansion module while the system was disarmed | | 334 | Repeater failure | Zone | A repeater in the system has reported a failure condition while the system was disarmed | | 335 | Local printer out of paper | Zone | The printer attached to the panel has reported an Out Of Paper condition | | 336 | Local printer failure | Zone | The printer attached to the panel has reported a failure condition | | 337 | Exp. Module DC Loss | Zone | An expansion module has detected a DC power loss | | 338 | Exp. Module Low Batt | Zone | An expansion module has detected a low battery condition | | 339 | Exp. Module Reset | Zone | An expansion module has reset | | 341 | Exp. Module Tamper | Zone | An expansion module has detected its taper switch has been faulted | | 342 | Exp. Module AC Loss | Zone | An expansion module has detected the loss of AC power | | 343 | Exp. Module self-test fail | Zone | An expansion module has failed a self-test | | 344 | RF Receiver Jam Detect | Zone | An RF receiver has detected the presence of a jamming signal, preventing it from receiving normal signals from the system RF devices | | 345 | AES Encryption disabled/ enabled | Zone | E345 AES Encryption has been disabledR345 AES Encryption has been enabled | | 350 | Communication trouble | Zone | The system has experienced difficulties communicating with the central station | | 351 | Telco 1 fault | Zone | The system has detected a fault on the primary dial-up line | | 352 | Telco 2 fault | Zone | The system has detected a fault on the secondary dial-up line | | 353 | Long Range Radio xmitter fault | Zone | A fault has been detected in the long range radio subsystem | | 354 | Failure to communicate event | Zone | The system was unable to communicate an event to the central station | | 355 | Loss of Radio supervision | Zone | The radio has not reported in its designated supervision interval | | 356 | Loss of central polling | Zone | The radio has detected a loss in the polling signal from it's associated receiver | | 357 | Long Range Radio VSWR problem | Zone | The Long Range Radio has reported a transmitter/antenna problem | | 358 | Periodic Comm Test Fail /Restore | Zone | A periodic Communication path test has failed | | 370 | Protection loop | Zone | The specified protection loop has reported a trouble condition | | 371 | Protection loop open | Zone | The specified protection loop has reported an open-loop trouble condition | | 372 | Protection loop short | Zone | The specified protection loop has reported a shorted-loop trouble condition | | 373 | Fire trouble | Zone | A fire sensor has detected a trouble condition on the specified zone while the system was disarmed | | 374 | Exit error alarm (zone) | Zone | An exit error condition has been reported for the specified alarm zone | | 375 | Panic zone trouble | Zone | The system has detected a trouble condition on the panic zone | | 376 | Hold-up zone trouble | Zone | The system has detected a trouble condition on the hold-up zone | | 377 | Swinger Trouble | Zone | A fault has occurred on a zone that has been shut down due to excessive alarms | | 378 | Cross-zone Trouble | Zone | The specified zone in a cross-zone configuration has faulted without a fault on its corresponding cross-zone in a specific time period | | 380 | Sensor trouble | Zone | The specified sensor has reported a trouble condition | | 381 | Loss of supervision - RF | Zone | The specified zone has failed to report in during its designated supervision period | | 382 | Loss of supervision - RPM | Zone | An Remote Polled Module assigned to the specified zone has failed supervision | | 383 | Sensor tamper | Zone | The tamper switch on the specified sensor has been faulted | | 384 | RF low battery | Zone | The specified battery powered RF zone has reported a low battery condition | | 385 | Smoke detector Hi sensitivity | Zone | A smoke detector's sensitivity level has drifted to the upper limit | | 386 | Smoke detector Low sensitivity | Zone | A smoke detector's sensitivity level has drifted to the lower limit | | 387 | Intrusion detector Hi sensitivity | Zone | An intrusion detector's sensitivity level has drifted to the upper limit | | 388 | Intrusion detector Low sensitivity | Zone | An intrusion detector's sensitivity level has drifted to the lower limit | | 389 | Sensor self-test failure | Zone | The specified sensor has failed a self-test | | 391 | Sensor Watch trouble | Zone | A motion sensor has not been triggered within a pre-defined time interval | | 392 | Drift Compensation Error | Zone | A smoke detector cannot automatically adjust its sensitivity | | 393 | Maintenance Alert | Zone | The specified zone requires maintenance | | 394 | CO Detector needs replacement | Zone | The specified Carbon Monoxide detector has reached end-of-life | | 400 | Open/Close | User | The specified user has disarmed/armed the system | | 401 | O/C by user | User | The specified user has disarmed/armed the system | | 402 | Group O/C | User | A group of zones has been armed or disarmed | | 403 | Automatic O/C | User | A partition has been automatically armed or disarmed | | 404 | Late to O/C (Note: use 453 or 454 instead ) | User | | | 405 | Deferred O/C (Obsolete- do not use ) | User | | | 406 | Cancel | User | The specified user has cancelled the previously reported alarm condition | | 407 | Remote arm/disarm | User | The specified user has armed or disarmed the system from off-premises | | 408 | Quick arm | User | The specified user has quick-armed the system | | 409 | Keyswitch O/C | User | The specified user has armed or disarmed the system using a keyswitch | | 411 | Callback request made | User | A remote site (central station) has requested the panel call it back | | 412 | Successful download/access | User | The configuration data of the system has been successfully downloaded | | 413 | Unsuccessful access | User | A number of failed attempts have been made to remotely access the system | | 414 | System shutdown command received | User | A central station has sent a system shutdown command to the panel | | 415 | Dialer shutdown command received | User | A central station has sent a dialer shutdown command to the panel | | 416 | Successful Upload | Zone | The configuration data of the system has been successfully uploaded | | 421 | Access denied | User | The access control system has denied access to the specified user | | 422 | Access report by user | User | | | 423 | Forced Access | User | The specified access control door has been forced open | | 424 | Egress Denied | User | The access control system has denied egress to the specified user | | 425 | Egress Granted | User | The access control system has granted egress for the specified user | | 426 | Access Door propped open | Zone | The specified access control door has been held open | | 427 | Access point Door Status Monitor trouble | Zone | The specified Access Point's Door Status Monitor has reported a trouble condition to the panel | | 428 | Access point Request To Exit trouble | Zone | The specified Access Point's Request To Exit zone has reported a trouble condition to the panel | | 429 | Access program mode entry | User | The access control system has been put into program mode | | 430 | Access program mode exit | User | The access control system has exited program mode | | 431 | Access threat level change | User | The access control system's threat level has been changed | | 432 | Access relay/trigger fail | Zone | The specified access control output device has failed to operate properly | | 433 | Access RTE shunt | Zone | The specified Request To Exit zone has been shunted and will no longer report activity | | 434 | Access DSM shunt | Zone | The specified Door Status Monitor zone has been shunted and will no longer report activity | | 435 | Second Person Access | User | A second person has accessed an access point conforming to Two-Man-Rule requirements | | 436 | Irregular Access | User | | | 441 | Armed STAY | User | The specified user has armed the system in STAY mode | | 442 | Keyswitch Armed STAY | User | The specified user has armed the system in STAY mode using a keyswitch | | 443 | Armed with System Trouble Override | User | The specified user has armed the system while overriding a trouble condition | | 450 | Exception O/C | User | The system has been armed or disarmed outside of the configured time window | | 451 | Early O/C | User | The system has been disarmed/armed by the specified user before the configured time window has started | | 452 | Late O/C | User | The system has been disarmed/armed by the specified user after the configured time window has ended | | 453 | Failed to Open | User | The system has failed to have been disarmed during the designated time window | | 454 | Failed to Close | User | The system has failed to be armed during the designated time window | | 455 | Auto-arm Failed | User | The system has failed to automatically arm itself at the designated time | | 456 | Partial Arm | User | The system has been only partially armed by the specified user | | 457 | Exit Error (user) | User | The specified user has made an error exiting the premises after arming the system | | 458 | User on Premises | User | A user has disarmed the system after an alarm has occurred | | 459 | Recent Close | User | The system had been armed within the last xx minutes | | 461 | Wrong Code Entry | Zone | | | 462 | Legal Code Entry | User | | | 463 | Re-arm after Alarm | User | | | 464 | Auto-arm Time Extended | Zone | A user has successfully requested that the system delay automatically arming | | 465 | Panic Alarm Reset | User | The specified panic zone has been reset | | 466 | Service On/Off Premises | User | A service person has entered or left the premises | | 501 | Access reader disable | Zone | The credential reader on the specified access point has been disabled | | 520 | Sounder/Relay Disable | Zone | The specified sounder or relay has been disabled | | 521 | Bell 1 disable | Zone | The specified output for Bell 1 has been disabled | | 522 | Bell 2 disable | Zone | The specified output for Bell 2 has been disabled | | 523 | Alarm relay disable | Zone | The specified alarm relay has been disabled | | 524 | Trouble relay disable | Zone | The specified trouble relay has been disabled | | 525 | Reversing relay disable | Zone | The specified reversing relay has been disabled | | 526 | Notification Appliance Ckt. # 3 disable | Zone | The specified output for Bell 3 has been disabled | | 527 | Notification Appliance Ckt. # 4 disable | Zone | The specified output for Bell 4 has been disabled | | 531 | Module Added | Zone | The specified access control module has been added to the system | | 532 | Module Removed | Zone | The specified access control module has been removed from the system | | 551 | Dialer disabled | Zone | The specified dialer has been disabled | | 552 | Radio transmitter disabled | Zone | The specified radio transmitter has been disabled | | 553 | Remote Upload/Download disabled | Zone | Remote configuration has been enabled | | 570 | Zone/Sensor bypass | Zone | The specified zone or sensor has been bypassed | | 571 | Fire bypass | Zone | The specified fire zone has been bypassed | | 572 | 24 Hour zone bypass | Zone | The specified 24 hour zone has been bypassed | | 573 | Burg. Bypass | Zone | The specified burglary zone has been bypassed | | 574 | Group bypass | Zone | A group of zones has been bypassed | | 575 | Swinger bypass | Zone | The specified zone which has reported an excessive number of faults/restores in a short period of time has been bypassed | | 576 | Access zone shunt | Zone | The specified zone in the access control system has been shunted and will no longer report activity | | 577 | Access point bypass | Zone | The specified access point in the access control system has been bypassed and will allow the door to open (unsecured) | | 578 | Vault Bypass | Zone | The specified vault zone has been bypassed | | 579 | Vent Zone Bypass | Zone | The specified vent zone has been bypassed and will no longer report any activity | | 601 | Manual trigger test report | Zone | A test report has been triggered manually | | 602 | Periodic test report | Zone | A periodic test report has been triggered | | 603 | Periodic RF transmission | Zone | A periodic RF path test report has been triggered | | 604 | Fire test | User | The specified user has initiated a test of the fire alarm zones | | 605 | Status report to follow | Zone | | | 606 | Listen-in to follow | Zone | The system is about to activate a 2-way audio session | | 607 | Walk test mode | User | The specified user has placed the system into the walk-test mode for testing purposes | | 608 | Periodic test - System Trouble Present | Zone | A periodic test has been triggered but the fire system has a trouble condition present | | 609 | Video Xmitter active | Zone | A video look-in session is about to begin | | 611 | Point tested OK | Zone | The specified point tested successfully | | 612 | Point not tested | Zone | The specified point has not been tested | | 613 | Intrusion Zone Walk Tested | Zone | The specified intrusion zone has been successfully walk-tested | | 614 | Fire Zone Walk Tested | Zone | The specified fire zone has been successfully walk-tested | | 615 | Panic Zone Walk Tested | Zone | The specified panic zone has been successfully walk-tested | | 616 | Service Request | Zone | A request has been made for system servicing | | 621 | Event Log reset | Zone | The event log has been reset and all stored events have been discarded | | 622 | Event Log 50% full | Zone | The event log is 50% full | | 623 | Event Log 90% full | Zone | The event log is 90% full | | 624 | Event Log overflow | Zone | The event log has overflowed and events have been lost | | 625 | Time/Date reset | User | The time and date have been reset to a new value by the specified user | | 626 | Time/Date inaccurate | Zone | The system time and date is known to be in error | | 627 | Program mode entry | Zone | The system has been placed into program mode | | 628 | Program mode exit | Zone | The system has exited program mode | | 629 | 32 Hour Event log marker | Zone | | | 630 | Schedule change | Zone | The specified fire/burglary schedule has been changed | | 631 | Exception schedule change | Zone | The time schedule for event reporting by exception has been changed | | 632 | Access schedule change | Zone | The specified access control schedule has been changed | | 641 | Senior Watch Trouble | Zone | A person has not activated a motion sensor in a specified period | | 642 | Latch-key Supervision | User | A child has disarmed the system (after school) | | 651 | Reserved for Ademco Use | Zone | | | 652 | Reserved for Ademco Use | User | | | 653 | Reserved for Ademco Use | User | | | 654 | System Inactivity | Zone | System has not been operated for x days | | 655 | User Code X modified by Installer | User | The Installer has modified the specified User's code | | 703 | Auxiliary #3 | Zone | | | 704 | Installer Test | Zone | | | 750 | User Assigned | | | | 789 | User Assigned | | | | 796 | Unable to output signal (Derived Channel) | Zone | | | 798 | STU Controller down (Derived Channel) | Zone | | | 900 | Download Abort | Downloader ID | The specified Downloader ID has aborted a download sequence in progress | | 901 | Download Start/End | Downloader ID | Downloader has started or ended a download sequence to the panel | | 902 | Download Interrupted | Downloader ID | A download sequence has been interrupted | | 903 | Device Flash Update Started/ Completed | Device | A code update for a device has started (E903) or completed successfully (R903) | | 904 | Device Flash Update Failed | Device | A code update for a device has failed | | 910 | Auto-close with Bypass | Zone | An auto-close sequence has been started and the specified zone has been bypassed | | 911 | Bypass Closing | Zone | | | 912 | Fire Alarm Silence | Zone | The fire alarm has been silenced | | 913 | Supervisory Point test Start/End | User | A fire supervisory device has been tested | | 914 | Hold-up test Start/End | User | The specified user has started or ended a hold-up test | | 915 | Burg. Test Print Start/End | User | The printed progress of a burglary test has been started or ended | | 916 | Supervisory Test Print Start/End | User | The printed progress of a supervisory test has been started or ended | | 917 | Burg. Diagnostics Start/End | Zone | A burglary system diagnostic test has been started or ended | | 918 | Fire Diagnostics Start/End | Zone | A fire system diagnostic test has been started or ended | | 919 | Untyped diagnostics | Zone | | | 920 | Trouble Closing (closed with burg. during exit) | User | | | 921 | Access Denied Code Unknown | User | Access has been denied because the system did not recognize the supplied access code as valid | | 922 | Supervisory Point Alarm | Zone | The specified supervisory point has reported an alarm condition | | 923 | Supervisory Point Bypass | Zone | The specified supervisory point has been bypassed | | 924 | Supervisory Point Trouble | Zone | The specified supervisory point has reported a trouble condition | | 925 | Hold-up Point Bypass | Zone | The specified hold-up point has been bypassed | | 926 | AC Failure for 4 hours | Zone | There has been a loss of AC power for at least four hours | | 927 | Output Trouble | Zone | The specified output has reported a trouble condition | | 928 | User code for event | User | This message contains the ID of the user who triggered the previous event | | 929 | Log-off | User | The specified user has logged-off of the system | | 954 | CS Connection Failure | Zone | The specified CS connection has failed/restored | | 961 | Rcvr Database Connection Fail/Restore | Zone | The connection to the receiver's database has failed/restored | | 962 | License Expiration Notify | Zone | The product license has been terminated (7810PC) | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/alarm-transmission/alarm-transmission-ademco-format.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.