Map Descriptor Example 1 - Sensor / Module Events - FieldServer Gamewell FCI E3 Series Driver Manual

FS-8700-132 Gamewell FCI-E3 Driver Manual
5.4 Map Descriptor Example 1 – Sensor / Module Events
If messages from Loop 1, Module 1 to 99 are received then the Map Descriptor in this example will be used for storage. If modules occur on more than one loop, one
Map Descriptor is required per loop. In this example the event type is set to 'Alarm' so only "Alarm" events will be stored. The "Event_Type" can be changed to suit the
required data. If all events are required, the parameter should be set to "Any".
Example:
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name , Data_Array_Name
ModuleData1 , DA_MODULE
The Data Array
Unique Map
name and
Descriptor
starting location
Names are
that data should
recommended.
be stored.
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: support@fieldserver.com
, Data_Array_Offset , Function , Node_Name
, 0 , Passive_Client , Panel-01
The driver listens The name of the
passively for Node defined in
messages from Section 5.2.
the Panel. It
cannot poll for
data.
Page 9 of 20
, Event Type , Point Type , Relay/Loop/Zone Number
, Alarm , Module , 1
Only Alarm
Change this to
events will be
'Sensor' for
stored.
sensors.
, Address , Length , Clear_on_Reset
, 1 , 99 , Yes
The address specifies
the starting Module
number and the Length
tells the driver the
range of Modules.
In this example: Module
1 to 99