Page 17 of 24 |
Example 2 : Action Numbers
You can have the driver store a value corresponding to the contents of the action field reported in the incoming messages. Actions are brief descriptions of the event that caused the message to be generated. A table of values vs. descriptions is provided in section 6.5. The driver stores the most recent action number, overwriting the previously stored action numbers. The driver does not keep an event log. The action number’s are set to zero, if the clear_on_reset is set to ‘yes’ and a system reset message is received.
For example, if the string ‘Fire Alarm in’ is contained in the action field of the message the driver would store an action value of 11.
This map descriptor can be used as well as the any of the map descriptors shown in previous examples. Thus you can have one (or more) map descrriptor storing the state and one storing the action number.
Map_Descriptors |
| Data_Array_Name | , | Data_Array_Offset, | Function, | node_name, | ckt | , | Length | , | Data_Type | , | Clear_on_Reset | ||
Map_Descriptor_Name, | |||||||||||||||
Ckt1128_data12 | , | DA_ACTION128 | , | 000 | , | passive , | panel1 | , | 128 | , | 127 | , | Action_Numbers , | yes | |
Using this data_Type the driver stores a value corresponding to the contents of the action field portion of the message sent by the panel. A table in section 6.5 provides a list of values vs. action descriptions.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)
