5Configuring the FieldServer as a VESDA Client................................................................................................ 7
5.1Client Side Connection Parameters .............................................................................................................. 7
5.2Client Side Node Parameters ....................................................................................................................... 8
5.3Client Side Map Descriptor Parameters ....................................................................................................... 8
5.3.1 FieldServer Related Map Descriptor Parameters ..................................................................................... 8
5.3.2 Driver Related Map Descriptor Parameters ............................................................................................. 9
5.3.3 Map Descriptor Example ........................................................................................................................ 10
Appendix A. Useful Features ................................................................................................................................ 11
Appendix A.1. VESDA mapping format for Command 1 (Set Operation) ................................................................ 11
Appendix A.1.1. Data Arrays ............................................................................................................................ 11
Appendix A.1.2. Client Side Map Descriptors ................................................................................................... 11
Appendix A.1.3. Example .................................................................................................................................. 11
Appendix A.2. VESDA mapping format for Command 4 (Zone Update) .................................................................. 12
Appendix A.2.1. Data Arrays ............................................................................................................................ 12
Appendix A.2.2. Client Side Map Descriptors ................................................................................................... 12
Appendix A.2.3. Data Block Description ........................................................................................................... 12
Appendix A.3. VESDA mapping format for Command 6 (Remote Input) ................................................................ 14
Appendix A.3.1. Data Array .............................................................................................................................. 14
Appendix A.7.1. Data Arrays ............................................................................................................................ 24
Appendix A.7.2. Client Side Map Descriptors ................................................................................................... 24
Appendix A.8. VESDA mapping format for command 29 (Set Smoke Thresholds).................................................. 26
Appendix A.8.1. Data Arrays ............................................................................................................................ 26
Appendix A.8.2. Client Side Map Descriptors ................................................................................................... 26
Appendix A.8.3. Data Block Description ........................................................................................................... 26
Appendix B. Troubleshooting ............................................................................................................................... 28
The VESDA driver allows the FieldServer to read data from VESDA LaserPLUS controllers (FAS or FD type) via the
VESDA High Level Interface (HLI) communications module, using RS-232. The FieldServer can be used only as a
Client with this driver, and operates in the HLI Master/Slave mode.
The information that follows describes how to expand upon the factory defaults provided in the configuration files
included with the FieldServer.
2 DRIVER S C OPE OF SUPP LY
2.1 Supplied by Fiel dServer Tec hno l o gies for this D r i v er
2.2 Provided by S u p plier of 3
rd
Party Techno l o gy
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Specify which port the device is connected to the FieldServer
P1-P8, R1-R21
Baud*
Specify baud rate2
110 – 115200, standard
baud rates only. 9600
Parity*
Specify parity
None
Data_Bits*
Specify data bits
8
Stop_Bits*
Specify stop bits
1
Timeout*
Specify time allowed between poll and responses.
≤10s, 2s
IC_timeout*
This parameter monitors the time between characters in a response. If
the time exceeds the IC_Timeout the response is discarded and
considered a timeout.
0-1.0s, 0.5s
// Client Side Connections
//
Connections
Port
, Baud
, Data_bits
, Stop_bits
, Parity
, Timeout
, IC_Timeout
P1
, 9600
, 8
, 1
, None
, 10.0s
, 1.0s
1
2
5 CONFI G U RING THE F I ELDSERVER AS A VE S DA CLIEN T
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 communicate
with a Vesda Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for Vesda communications, the driver independent FieldServer buffers need to be declared in the
“Data Arrays” section, the destination device addresses need to be declared in the “Client Side Nodes” section, and
the data required from the servers needs to be mapped in the “Client Side Map Descriptors” section. Details on
how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
5.1 Client Side Co n ne c t ion Para m eters
Example:
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
Most Vesda Panels are configured for Baud 19200.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Name of Data Array where data is to be stored
in the FieldServer
Data_Array_Name defined in
Appendix A.1.1
Function
Function of Client Map Descriptor.
Wrbc, Wrbx
Node_Name
Name of Node to fetch data from
One of the Node names specified in
Section 5.2.
Data_Type
Data type
Dig_Output
Length
Length of Map Descriptor
1-16 (must not overflow the data
array)
Address*
Starting address of read block
0-15, 0
Command
The command ID
1
Network*
The network number
1-255, 0
Zone*
The zone number
1-255, 0
Sector*
The sector number
1-255, 0
Map_Descriptors
Map_Descriptor_Name
, Data_Array_Name
, Function
, Data_Type
, Node_Name
, Address
, Length
, Command
, Network
, Zone
, Sector
set_op_vesda_hli
, set_op
, Wrbc
, Dig_Output
, VESDA_HLI
, 0
, 8
, 1
, 0
, 0
, 0
Appendix A. Useful Features
Appendix A.1. VESDA mapping format for Command 1 (Set Operation)
This command is mandatory as it turns the VESDA system into a master slave relationship and is of type BIT. The
content of the data is irrelevant. The format for the data is as follows:
Appendix A.1.1. Data A r r a y s
Appendix A.1.2. Client S ide Map Descri p t ors
Appendix A.1.3. Exam p l e
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Name of Data Array where data is to be
stored in the FieldServer.
Data Array 1 name defined in Appendix
A.4.1
DA_Bit_Offset
Starting location in Data Array.
0 to (Data_Array_Length -1) as specified
in Appendix A.4.1
DA_Float_Name
Name of Data Array where data is to be
stored in the FieldServer.
Data Array 2 name defined in Appendix
A.4.2
DA_Float_Offset
Starting location in Data Array.
0 to (Data_Array_Length -1) as specified
in Appendix A.4.1
Appendix A.4. VESDA mapping format for command 10 (Update Display Status)
This request returns the Current Display Status in a split data array (2 data arrays of different type in one map
descriptor). The format for the data is as follows:
Appendix A.4.1. Data A r r a y s 1
Appendix A.4.2. Data A r r a y s 2
Appendix A.4.3. Client S ide Map Descri p t ors
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Update Display Status:
Note that the Sector is
specified as a bitmask.
For Sector 1 – Specify 128
For Sector 2 – Specify 64
For Sector 3 – Specify 32
For Sector 4 – Specify 16
Overall Smoke Level
and Highest Alarms.
(Sector must be zero)
Example
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Name of Data Array where data is to be
stored in the FieldServer.
Data Array 1 name defined in Appendix
A.6.1
DA_Bit_offset
Starting location in Data Array.
0 to (Data_Array_Length -1) as specified
in Appendix A.6.1
DA_Byte_Name
Name of Data Array where data is to be
stored in the FieldServer.
Data Array 2 name defined in Appendix
A.6.2
DA_Byte_offset
Starting location in Data Array.
0 to (Data_Array_Length -1) as specified
in Appendix A.6.1
Appendix A.6. VESDA mapping format for command 16 (Update Airflow Status)
This request returns the Current Airflow Status in a split data array (2 data arrays of different type in one map
descriptor). The format for the data is as follows:
Appendix A.6.1. Data Arrays 1
Appendix A.6.2. Data A rrays 2
Appendix A.6.3. Client S ide Map Descri p t ors
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
When the HLI is powered on the FieldServer will not be able to communicate with the Panel for 10 to 30 seconds.
During this time the HLI starts up its application code and initializes various internal parameters.
Appendix B.2. Reading Smoke Levels on the VESDA Panels
The Vesda panel only allows the driver to read the average Smoke Level on all the ports. Polling for individual
sector smoke levels will always return a value of zero.
Zone setup - If the zone on the Panel has not been configured the zone must be set to zero in the
FieldServer configuration file.
Sector setup - Setting the sector to zero will allow the driver to poll for the average smoke level.
Refer to Appendix A.4 for more information.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com