Page 9 of 20 | |
|
|
4.4.2.Driver Related Map Descriptor Parameters
| Column Title |
| Function |
|
|
| Legal Values |
| ||
|
|
|
|
|
|
| One | of | the | Node |
| Node_Name | Name of Node to fetch data from |
|
| Names specified in | |||||
|
|
|
|
|
|
| Section 4.3 |
| ||
|
|
| This driver uses this parameter to determine the |
|
|
|
|
| ||
|
|
| suitability of a Map Descriptor when looking for a |
|
|
|
|
| ||
|
|
| location to store data from an incoming message. |
|
|
|
|
| ||
| Event Type |
| A Map Descriptor may be defined to | store only | Any, | Other, | Fault, | |||
|
| ‘Alarm’, ‘Fault’, ‘Trouble’ or ‘Other events. | Alarm, Trouble | |||||||
|
|
| ||||||||
|
| Alternatively, specify “Any” |
|
|
|
|
|
| ||
|
| A table of events vs. categories is provided in |
|
|
|
|
| |||
|
| Appendix A.1 |
|
|
|
|
|
|
| |
|
|
| This driver uses this parameter to determine the |
| Zone, Relay, Loop, | |||||
| Point Type |
| suitability of a Map Descriptor when looking for a |
| Sensor, | Module, | ||||
|
|
| location to store data from an incoming message. |
| Panel |
|
|
| ||
|
|
| Ignored when the Point Type is ‘Panel’ |
|
|
|
|
|
| |
|
|
| Point Type = Relay 1..255 |
|
|
|
|
|
| |
| Relay/Loop/Zone |
| Point Type = Zone 1..8 |
|
| Whole Numbers | ||||
| Number |
| Point Type = Loop 1..2 |
|
| 1, 2 , etc |
|
| ||
|
|
| Point Type = Module 1..2 |
|
|
|
|
|
| |
|
|
| Point Type = Sensor | 1..2 |
|
|
|
|
|
|
|
|
| Each Map Descriptor defines storage locations for a |
| 1,2,3 .etc |
|
| |||
| Length* |
| series of addresses. | This parameter specifies the |
| Whole numbers | ||||
|
|
| length of the series. |
|
|
|
|
|
|
|
|
|
| This parameter is specific to Map Descriptors with |
|
|
|
|
| ||
|
|
| ‘Event Type’ Module or Sensor. It specifies the |
|
|
|
|
| ||
Address |
| starting Module or | Sensor number. | The length | 1..99 |
|
|
| ||
|
|
| parameter then determines the range of the |
|
|
|
|
| ||
|
|
| Sensor/Module numbers |
|
|
|
|
|
| |
|
|
| By default the driver stores using the ‘Index Value’ |
|
|
|
|
| ||
| Store As* |
| Method. If set to ‘Bit’ the driver will use the primary |
| Bit, Index_Value | |||||
|
|
| Data Array to store using the ‘Bit Storage’ Method. |
|
|
|
|
| ||
|
|
| These methods are described in Appendix A.3 |
|
|
|
|
| ||
|
|
| If the default ‘Store As’ is specified or if the |
|
|
|
|
| ||
|
|
| parameter is omitted then a secondary array can be |
| One | of | the | Data | ||
| DA_Bit_Name |
| specified using this parameter - the driver will store | Array | names | from | ||||
|
| event data as ‘Bit Storage’ in the Secondary array |
| “Data |
| Array” | ||||
|
|
|
|
| ||||||
|
|
| (and as ‘Index Values’ in the Primary array.) These |
| section above |
| ||||
|
|
| methods are described in Appendix A.3 |
|
|
|
|
|
| |
|
|
| If this parameter is specified it will prevent the Driver |
|
|
|
|
| ||
| Clear on Reset* |
| resetting the Data Array points associated with the | Yes, No |
|
| ||||
|
|
| Map Descriptor on reset. |
|
|
|
|
|
| |
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