Page 6 of 22 | |
|
|
4CONFIGURING THE FIELDSERVER AS A NOTIFIER NCA2/NFS2-3030 CLIENT
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (See “.csv” sample files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to receive information from a Notifier Panel.
4.1Panel Status - Memory Mapping
The primary purpose of this driver is to record the status of devices connected to the Notifier panel by interpreting the text messages sent to the printer or CRT port. Not all messages will be interpreted, as many messages do not directly pertain to device status, or are not currently supported. The following subset of event messages is recognized:
Active Events:
FIRE ALARM
SECURITY ALARM (LIFE)
LIFE CRITICAL ALARM
MEDICAL EMERGENCY
SECURITY ALARM
CRITICAL PROCESS
SUPERVISORY
TROUBLE/ FAULT
DISABLED
PREALARM
ACTIVE
ON/ OFF
This Driver divides the memory into various types. Each location in each memory type is assigned an address. It is therefore possible to map an address to a particular offset in a Data Array and make it accessible for reading by other connected devices. The address structure is provided in Table 1.
Most of these addresses will only contain binary information to represent an active or inactive state.
Where multiple troubles are associated with a single device the addressed register corresponding to that device will be incremented as a counter for each trouble message and decremented when a trouble is cleared. These addresses should preferably be stored in SINT16 format in the Data Array.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408)
