| 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 | Function | Legal Values | |
Data_Array_Name | Provide name for Data Array | Up to 15 alphanumeric | |
characters | |||
|
| ||
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 |
| Name of this Map |
| Up to 32 alphanumeric | |
|
|
| Descriptor |
| characters | |
|
|
| Name of Data Array where |
|
|
|
| Data_Array_Name |
| data is to be stored in the |
| As above. | |
|
|
| FieldServer |
|
|
|
| Data_Array_Location |
| Starting location in Data | 0 |
| |
|
| Array |
| |||
|
|
|
|
|
| |
| Function |
| Function of Client Map |
| WRBC, WRBX | |
|
| Descriptor. |
| |||
|
|
|
|
|
| |
|
|
| Name of Node to fetch data |
| One of the node names | |
| Node_Name |
|
| specified in “Client Node | ||
|
| from |
| |||
|
|
|
| Descriptor” above | ||
|
|
|
|
| ||
| Data_Type |
| Data type |
| dig_output | |
| Length | Length of Map Descriptor | 8 |
| ||
| Address |
| Starting address of read | 0 |
| |
|
| block |
| |||
|
|
|
|
|
| |
| Command |
| The command id as given in | 1 |
| |
|
|
| the notes. |
|
|
|
| Network |
| The network number |
| ||
| Zone | The zone number |
| |||
| Sector |
| The sector number |
| ||
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)
