FieldServer Gamewell FCI E3 Series - Manual (Page 14)

FS-8700-132 Gamewell FCI-E3 Driver Manual Page 14 of 20
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]
Appendix C. Reference
Appendix C.1. Data Storage Methodology
All messages shorter than 102 characters are discarded unless they contain information identifying the
networked/local panel. All other messages are processed as follows:
1. The driver determines if the message is a Zone, Relay, Loop, Sensor, Module or Panel message.
2. The driver finds all Map Descriptors with matching ‘Point Type’ parameters.
3. The event category is determined.
4. Map Descriptor selection is refined based on whether the ‘Event Type’ matches or has been defined as “Any”
5. The driver determines the Loop. Relay, Zone, Sensor and Module numbers from the message and refines its
selection of Map Descriptors by selecting those that match the values determined from the message.
6. The selected Map Descriptors are now used to determine a Data Array and offset at which to store the data.
7. The driver checks the ‘Store As’ parameter. If it hasn’t been specified then ‘Index Value’ storage is assumed. If
it has been specified as ‘Bits’ then the driver will perform ‘Bit Storage’. In cases where the Map Descriptor has
both a primary and secondary Data Array, the driver will use ‘Index Value’ storage using the primary data array
and ‘Bit Storage’ using the secondary array.
Appendix C.1.1. Exam ple:
The following fragment is part of a Map Descriptor definition; some parameters have been omitted for the
purposes of clarity.
Map_Descriptors
Data_Array_Name , Data_Array_Offset , Event Type , Point Type , Relay/Loop/Zone Number , Address , Length , Clear_on_Reset , DA_Bit_Name
DA_MODU
, 0 , ANY , Module , 1 , 1 , 99 , Yes , DB_MODU
DA_MODU_A , 0 , ALARM , Module , 1 , 1 , 99 , Yes , DB_MODU_A
DA_MODU_F , 0 , FAULT , Module , 1 , 1 , 99 , Yes , DB_MODU_F
DA_MODU_T , 0 , TROUBLE , Module , 1 , 1 , 99 , Yes , DB_MODU_T
DA_MPODU_O , 0 , OTHER , Module , 1 , 1 , 99 , Yes , DB_MODU_O
Message = “FAULT: AC Power E3 0:00:04 1/01/92”
This message does not report the status of a Zone, Relay, Loop, Sensor or Module and is therefore assumed to be a
panel message. Since there is no Map Descriptor with “Point Type” Panel, the message is ignored.
Message = “TROUBLE: QZUb L1M22 << Chief's Office >> 5:24:00 3/03/93”
This message reports status for Loop 1 Module 22. Since all the MD’s in the example have a ‘Point Type’=‘Module’,
they are all considered for storage.
The driver looks in the Event Table and finds it has an index value of 34 and a category of 4 (Trouble). Only the
Map Descriptors with “Event Type” set to “Any” and “Trouble” are now considered.
Since the value of the ‘Relay/Loop/Zone’ parameter matches the Loop number in the message, these Map
Descriptors remain in contention.