EasyManua.ls Logo

GE Security EST3 - Compatibility; Transmission Protocols

GE Security EST3
388 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Installation
EST3 Installation and Service Manual
5.32
These entries are made on the System tab of the Cardholder tab.
The ACDB user should enter a User ID for each CMS Account.
Compatibility
EST3 versions
The 3-MODCOM Module will operate with EST3 Version. 3.0
or above. Do not use this communication module with earlier
versions.
Receiver compatibility
Refer to the EST3 ULI/ULC Compatibility Lists (P/N 3100427),
for a list of compatible receivers.
Transmission protocols
The 3-MODCOM is capable of transmitting messages in five
formats, or protocols:
• Contact ID
• SIA DCS
SIA P2 (3/1 Pulse Format)
SIA P3 (4/2 Pulse Format)
TAP (3-MODCOMP only)
All formats consist of short, predefined messages. Most contain
several parameters, some of which are optional. Check with your
dialer receiver and central monitoring station software provider
for the exact structure they require.
When programming transmissions, remember that device
messages require two separate send commands, one for
activation, and one for restoration.
Contact ID:
numeric messages with several parameters including
event code, partition, and device or user. The format is:
[EventCode] [Partition] [DeviceNumber | User]
SIA DCS: ASCII text messages that include a number of
optional parameters, including time, date, user, partition, and
device. The format is:
[Date] [Time] [UserID] AlarmCode [Device | User | Partition]
SIA P2 (3/1): numeric messages that consist of four digits. These
contain the account number (three digits) and the alarm code
(one digit). The format is:
AccountNumber AlarmCode
The is no standard assignment of alarm codes and meanings.
Obtain the codes used by your CMS.

Table of Contents