Technologies Computer Driver Instruction Manual

FS-8700-112 FCI 7100 Series Driver Manual Page 12 of 24
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
4.5. Map Descriptor Example 1 – Sensor / Module Events
If messages from Loop 1, Module 1 to 99 are received then the MD in this example will be used for storage. If you have modules on
more than one loop then you will need one MD for each loop. In this example the event type was set to ‘Alarm’. This means that
only ‘Alarm’ events will be stored using this MD. This could be useful if you are only interested I one category of events. If you want
all events stored then change the ‘Event Type’ 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,
It is
recommended
that you
allocate unique
MD names.
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.
In this example,
only Alarm
events will be
stored.
Messages
reporting other
events will be
ignored unless
other MD’s are
defined.
Tell the driver
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
Descri
p
tor