| Page 6 of 31 |
4.Configuring the FieldServer as a Carrier DataLink Client
It is not possible to configure communication with a DataLink device until familiar with the data available from the devices connected to the DataLink. The DataLink device does not provide a method for discovering the data tables and variables that are available in all the Carrier devices.
In order to configure the Client it is necessary to know the names of the data tables available in the devices connected via the CCN network to the data link. A partial list of available tables is provided in Appendix A.1. If you know the table names and the variable names that you wish to poll then you have enough information to complete the configuration. If you have table names but do not know variable names then we provide a method of discovering the variable names. This method is discussed in chapter 6. If you do not have the table names then you will need to consult with the Carrier Corporation before proceeding.
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 Carrier DataLink Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable the FieldServer for Carrier DataLink 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.
4.1.Data Arrays/Descriptors
Section Title |
|
| |
Data_Arrays |
|
| |
Column Title | Function | Legal Values | |
Data_Array_Name | Provide name for Data Array | Up to 15 alphanumeric | |
characters | |||
|
| ||
Data_Format | Provide data format. Each data | FLOAT, BIT, UInt16, SInt16, | |
Packed_Bit, Byte, | |||
array can only take on one format. | |||
| Packed_Byte, Swapped_Byte | ||
|
| ||
| Number of Data Objects. Must be |
| |
Data_Array_Length | larger than the data storage area | ||
| required for the data being placed in |
| |
| this array. |
| |
|
|
|
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)
