FieldServer FS-8700-82 Configuring the FieldServer as a Carrier DataLink Client, Section Title

Page 6

FS-8700-82 Carrier DataLink

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

1-10,000

 

required for the data being placed in

 

 

this array.

 

 

 

 

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldserver.com

Page 5 Page 7
Image 6
Page 5 Page 7
Contents FS-8700-82 Carrier DataLink Table of Contents Carrier DataLink Description FS-8700-82 Carrier DataLinkProvided by Suppler of 3 rd Party Equipment FieldServer TechnologiesHardware Connections Section Title Configuring the FieldServer as a Carrier DataLink ClientData Arrays/Descriptors Column Title Function Legal ValuesNone Client Side Connection DescriptionsFS-8700-82 Carrier DataLink Example SecondClient Side Node Descriptors Column Function Legal Values TitleRDBC, WRBC, Wrbx TZONE1’ Driver Related Map Descriptor ParametersTiming Parameters ‘EVERYTHING’Map Descriptor Example 1 Read a Table Map Descriptor Example 2 Read a Variable Map Descriptor Example 3 Write a VariableMap Descriptor Example 4 Write Day of Week DOW or Time Configuring the FieldServer as a Carrier DataLink Server Server Side Connection DescriptorsServer Side Nodes Driver Specific Map Descriptor Parameters Timing Parameters Map Descriptor Example As a server Driver Limitations and ExclusionsAs a client GeneralAppendix A. Advanced Topics Appendix A.1. Table Names Equipment Type Table NameFS-8700-82 Carrier DataLink Equipment Type Table Name Dadump DEV 02 Display Appendix A.3.2. Client reads a variable Appendix A.3. Map Descriptor Length ExplainedAppendix A.3.1. Client Reads a Table Appendix A.3.3. Client writes a variableAppendix A.4.2. Extending the List of Discrete State Words FS-8700-82 Carrier DataLinkPage 24Appendix A.4.5. Occupancy Strings / Values Appendix A.4.3. Time ValuesAppendix A.4.4. Numeric Values Appendix A.5. Timing ConsiderationsAppendix B. Carrier DataLink Device Error Response Message Explanation ActionNack Appendix C. Driver Notes Appendix C.1. Driver Stats DacarrierstatsOffset Description Appendix D. Driver Error Messages Error Message ExplanationEverything FS-8700-82 Carrier DataLink Error Message Explanation This page Intentionally Left Blank
Top Page Image Contents