The VESDA driver allows the FieldServer to transfer data to and from devices over RS-232
using VESDA protocol. The FieldServer can emulate a VESDA Client.
The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
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.
4.1. Data Arrays
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.
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array
Data_Format Provides data format BIT,FLOAT,BYTE
4.4.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor
Name of Data Array where
Data_Array_Name
Data_Array_Location Starting location in Data Array
Function
data is to be stored in the
FieldServer. Only used for
commands 1,4,6,12.
Function of Client Map
Descriptor. A Command is a
write, and a response is a read
Up to 32 alphanumeric
characters
One of the Data Array
names from “Data Array”
section above. Must be of
type BIT
0 to maximum specified in
“Data Array” section above
RDBC, WRBC, WRBX
4.4.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
One of the node names
Node_Name Name of Node to fetch data from
Data_Type Data type Dig_input or dig_output
Length Length of Map Descriptor 1 to end of data block or less
Address Starting address of read block
Command
Network The network number 1-255
Zone The zone number
Sector The sector number
DA_Bit_Name
DA_Bit_offset
DA_Float_Name
DA_Float_offset
DA_Byte_Name
DA_Byte_offset
The command id as given in the
notes.
Name of Data Array where data
is to be stored in the FieldServer.
Used for command 10 and 16.
Starting location in Data Array.
Used for command 10 and 16
Name of Data Array where data
is to be stored in the FieldServer.
Only used for command 10.
Starting location in Data Array.
Only used for command 10
Name of Data Array where data
is to be stored in the FieldServer.
Only used for command 16.
Starting location in Data Array.
Only used for command 16
specified in “Client Node
Descriptor” above
The start bit number of the data
of interest
1,4,6,10,12,16
1-255 or 0 if the Zone is not
configured on the Panel
1-255 or 0 to read the average
smoke level and highest alarms.
One of the Data Array names
from “Data Array” section above.
Must be of type BIT
0 to maximum specified in “Data
Array” section above
One of the Data Array names
from “Data Array” section above.
Must be of type FLOAT
0 to maximum specified in “Data
Array” section above
One of the Data Array names
from “Data Array” section above.
Must be of type BYTE
0 to maximum specified in “Data
Array” section above
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Each Command on the VESDA has a particular data format.
4.5.1. VESDA data 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:
Data Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array
Data_Format Provides data format BIT
Data_Array_Length Number of Data Objects 8
Client Side Map Descriptors
Column Title Function Legal Values
Map_Descriptor_Name
Data_Array_Name
Data_Array_Location
Function
Node_Name
Data_Type Data type dig_output
Length Length of Map Descriptor 8
Address
Command
Network The network number 1-255
Zone The zone number 1-255
Sector The sector number 1-255
Up to 15 alphanumeric
characters
Name of this Map
Descriptor
Name of Data Array where
data is to be stored in the
FieldServer
Starting location in Data
Array
Function of Client Map
Descriptor.
Name of Node to fetch data
from
Starting address of read
block
The command id as given in
the notes.
Up to 32 alphanumeric
characters
As above.
0
WRBC, WRBX
One of the node names
specified in “Client Node
Descriptor” above
0
1
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.5.5. VESDA data 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:
Data Arrays 1
Column Title Function Legal Values
Data_Array_Name
Data_Format Provides data format BIT
Data_Array_Length Number of Data Objects 32
Data Arrays 2
Column Title Function Legal Values
Data_Array_Name
Data_Format Provides data format FLOAT
Data_Array_Length Number of Data Objects 32 (only first position used)
Client Side Map Descriptors
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor
Data_Array_Location
Function
Node_Name
Data_Type Data type Dig_input
Length Length of Map Descriptor 32
Address
Command The command id 10
Network The network number 1-255
Zone The zone number 1-255
Sector The sector number 1-255
DA_Bit_Name
DA_Bit_offset
DA_Float_Name
DA_Float_offset
Provide name for Data
Array
Up to 15 alphanumeric
characters
Provide name for Data
Array
Up to 15 alphanumeric
characters
Up to 32 alphanumeric
characters
Starting location in Data
Array
Function of Client Map
Descriptor
Name of Node to fetch data
from
Starting address of read
block
0
RDBC
One of the node names
specified in “Client Node
Descriptor” above
0
Name of Data Array where
data is to be stored in the
Data Array 1 name
FieldServer.
Starting location in Data
Array.
0
Name of Data Array where
data is to be stored in the
Data Array 2 name
FieldServer.
Starting location in Data
Array.
0
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.5.6. VESDA data 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:
Data Arrays 1
Column Title Function Legal Values
Data_Array_Name
Data_Format Provides data format BIT
Data_Array_Length Number of Data Objects 4
Data Arrays 2
Column Title Function Legal Values
Data_Array_Name Provide name for Data
Data_Format Provides data format BYTE
Data_Array_Length Number of Data Objects 4
Client Side Map Descriptors
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor
Data_Array_Location
Function
Node_Name
Data_Type Data type Dig_input
Length Length of Map Descriptor 4
Address
Command The command id 16
Network The network number 1-255
Zone The zone number 1-255
Sector The sector number 1-255
DA_Bit_Name
DA_Bit_offset
DA_Byte_Name
DA_Byte_offset
Provide name for Data
Array
Up to 15 alphanumeric
characters
Up to 15 alphanumeric
Array
characters
Up to 32 alphanumeric
characters
Starting location in Data
Array
Function of Client Map
Descriptor
Name of Node to fetch data
from
Starting address of read
block
0
RDBC
One of the node names
specified in “Client Node
Descriptor” above
0
Name of Data Array where
data is to be stored in the
Data Array 1 name
FieldServer.
Starting location in Data
Array.
0
Name of Data Array where
data is to be stored in the
Data Array 2 name
FieldServer.
Starting location in Data
Array.
0
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
0 Pipe1 status
1 Pipe2 status
2 Pipe3 status
3 Pipe4 status
Data Block 2 Description
BYTE offset Function
0 Airflow in pipe 1 as percentage of normalised pipe airflow.
1 Airflow in pipe 2 as percentage of normalised pipe airflow.
2 Airflow in pipe 3 as percentage of normalised pipe airflow.
3 Airflow in pipe 4 as percentage of normalised pipe airflow.
4.5.7. 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.
4.5.8. VESDA Panel start-up delay.
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.
7
1 indicates OPEN; 0 indicates CLOSE
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com