| Page 12 of 24 |
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 |
|
|
|
|
|
|
|
|
| Event |
| Point |
| Relay/Loop/Zone |
|
|
|
|
|
|
|
| Map_Descriptor_Name, |
| Data_Array_Name, |
| Data_Array_Offset, |
| Function, |
| Node_Name, |
|
|
|
| Address, |
| Length, |
| Clear_on_reset |
| |||
|
|
|
|
|
| Type, |
| Type, |
| Number, |
|
|
|
| ||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
| ModuleData1, | DA_MODULE, | 0, |
| Passive_Client, | Alarm, |
| Module |
| 1, | 1, | 99, |
| Yes, | ||||||||
It | is | Tell | the | driver | The | driver | The name | of | ||
recommended | the | Data | Array | listens |
|
| the | Node | ||
that | you | name | and | passively |
| for | defined | in | the | |
allocate | unique | starting location | messages | from | Node |
|
| |||
MD names. | that data should | the Panel. | It | Descriptor |
| |||||
|
| be stored. |
| cannot poll | for |
|
|
| ||
|
|
|
|
| data. |
|
|
|
|
|
In this example, | Change | this to | |
only | Alarm | ‘Sensor’ | for |
events | will be | sensors. |
|
stored. |
|
|
|
Messages reporting other events will be ignored unless other MD’s are defined.
The address specifies the starting Module number and the Length tells the driver the range of Modules.
In this example: Module 1 to 99
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)