Table 8-8: Call Message With Listen-In Data - Honeywell ADEMCO MX8000 Installation And Operation Manual

Digital alarm receiver
Hide thumbs Also See for ADEMCO MX8000:
Table of Contents

Advertisement

MX8000 Installation and Operation Guide
The following is an example of a call message containing a listen-in indicator:
Example:
<FMT#><LC#><$05><123456><BA01><$2A><"060"><V-byte><$0D>
Table 8–8 describes the components of a call message containing a listen-in indicator.
Note: If the control panel calling does not include the listen-in period in the reporting message, the receiver
uses the listen-in timeout programmed in the line card. See Section 5.5.2.4.
8.4.2.4
Long Call Indicator
The maximum number of bytes the ADEMCO 8000 protocol can send to the automation computer in a single
packet is 128. If a panel sends more than 128 bytes, the receiver will break the panel information data down
into groups of 128 bytes or less. To alert the automation computer that this is being done, a long call
indicator (<$2C>) will be added before the V-byte to indicate more data is to follow.
The entire data string in a long call contains the same values in the header block. The last data string of the
long call will not contain a long call indicator prior to the V-byte.
The example below shows the long call data excluding the AE header and the panel data.
....<$2C><V-byte><$0D>
Note: Some panels are capable of transmitting multiple account information in a single call. The MX8000
receiver will treat a call with multiple accounts as multiple calls with a single account and will divide the call
into multiple data blocks. However, to distinguish them from a call with a single account, each data block of a
call with multiple accounts will contain the same reference number and a long call indicator with the
exception of the last block of data.
8.4.2.5
Bad Data Field Indicator
If the data received by the MX8000 is garbled or parts are missing the receiver will send a bad data indicator
(<$23> used in the event block as a separator) before the block of corrupted data. A bad data block will
contain a hex-ASCII dump of the data in ASCII form.
The example below shows a bad data field indicator excluding the AE header and some of the panel data.
Example:
<$23><aaaaaaaa><$23><bbbbb><$05><"123456"><$22><"BA01"><V-byte><$0D>
Table 8–9 shows the character in the above example and gives a description for each.
8–6
Table 8–8: Call Message With Listen-in Data
Character
<AE header>
AE header block of data. See
Section 8.4.1.
<FMT#>
Dialer format number containing
three ASCII digits. See 8.4.2.1.
<LC#>
Line Card number containing two
ASCII digits.
<$05>
Panel Data. See 8.4.2.2.
<123456>
<BA01>
<$2A>
Listen-in indicator.
<"060">
Listen-in time period in seconds.
Three ASCII characters- 60
seconds.
<V-byte>
Validation byte. See Section 8.4.5.
<$0D>
End of message indicator.
Description

Advertisement

Table of Contents
loading

Table of Contents