Sierra Monitor Company FS-8700-48 - Manual (Page 13)

FS-8700-48 Fike Cheetah Manual Page 14 of 37
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]
Column Title Function Legal Values
DA_Byte_Name
Full details of the most recent event (any device) may be stored in
the data array DA_HIST_EVENT. See sections 5.4.14 and 5.4.15.
Appendix D.3 maps the layout of this data.
DA_Hist_Event
5.4 Map Descriptor Examples
The driver processes messages from the panel that relay the panel’s current status as well as new history events.
These messages contain composite data and the contents cannot simply be stored in a Data Array to read by a
Client device.
Map Descriptors are used to store portions of this composite data from the following categories. At least one Map
Descriptor is required for each category.
5.4.1 Zone Status
There are two methods of storing Zone status data:
The driver can store the state (trouble, alarm, pre-alarm...) of each zone in a separate array as a a bit state
(1 or 0). See sections 5.4.6 and 5.4.7. A separate Map Descriptor is required per zone state (9 possible).
The driver can store a number to indicate normal or abnormal state of each zone. (The value of the
number indicates the states.) See section 5.4.8. All data is stored in a single Data Array and one Map
Descriptor is required for all zones.
5.4.2 Device Status
There are two methods of storing Device status data.
The driver can store the state (trouble, alarm, pre-alarm...) of each device in a separate array as a bit state
(1 or 0). See sections 5.4.9 and 5.4.10.. A separate Map Descriptor is required per zone state (9 possible).
A separate set of Map Descriptors is required for each loop (4 possible).
The driver can store a number in a separate Data Array to indicate normal or abnormal state of each
device. See section 5.4.11. All data is stored in a single Data Array and one Map Descriptor is required for
all zones.
5.4.3 Panel Information
Information about the panel itself such as evento counters, board status and LED status can be stored by the
driver. See section 5.4.12. This data is stored in consecutive array locations. Appendix D.3 maps the layout of this
data.
5.4.4 History Events
History events can be stored in two formats:
Event codes for all devices are stored in a single data array at a location based on the source device’s
address. This gives an array of the most recent events for all devices. See section 5.4.13