A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-43 VESDA
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Version:
1.01
Document Revision: 2
FS-8700-43 VESDA Driver Manual
Page 3 of 18
1.
VESDA Description
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.
FS-8700-43 VESDA Driver Manual
Page 4 of 18
2.
Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this Driver
FieldServer
Technologies PART #
DESCRIPTION
FS-8915-10
FS-8917-02
FS-8917-01
FS-8700-43
UTP cable (7 foot) for RS-232 use
RJ45 to DB9F connector adapter
RJ45 to DB25M connector adapter
Driver Manual
2.2.
Provided by Supplier of 3rd Party Technology
PART #
DESCRIPTION
VESDA PC Link HLI
FS-8700-43 VESDA Driver Manual
Page 5 of 18
3.
Hardware Connections
The FieldServer is connected to the Vesda as shown in connection drawing.
Configure the Vesda according to manufacturer’s instructions
LaserPlus
ETA232
FieldServer
X20/X40
VESDA HLI
LaserPlus
LaserPlus
LaserPlus
VESDAnet
(408)-262-2299
FIELDSERVER
VESDA
CONNECTION CONFIGURATIONS
BASE NAME:
FILE NAME:
DATE: 3/17/04
BY: MC
FS-8700-43 VESDA Driver Manual
Page 6 of 18
4.
Configuring the FieldServer as a VESDA 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 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
Up to 15 alphanumeric
characters
Data_Array_Name
Provide name for Data Array
Data_Format
Data_Array_Length
Provides data format
Number of Data Objects
BIT,FLOAT,BYTE
1-10000
Example:
// Data Arrays
Data_Arrays
Data_Array_Name,
set_op,
Data_Format,
bit,
float,
bit,
float,
bit,
float,
bit,
Data_Array_Length
32
32
32
32
32
32
32
32
32
VESDA01_1_f,
VESDA01_1_b,
VESDA01_2_f,
VESDA01_2_b,
VESDA01_3_f,
VESDA01_3_b,
VESDA01_4_f,
VESDA01_4_b,
float,
bit,
FS-8700-43 VESDA Driver Manual
Page 7 of 18
4.2.
Client Side Node Descriptors
Section Title
Nodes
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
VESDA
Node_Name
Protocol
Provide name for node
Specify protocol used
Example:
Nodes
Node_name,
VESDA_HLI,
Protocol,
VESDA,
Port, Timeout,
P1, 10.0s,
Recovery_Interval,
-,
Retry_Interval
-
4.3.
Client Side Connection Descriptors
Section Title
Connections
Column Title
Function
Legal Values
Specify which port the device
is connected to the FieldServer
Specify baud rate
Specify parity
Specify data bits
Port
P1-P8, R1-R21
Baud
Parity
Data_Bits
19200
None
8
Stop_Bits
Timeout
IC_timeout
Specify stop bits
Message timeout
Inter character timeout
1
10s
1.0s
Example:
// Client Side Connections
//
Connections
Port,
P1,
Baud,
19200,
Timeout,
10.0s,
IC_Timeout, Parity,
1.0s, none,
Data_bits, Stop_bits
8,
1
1
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
FS-8700-43 VESDA Driver Manual
Page 8 of 18
4.4.
4.4.1.
Client Side Map Descriptors
FieldServer Related Map Descriptor Parameters
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name Name of this Map Descriptor
Name of Data Array where
One of the Data Array
names from “Data Array”
section above. Must be of
type BIT
data is to be stored in the
Data_Array_Name
FieldServer. Only used for
commands 1,4,6,12.
0 to maximum specified in
“Data Array” section above
Data_Array_Location
Function
Starting location in Data Array
Function of Client Map
Descriptor. A Command is a
write, and a response is a read
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 specified in “Client Node
Descriptor” above
Data_Type
Length
Data type
Dig_input or dig_output
Length of Map Descriptor
1 to end of data block or less
The start bit number of the data
of interest
Address
Starting address of read block
The command id as given in the
notes.
The network number
Command
Network
Zone
1,4,6,10,12,16
1-255
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
The zone number
Sector
The sector number
Name of Data Array where data
DA_Bit_Name
DA_Bit_offset
is to be stored in the FieldServer. from “Data Array” section above.
Used for command 10 and 16.
Starting location in Data Array.
Used for command 10 and 16
Name of Data Array where data
Must be of type BIT
0 to maximum specified in “Data
Array” section above
One of the Data Array names
DA_Float_Name is to be stored in the FieldServer. from “Data Array” section above.
Only used for command 10.
Starting location in Data Array.
Only used for command 10
Name of Data Array where data
Must be of type FLOAT
0 to maximum specified in “Data
Array” section above
DA_Float_offset
One of the Data Array names
DA_Byte_Name is to be stored in the FieldServer. from “Data Array” section above.
Only used for command 16.
Starting location in Data Array.
Only used for command 16
Must be of type BYTE
0 to maximum specified in “Data
Array” section above
DA_Byte_offset
FS-8700-43 VESDA Driver Manual
Page 9 of 18
4.4.3.
Map Descriptor Example
Map_Descriptors
Map_Descriptor_Name,
set_op_vesda_hli,
Data_Array_Name, Data_Array_Offset, Function,
Data_Type, Node_Name, Address,
Length,
8,
Command,
1,
Network,
0,
Zone,
255,
Sector
-
set_op,
0,
WRBC,
dig_output,
VESDA_HLI,
0,
Map_Descriptors
Map_Descriptor_Name,
rd_vesda_01_1,
rd_vesda_01_2,
rd_vesda_01_3,
rd_vesda_01_4,
Zone,
Sector,
128,
64,
32,
16,
node_name,
VESDA_HLI,
VESDA_HLI,
VESDA_HLI,
VESDA_HLI,
Function,
DA_Bit_Name
VESDA01_1_
VESDA01_2_b
VESDA01_3_b
VESDA01_4_b
DA_Float_Name,
VESDA01_1_f,
VESDA01_2_f,
VESDA01_3_f,
VESDA01_4_f,
DA_Bit_offset,
DA_Float_offset,
Data_Array_Offset,
Data_Type,
Command,
Network,
Address,
Length
32
32
32
32
0,
0,
0,
0,
rdbc,
rdbc,
rdbc,
rdbc,
0,
0,
0,
0,
0,
0,
0,
0,
0
0
0
0
dig_input,
dig_input,
dig_input,
dig_input,
10,
10,
10,
10,
0,
0,
0,
0,
0,
0,
0,
0,
FS-8700-43 VESDA Driver Manual
Page 10 of 18
4.5.
Common Applications and Examples
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
Data_Array_Name Provide name for Data Array
Data_Format Provides data format
Function
Legal Values
Up to 15 alphanumeric
characters
BIT
8
Data_Array_Length Number of Data Objects
Client Side Map Descriptors
Column Title
Function
Name of this Map
Descriptor
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array where
data is to be stored in the
FieldServer
Data_Array_Name
As above.
Starting location in Data
Array
Function of Client Map
Descriptor.
Data_Array_Location
Function
0
WRBC, WRBX
One of the node names
specified in “Client Node
Descriptor” above
dig_output
Name of Node to fetch data
from
Node_Name
Data_Type
Length
Data type
Length of Map Descriptor
Starting address of read
block
8
0
Address
The command id as given in
the notes.
Command
1
Network
Zone
Sector
The network number
The zone number
The sector number
1-255
1-255
1-255
FS-8700-43 VESDA Driver Manual
Page 11 of 18
4.5.2.
VESDA data format for command 4 (Zone Update)
This request returns the Current Zone Status in a BIT data array. The format for the data
is as follows:
Data Arrays
Column Title
Function
Legal Values
Up to 15 alphanumeric
characters
BIT
Data_Array_Name
Provide name for Data Array
Data_Format
Provides data format
Data_Array_Length Number of Data Objects
1 - 16
Client Side Map Descriptors
Column Title
Function
Legal Values
Name of this Map
Descriptor
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array where
data is to be stored in the
FieldServer
Data_Array_Name
As above.
Starting location in Data
Array
Function of Client Map
Descriptor.
Data_Array_Location
Function
0 -16
RDBC
One of the node names
specified in “Client Node
Descriptor” above
dig_input
Name of Node to fetch data
from
Node_Name
Data_Type
Length
Data type
1-16 (must not overflow the
data array)
Length of Map Descriptor
Starting address of read
block
The command id as given in
the notes.
Address
1-16
4
Command
Network
Zone
Sector
The network number
The zone number
The sector number
1-255
1-255
1-255
Data Block Description2
BIT offset
Function
Other Zone Info
Scanning
Autolearning
Normalising
Isolated
Fault Filter
Fault Airflow
Fault Network
BIT offset
8
9
10
11
12
13
14
15
Function
0
1
2
3
4
5
6
7
Fault Power
Fault Urgent
Fault Zone
Fault System
Alarm Fire2
Alarm Fire1
Alarm Action
Alarm Alert
2 1 indicates TRUE; 0 indicates FALSE
FS-8700-43 VESDA Driver Manual
Page 12 of 18
4.5.3.
VESDA data format for command 6 (Remote Input)
This command sends the Remote Input in a BIT data array.
Data Array
Column Title
Function
Legal Values
Provide name for Data
Array
Up to 32 alphanumeric
characters
Data_Array_Name
Data_Format
Provides data format
BIT
Data_Array_Length Number of Data Objects
1 - 8
Client Map Descriptors
Column Title
Function
Name of this Map
Descriptor
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array where
data is to be stored in the
FieldServer
Data_Array_Name
As above.
Starting location in Data
Array
Function of Client Map
Descriptor.
Data_Array_Location
Function
0 –8
WRBX
One of the node names
specified in “Client Node
Descriptor” above
dig_output
Name of Node to fetch data
from
Node_Name
Data_Type
Length
Data type
1-8 (must not overflow the
data array)
Length of Map Descriptor
Starting address of read
block
The command id as given in
the notes.
Address
1-8
6
Command
Network
Zone
Sector
The network number
The zone number
The sector number
1-255
1-255
1-255
Data Block Description34
BIT offset
Function
0
1
2
3
4
5
6
7
Stop Test
Scan Start
Start Test
Silence
De-Isolate
Isolate
Reset
Reserved
3 1 indicates TRUE; 0 indicates FALSE
4 ONLY 1 OF THE 8 BITS MAY BE SET IN ONE COMMAND
FS-8700-43 VESDA Driver Manual
Page 13 of 18
4.5.4.
VESDA data format for command 12 (Current Fault Status)
This request returns the Current Fault Status in a BYTE data array. The format for the
data is as follows:
Data Arrays
Column Title
Function
Provide name for Data
Array
Legal Values
Up to 15 alphanumeric
characters
Data_Array_Name
Data_Format
Provides data format
BYTE
Data_Array_Length Number of Data Objects
1 – 21
Client Side Map Descriptors
Column Title
Function
Legal Values
Name of this Map
Descriptor
Up to 32 alphanumeric
characters
Map_Descriptor_Name
Name of Data Array where
data is to be stored in the
FieldServer
Data_Array_Name
As above.
Starting location in Data
Array
Function of Client Map
Descriptor.
Data_Array_Location
Function
0
RDBC
One of the node names
specified in “Client Node
Descriptor” above
dig_input
Name of Node to fetch data
from
Node_Name
Data_Type
Length
Data type
1-21 (must not overflow the
data array)
Length of Map Descriptor
Starting address of read
block
Address
0
The command id as given in
the notes.
Command
12
Network
Zone
Sector
The network number
The zone number
The sector number
1-255
1-255
1-255
Data Block Description5
BYTE offset
Function
0
Number of faults
Fault list
1 - 20
5 1 indicates TRUE; 0 indicates FALSE
FS-8700-43 VESDA Driver Manual
Page 14 of 18
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
Provide name for Data
Array
Up to 15 alphanumeric
characters
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
Provide name for Data
Array
Up to 15 alphanumeric
characters
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
Up to 32 alphanumeric
characters
Map_Descriptor_Name Name of this Map Descriptor
Starting location in Data
Data_Array_Location
Array
0
Function of Client Map
Descriptor
Function
RDBC
One of the node names
specified in “Client Node
Descriptor” above
Dig_input
Name of Node to fetch data
Node_Name
from
Data_Type
Length
Data type
Length of Map Descriptor
Starting address of read
block
32
0
Address
Command
Network
Zone
The command id
10
The network number
The zone number
The sector number
Name of Data Array where
data is to be stored in the
FieldServer.
1-255
1-255
1-255
Sector
DA_Bit_Name
DA_Bit_offset
Data Array 1 name
Starting location in Data
Array.
0
Name of Data Array where
data is to be stored in the
FieldServer.
Starting location in Data
Array.
DA_Float_Name
DA_Float_offset
Data Array 2 name
0
FS-8700-43 VESDA Driver Manual
Page 15 of 18
Data Block 1 Description6
BIT offset
Function
0
1
2
3
4
5
6
7
Reserved Flash
Fault Filter Flash
Fault Airflow Flash
Fault Network Flash
Fault Power Flash
Fault Urgent Flash
Fault Zone Flash
Fault System Flash
OK Flash
8
9
Isolate Flash
Fault Minor Flash
Fault Major Flash
Alarm Fire2 Flash
Alarm Fire1 Flash
Alarm Action Flash
Alarm Alert Flash
Reserved
Fault Filter
Fault Airflow
Fault Network
Fault Power
Fault Urgent
Fault Zone
Fault System
OK
Isolate
Fault Minor
Fault Major
Alarm Fire2
Alarm Fire1
Alarm Action
Alarm Alert
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Data Block 2 Description
FLOAT offset
Function
0
Average Smoke Level (Sector must be set to zero)
6 1 indicates TRUE; 0 indicates FALSE
FS-8700-43 VESDA Driver Manual
Page 16 of 18
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
Provide name for Data
Array
Up to 15 alphanumeric
characters
Data_Array_Name
Data_Format
Data_Array_Length Number of Data Objects
Provides data format
BIT
4
Data Arrays 2
Column Title
Function
Legal Values
Data_Array_Name Provide name for Data
Array
Up to 15 alphanumeric
characters
BYTE
4
Data_Format
Provides data format
Data_Array_Length Number of Data Objects
Client Side Map Descriptors
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name Name of this Map Descriptor
Starting location in Data
Data_Array_Location
Array
0
Function of Client Map
Descriptor
Function
RDBC
One of the node names
specified in “Client Node
Descriptor” above
Dig_input
Name of Node to fetch data
Node_Name
from
Data_Type
Length
Data type
Length of Map Descriptor
Starting address of read
block
4
0
Address
Command
Network
Zone
The command id
16
The network number
The zone number
The sector number
Name of Data Array where
data is to be stored in the
FieldServer.
Starting location in Data
Array.
Name of Data Array where
data is to be stored in the
FieldServer.
1-255
1-255
1-255
Sector
DA_Bit_Name
DA_Bit_offset
DA_Byte_Name
DA_Byte_offset
Data Array 1 name
0
Data Array 2 name
0
Starting location in Data
Array.
FS-8700-43 VESDA Driver Manual
Page 17 of 18
Data Block 1 Description7
BIT offset
Function
0
1
2
3
Pipe1 status
Pipe2 status
Pipe3 status
Pipe4 status
Data Block 2 Description
BYTE offset
Function
0
1
2
3
Airflow in pipe 1 as percentage of normalised pipe airflow.
Airflow in pipe 2 as percentage of normalised pipe airflow.
Airflow in pipe 3 as percentage of normalised pipe airflow.
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
FS-8700-43 VESDA Driver Manual
Page 18 of 18
THIS PAGE INTENTIONALLY LEFT BLANK
|