Filter
Top Products
FS-8700-132 Gamewell FCI-E3 Driver Manual Page 10 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: support@fieldserver.com
4.5. 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:
F.S.E.C. :[CR][LF]
FIRST ALARM: UP STAIRS N. ENT Manual Station L1M21 00:37:28 01/01/99[CR][LF]
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Event Type, Point Type, Relay/Loop/Zone Number, Address, Length, Clear_on_Reset
ModuleData1, DA_MODULE, 0, Passive_Client, Panel-01, Alarm, Module, 1, 1, 99, Yes
Unique Map
Descriptor
Names are
recommended.
The address
specifies the
starting Module
number and the
Length tells the
driver the range
of Modules.
In this example:
Module 1 to 99
Change this to
‘Sensor’ for
sensors.
Only Alarm
events will be
stored.
The Data Array
name and
starting location
that data should
be stored.
The driver
listens
passively for
messages from
the Panel. It
cannot poll for
data.
The name of
the Node
defined in the
Node
Descriptor