FieldServer Carrier DataLink FS-8700-82 Release note

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-82 Carrier DataLink
Driver Version:
1.03
Document Revision: 5

FS
-
8700
-
82 Carrier DataLink
Table of Contents
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
TABLE OF CONTENTS
1. Carrier DataLink Description..........................................................................................3
2. Driver Scope of Supply...................................................................................................4
2.1. Supplied by FieldServer Technologies for this driver ..................................................4
2.2. Provided by Suppler of 3rd Party Equipment................................................................4
3. Hardware Connections...................................................................................................5
4. Configuring the FieldServer as a Carrier DataLink Client............................................6
4.1. Data Arrays/Descriptors..............................................................................................6
4.2. Client Side Connection Descriptions...........................................................................7
4.3. Client Side Node Descriptors......................................................................................8
4.4. Client Side Map Descriptors........................................................................................8
4.4.1. FieldServer Related Map Descriptor Parameters.....................................................8
4.4.2. Driver Related Map Descriptor Parameters.............................................................9
4.4.3. Timing Parameters..................................................................................................9
4.4.4. Map Descriptor Example 1 – Read a Table ...........................................................10
4.4.5. Map Descriptor Example 2 – Read a Variable.......................................................11
4.4.6. Map Descriptor Example 3 – Write A Variable.......................................................11
4.4.7. Map Descriptor Example 4 – Write Day of Week (DOW) or Time..........................12
5. Configuring the FieldServer as a Carrier DataLink Server.........................................13
5.1. Server Side Connection Descriptors.........................................................................13
5.2. Server Side Nodes....................................................................................................14
5.3. Server Side Map Descriptors....................................................................................15
5.3.1. FieldServer Specific Map Descriptor Parameters...................................................15
5.3.2. Driver Specific Map Descriptor Parameters...........................................................15
5.3.3. Timing Parameters................................................................................................16
5.3.4. Map Descriptor Example. ......................................................................................17
5.4. Driver Limitations and Exclusions.............................................................................18
Appendix A. Advanced Topics ..........................................................................................19
Appendix A.1. Table Names...............................................................................................19
Appendix A.2. Using the Carrier Datalink Driver to Obtain Field Names .............................21
Appendix A.3. Map Descriptor Length Explained................................................................23
Appendix A.3.1. Client Reads a Table:............................................................................23
Appendix A.3.2. Client reads a variable:..........................................................................23
Appendix A.3.3. Client writes a variable:..........................................................................23
Appendix A.3.4. Server:...................................................................................................23
Appendix A.4. How the Client stores the states/values of the Table Variables....................23
Appendix A.4.1. Discrete States......................................................................................23
Appendix A.4.2. Extending the List of Discrete State Words............................................24
Appendix A.4.3. Time Values ..........................................................................................25
Appendix A.4.4. Numeric Values.....................................................................................25
Appendix A.4.5. Occupancy Strings / Values...................................................................25
Appendix A.5. Timing Considerations.................................................................................25
Appendix B. Carrier DataLink Device Error Response ....................................................26
Appendix C. Driver Notes...................................................................................................27
Appendix C.1. Driver Stats..................................................................................................27
Appendix D. Driver Error Messages..................................................................................29

FS
-
8700
-
82 Carrier DataLink
Page
3
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
1. Carrier DataLink Description
The Carrier DataLink driver allows the FieldServer to transfer data to and from devices over
either RS-232 or RS-485 using Carrier DataLink protocol. The FieldServer can emulate either a
Server or Client.
The Carrier DataLink Serial Driver allows variables to be read and written in system elements
connected to a Carrier Comfort Network communication bus. Up to 15 system elements may be
connected to a DataLink Device. Display, Occupancy, Set Point Tables and Carrier Comfort
Network (CCN) variables may be read or written.
The DataLink device provides a gateway to CCN devices. This driver polls the DataLink device
which in turn reads/writes data to the CCN devices.
Carrier limits the number of CCN devices that can polled from a DataLink Device as well as the
data that can be transferred between some CCN devices and the DataLink device. For
information on these limitations please consult the Carrier Corporation.
The driver is an active client driver. This means that it initiates read/write polls with the DataLink
device which is expected to provide responses. Server functionality is not intended to provide
full emulation of DataLink Devices but can be extended on request.
The driver is configured to allow data tables to be read from the CCN devices via the DataLink
device. As the tables typically contain more than one data element, the retrieved data is stored
in a number of consecutive FieldServer data array locations in the FieldServer. The individual
values cannot be scaled before they are stored. The driver can provide descriptions for each of
the table values retrieved. Descriptions are stored in ASCII in a separate data array.
The driver can be configured to read a specific variable from a CNN device and store its value
using optional scaling in a configurable location in a FieldServer data array.
The driver can be configured to write a value (using optional scaling) from a FieldServer data
array to a specific variable in a CNN device, provided that the variable allows its value to be
written.
The driver has no advanced knowledge of the CCN devices and their data tables. Therefore it
cannot validate table names or variable names specified in the configuration file. This means
that the driver handles each table in a generic way, without regard for the particular variables
that constitute the tables.
It is important that you understand the limitations and exclusions of this driver. Refer to Section
5.4 for more information.

FS
-
8700
-
82 Carrier DataLink
Page
4
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
2. Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART # DESCRIPTION
FS-8915-10 UTP cable (7 foot) for RS-232 use
FS-8917-17 RJ45 to DB25M connection adapter
FS-8700-82 Driver Manual.
2.2. Provided by Suppler of 3rd Party Equipment
PART # DESCRIPTION
Carrier DataLink Card

FS
-
8700
-
82 Carrier DataLink
Page
5
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
3. Hardware Connections
The FieldServer is connected to the Carrier DataLink device as shown below. Ensure that the
device to be connected to is in fact the DataLink device and not the DataPort device which is
similar looking.
Configure the DataLink Device according to manufacturer’s instructions. This driver requires
that the DataLink device’s DTPCONFIG table has been configured prior to connection with a
FieldServer. Consult the manufacturer’s information on connecting Carrier Device’s to CCN
network.

FS
-
8700
-
82 Carrier DataLink
Page
6
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
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
array can only take on one format.
FLOAT, BIT, UInt16, SInt16,
Packed_Bit, Byte,
Packed_Byte, Swapped_Byte
Data_Array_Length
Number of Data Objects. Must be
larger than the data storage area
required for the data being placed in
this array.
1-10,000

FS
-
8700
-
82 Carrier DataLink
Page
7
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Example
// Data Arrays
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length
DA_AI_01, UInt16, 200
DA_AO_01, UInt16, 200
DA_DI_01, Bit, 200
DA_DO_01, Bit, 200
4.2. Client Side Connection Descriptions
Section Title
Connections
Column Title Function Legal Values
Port Specify which port the device is connected to the
FieldServer P1-P8, R1-R21
Baud* Specify baud rate 300, 600 , 1200, 2400, 9600 (Vendor
limitation)
Parity* Specify parity. None (Vendor
Limitation)
Data_Bits* Specify data bits 8 (Vendor Limitation)
Stop_Bits* Specify stop bits 1 (Vendor limitation)
Protocol Specify protocol used CarrrierDL
Handshaking* Specify hardware handshaking None
Poll _Delay* Time between internal polls 0-32000 seconds, 1
second
Timeout* When reading entire tables it is recommended that
the timeout be set to between 15 and 30 seconds.
Additional information is provided in Appendix A.5
0.1 to 60.0 seconds,
2.0seconds
IC_Timeout* When reading entire tables it is recommended that
the ic_timeout be set to approx 15.0 seconds.
Additional information is provided in Appendix A.5
Example
// Client Side Connections
Connections
Port, Baud, Parity, Data_bits, Stop_Bits, Protocol, Handshaking, Poll_Delay
P8, 9600, None, 8 , 1 , CarrierDL, None , 0.100s
1Not 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
-
82 Carrier DataLink
Page
8
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
4.3. Client Side Node Descriptors
Section
Title
Nodes
Column
Title Function Legal Values
Node_Name Provide name for node Up to 32
alphanumeric
characters
Node_ID
Modbus station address of physical server node.
These correspond to the ‘devices’ configured in the
DTPConfig. Thus the Node_ID is not the address of
the final CCN device.
The DataLink DTPConfig table maps a device number
(1..15) to a bus number (0-239). Use the Node_ID to
tell the driver which device to use.
1-15
Protocol Specify protocol used CarrierDL
Port Specify which port the device is connected to the
FieldServer P1-P8, R1-R22
Example
// Client Side Nodes
Nodes
Node_Name, Node_ID, Protocol , Port
FAN1 , 1 , CarrierDL, P8
4.4. Client Side Map Descriptors
4.4.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric
characters
Data_Array_Name Name of Data Array where data is to be stored in the
FieldServer
One of the Data Array names
from “Data Array” section
above
Data_Array_Location Starting location in Data
Array 0 to maximum specified in “Data Array” section above
Function Function of Client Map
Descriptor RDBC, WRBC, WRBX
2Not 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
-
82 Carrier DataLink
Page
9
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
4.4.2. Driver Related Map Descriptor Parameters
Column
Title Function Legal Values
Node_Name Name of Node to fetch data from One of the node names
specified in “Client Node
Descriptor” above
Data_Type
Data type. This parameter is not required
except when defining Map Descriptors
which write DOW (Day of Week) and
Time value to the Carrier devices. When
a write Map Descriptor checks the data
type it uses the information to convert the
value extracted from the FieldServer’s
Data Arrays into a suitable format for a
write. Refer to Section 4.4.7.
-
Occupancy_Time
Occupancy_DOW
Length
Length of Map Descriptor. When reading
a compete table, set the length to the
maximum number of data values you
want stored. Additional information on the
length parameter is provided in Appendix
A.5.
1 – 1000
Address This commonly used parameter is not required for this driver.
Table_Name
The name of the table to be polled, e.g.
DISPLAY. Some system elements have
multiple instances of the same table
name. For example, the Terminal System
Manager has 64 Temperature Zone
configuration tables named TZONE1
though TZONE64. These tables are
accessed by using both the primary &
secondary table names, e.g. ‘TZCONF
TZONE1’
Only ASCII characters are
permitted.
When using the table
name parameter to specify
a primary and secondary
table, leave a single space
between the two names.
Field_Name*
If you wish to read the whole table, leave
the field name blank or specify
‘EVERYTHING’.
Only ASCII characters are
permitted. Field names
never contain spaces.
They may not be longer
than 10 characters long.
Store_As* Use the Ascii or AsciiLog format when you
are discovering the variables contained in
a table by reading a table. Refer to 1.1 Ascii, AsciiLog, Values
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled >0.1s

FS-8700-82 Carrier DataLink Page 10 of 31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
4.4.4. Map Descriptor Example 1 – Read a Table
This example illustrates how to read the entire contents of a table called ‘DISPLAY’. The Map Descriptor is connected to a node
using the node name and a node definition provides a connection to a port. Thus this Map Descriptor is connected to a port via its
node. The FieldServer will use that port to send this poll which will be generated every 5 seconds.
The value extracted from the response will be stored in the array called DA_DISPLAY. Ensure that it is suitable format for storing a
number – FLOAT is suggested. The driver stores the value of the 1
st
element at offset 1; the 2
nd
element at offset 2… The number of
table elements whose values have been successfully stored at is stored at offset zero.
// Client Side Map Descriptors
Map Descriptors
Map_Descriptor_Name,
Data_Array_Name,
Data_Array_Offset,
Function, Node_Name,
Length, Scan_Interval,
Table_Name, Field_Name
Read_Table_Md , DA_DISPLAY , 0 , rdbc , FAN01 , 100 , 5.0s , DISPLAY , EVERYTHING
By using the keyword
‘EVERYTHING’ you are
telling the driver to read
the whole table.
Responses are stored in
this data array. Table
element x gets stored at
offset x, where x is a non-
zero integer.
Offset zero is used by the
driver to report how many
values were stored.
The driver
generates a read
poll continuously.
The node name
connects the Map
Descriptor to a
node definition.
The length is set
to a number big
enough to contain
all the table’s
variables.
The name of the
table to be read.

FS-8700-82 Carrier DataLink Page 11 of 31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
4.4.5. Map Descriptor Example 2 – Read a Variable
This example illustrates how to read single variables from a Carrier Device. A Map Descriptor needs to be defined for each variable.
Reading variables is effective for reading a limited set of variables from a table(s). Scaling can be applied when the driver stores the
value by using the additional parameters: Data_Array_Low_Scale, Data_Array_High_Scale, Device_Low_Scale, Device_High_Scale
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function,
Node_Name,
Length,
Scan_Interval,
Table_Name,
Field_Name
Read_Temps_Md1 , DA_TEMPS , 0 , rdbc , FAN01 , 1 , 5.0s , DISPLAY , RAT Read_Temps_Md2 , DA_TEMPS , 1 , rdbc , FAN01 , 1 , 5.0s , DISPLAY , SAT
4.4.6. Map Descriptor Example 3 – Write A Variable
This example illustrates how to force a variable. Always set the length to 1 for a write. If the variable cannot be written then an error
will be reported. In this example the variable being written is called ‘FAN’. It can be set on/off because is a discrete point.
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Length, Scan_Interval, Table_Name, Field_Name Write_Md1 , DA_DISPLAY , 0 , wrbc , FAN01 , 1 , 5.0s , DISPLAY , FAN
As we are using the same data array for both variables,
we change the offset.
The ‘RAT’ temperature will be stored at index 0 (first
element), the SAT temperature will be stored at index 1
(2
nd
element of array).
If the first element of this array is set to 1,
the fan will be set ON;
if set to zero the fan
will be set OFF.
The pneumonic variable name.
Space Temperature -40.0 dF RAT
Supply Air Temperature -40.0 dF SAT
The variable names are supplied by the Carrier Corporation. Refer to
Appendix A.2 for assistance in determining version names.
Take care to
specify variables
that can be forced.
This function ensures that the driver
writes the Setpoint to the device
continuously (every 5 seconds in this
example.) Use WRBX to generate a
write message each time the value in
the array is updated.

FS-8700-82 Carrier DataLink Page 12 of 31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
4.4.7. Map Descriptor Example 4 – Write Day of Week (DOW) or Time
This example illustrates how to write values to an occupancy table. Occupancy tables contain amongst other variables, Day of Week
(DOW) settings and time settings. The driver needs to be configured so that it formats these values correctly.
When the DOW write occurs, the driver extracts the value from the Data Array and converts it to a binary string whose bit value is the
binary representation of the Data Array value, e.g. DA value = 131 DOW string = 10000011 e.g. DA value = 1 DOW string =
00000001
Occupancy’s are set using a BCD value. Write the value decimal equivalent of 01111100 (62 decimal) to signify an occupancy of
Monday to Friday. The bit string starts on Sunday, runs through Monday to Saturday and the final bit is for holidays.
When a time write occurs the driver extracts the value from the Data Array and coverts the value to a time string. The value extracted
from the DA is considered to be the number of minutes from midnight, e.g. DA value = 1 - Time = 00:01; DA value = 959 -
Time=15:59
Map_Descriptors Map_Descriptor_Name, Scan_interval, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Table_Name, Field_Name , Length, Data_Type MapDesc13 , 1.0s , TABLE_OCCPC64S, 100 , wrbx , Node_A , OCCDEFCS OCCPC64S, DOW3 , 1 , Occupancy_DOW MapDesc14 , 1.0s , TABLE_OCCPC64S, 101 , wrbx , Node_A , OCCDEFCS OCCPC64S, UNOCC3 , 1 , Occupancy_Time
The Data type tells the driver how
to format the value for the write.

FS
-
8700
-
82 Carrier DataLink
Page
13
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
5. Configuring the FieldServer as a Carrier DataLink Server
For a detailed discussion on FieldServer configuration, please refer to the FieldServer
Instruction 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 Client.
The FieldServer can be configured to emulate a Carrier DataLink Device. The use is able to
define a variable number of data tables, allocating a table name a variable number of variables.
The FieldServer may be polled and will respond like a DataLink device. Remote clients can
force variable states by ending write variable commands.
The FieldServer does not emulate any of the alarm buffer/history features of the DataLink
Device.
All variables may be read or written without restriction.
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 FieldServer virtual
node(s) needs to be declared in the “Server Side Nodes” section, and the data to be provided to
the clients needs to be mapped in the “Server 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.
5.1. Server Side Connection Descriptors
Section Title
Connections
Column Title Function Legal Values
Port Specify which port the device is
connected to the FieldServer P1-P8, R1-R23
Baud* Specify baud rate 300, 600 , 1200, 2400, 9600
(Vendor limitation)
Parity* Specify parity None (Vendor limitation)
Data_Bits* Specify data bits 8(Vendor limitation)
Stop_Bits* Specify stop bits 1 (Vendor limitation)
Protocol Specify protocol used CarrrierDL
Handshaking* Specify hardware handshaking None
3Not 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
-
82 Carrier DataLink
Page
14
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Example
// Server Side Connections
Connections
Port,
Baud,
Parity, Data_bits, Stop_Bits, Protocol , Handshaking, Poll_Delay
P8,
9600,
None , 8 , 1 , CarrierDL, None , 0.100s
5.2. Server Side Nodes
Section
Title
Nodes
Column
Title Function Legal Values
Node_Name Provide name for node Up to 32 alphanumeric
characters
Node_ID
Modbus station address of physical server node.
These correspond to the ‘devices’ configured in the
DTPConfig. Thus the Node_ID is not the address of
the final CCN device.
The DataLink DTPConfig table maps a device
number (1...15) to a bus number (0-239). Use the
Node_ID to tell the driver which device to use.
1-15
Protocol Specify protocol used CarrierDL
Example
// Server Side Nodes
Nodes
Node_Name, Node_ID, Protocol , Port
FAN1 , 1 , CarrierDL,
It is common to leave Server nodes
unconnected to a port. This means that the
FieldServer can respond with the node’s
data irrespective of which port the request
is receive
d on.

FS
-
8700
-
82 Carrier DataLink
Page
15
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
5.3. Server Side Map Descriptors
5.3.1. FieldServer Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric
characters
Data_Array_Name Name of Data Array where
data is to be stored in the
FieldServer
One of the Data Array names
from “Data Array” section
above
Data_Array_Location Starting location in Data Array 0 to maximum specified in
“Data Array” section above
Function Map Descriptor function Passive
5.3.2. Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fetch data from
One of the node
names specified in
“Server Node
Descriptor” above
Data_Type This commonly used parameter is not required for this driver.
Length
Length of Map Descriptor. When reading a
compete table, set the length to the maximum
number of data values to be stored. Refer to
1.1.
1 – 1000
Address This commonly used parameter is not required for this driver.
Table_Name
The name of the table to be polled, e.g.
DISPLAY. Some system elements have
multiple instances of the same table name,
e.g. the Terminal System Manager has 64
Temperature Zone configuration tables
named TZONE1 though TZONE64. These
tables are accessed by using both the
primary & secondary table names, e.g.
‘TZCONF TZONE1’
ASCII characters
only. When using
this parameter to
specify a primary
and secondary table,
leave a single space
between the two
names.
Field_Name This is the field/table variable pneumonic.
ASCII characters
only. No spaces,
maximum length 10
characters.
Field_Description
Field_Units
Returned when a client does a table read. If
units have no meaning for the variable then
leave this field blank or use a single dash.
ASCII string which
may contain spaces.
On_String
If the variable has a discrete state, use this
parameter to define the word that describes
the state when the variable’s value is 1.
OR
Use one of the keywords to tell the driver to
send the value of the associated array
elements as a number (keyword=NUMERIC),
NUMERIC
TIME
STRING
DOW
Or any other ASCII
string which may not
contain spaces.

FS
-
8700
-
82 Carrier DataLink
Page
16
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Column Title Function Legal Values
as a time value formatted as hh:mm
(keyword=TIME) or as a string of bytes
(keyword=STRING) or as an occupancy
string (keyword=DOW).
When using the string keyword the driver
reads x consecutive array elements and
treats them like ASCII character values in
forming the response. X is defined by the
length parameter.
Off_String
If the variable has a discrete state, use this
parameter to define the word that describes
the state when the variable’s value is zero. If
you have used one of the above keywords,
simply put a dash in this field.
An ASCII string
which may not
contain spaces.
Length Always set the length to 1 unless you use the
key word ‘STRING’ as the On_String
parameter. 1
5.3.3. Timing Parameters
Column Title Function Legal
Values
Scada_Hold_Timeout
Specifies time server side waits before responding
to client that node is offline on FieldServer client
side. >1.0s

FS-8700-82 Carrier DataLink Page 17 of 31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
5.3.4. Map Descriptor Example.
This example shows a number of server Map Descriptors used to define a table called ‘DISPLAY’. If a client sends a read table
request the driver responds by sending all the appropriate data for every Map Descriptor with the same table name (provided that the
node’s match).
Map_Descriptor_Name, Function, Node_Name, Table_Name, Field_Name, Field_Description,
Field_Units, On_String, Off_String, Data_Array_Name, Data_Array_Offset,
Length,
Display_MD01, passive, Node_1, DISPLAY, MODE,
Desired Mode,
, ON , OFF ,
TABLE DISPLAY, 01, 1
Display_MD02, passive, Node_1, DISPLAY, ALARM , Equipment
Status, , ALARM , NORMAL, TABLE DISPLAY, 02, 1
Display_MD03, passive, Node_1, DISPLAY, CSPT , Controlling Setp, dF, NUMERIC, -, TABLE DISPLAY, 03, 1 Display_MD04, passive, Node_1, DISPLAY, SPT , Controlling Temp, dF, NUMERIC, -, TABLE DISPLAY, 04, 1 Display_MD05, passive, Node_1, DISPLAY, RAT , Space Temp, dF, NUMERIC, -, TABLE DISPLAY, 05, 1 Display_MD06, passive, Node_1, DISPLAY, SAT , Supply Air Temp, dF, NUMERIC, -, TABLE DISPLAY, 06, 1 Display_MD07, passive, Node_1, DISPLAY, FANSTAT, Fan Mode, , ON , OFF, TABLE DISPLAY, 07, 1 Display_MD08, passive, Node_1, DISPLAY, CCAP , Cooling Capacity, % , NUMERIC, -, TABLE DISPLAY, 08, 1 Display_MD09, passive, Node_1, DISPLAY, HCAP , Heating Capacity, % , NUMERIC, - , TABLE DISPLAY, 09, 1 Display_MD10, passive, Node_1, DISPLAY, FLTSTAT, Filter Status
,
, DIRTY , CLEAN, TABLE DISPLAY, 10, 1
All the server Map
Descriptors are
passive.
If the value of the array named
TABLE_DISPLAY, offset 10 is 1
then the FieldServer will report he
FLTSTAT variable as DIRTY. If it
is zero then the variable’s state
will be reported as clean.
By using the NUMERIC
keyword, the driver is
told to report the value of
the variable HCAP as a
number. Thus the driver
sends the value of the
array named
TABLE_DISPLAY offset
9 to the client.

FS
-
8700
-
82 Carrier DataLink
Page
18
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
5.4. Driver Limitations and Exclusions
As a client:
•The Carrier DataLink driver is not capable of polling for alarm data. (The RA and AV
functions are not implemented).
•The Carrier DataLink driver dos not validate table or variable names.
•The Carrier DataLink driver does not support the Read Table command with the /C or /N
options.
•The Carrier DataLink driver records a timeout if the DataLink device does not provide the
‘?’ prompt within the user-configurable timeout period.
•Write-thru’s are not supported. The reason for this is that the driver read a composite
data set and the client side Map Descriptors do not contain enough information to format
a write.
As a server:
•The Carrier DataLink driver is not capable of serving alarm data. (RA and AV polls
produce an error response)
•The driver cannot set a discrete variable’s state unless it is set a value of one or zero.
•The driver server does not understand write table or write variable requests where the
requested state is a word like ON or OFF.
•The Carrier DataLink driver does not validate values or states, it simply stores the
values.
•All variables are may be read and written without limitation. The driver has not
implemented the Courier notion of Force Levels.
•There is no command buffer. One command can be processed at a time.
•The driver responds to all Read Table commands as if the /Y option was used. The
driver does not support the /C or /N options.
•The Carrier DataLink driver does not support the control character commands CTRL-
C/S/Q
General
•The Carrier DataLink driver is not capable of configuring the DataLink device. Software
provided by the Carrier Corporation is required to do this. The DataLink device requires
configuration, so that connects to the appropriate CCN devices on the CCN
communications network.
•The driver cannot be configured to act as what the Carrier Corporation identify as an
‘Alarm Acknowledger’.
•If the total length of the response from a read table query is more than 3000 bytes long,
the driver will produce an error.

FS
-
8700
-
82 Carrier DataLink
Page
19
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Appendix A.Advanced Topics
Appendix A.1. Table Names
The following list of table names is provided as a reference. Carrier may add tables and
new devices may become available.
Equipment Type Table Name
STATUS01
STATUS02
STATUS03
STATUS04
SETPOINT
OCCDEFCS
OCCPC01S
OCCDEFCS
OCCPC02S
17/19EX CHILLER:
OCCDEFCS
OCCPC03S
COMPRESS
CVC_PSWD
HEAT_EX
ISM_STAT
MAINSTAT
POWER
STARTUP
SETPOINT
OCCDEFCS
OCCPC01S
OCCDEFCS
OCCPC02S
23XL CHILLER:
OCCDEFCS
OCCPC03S
A_UNIT
CIRCADIO
CIRCA_AN
OPTIONS
SETPOINT
30GTNHW CHILLER:
OccDefcS
OCCPC01S
A_UNIT
CIRCADIO
CIRCA_AN
CIRCBDIO
(some units)
CIRCB_AN
(some units)
OPTIONS
30RA AQUASNAP
CHILLER:
SETPOINT
BASEUNIT
DXCOOL
39N AIR HANDLER:
ELECHEAT
Equipment Type Table Name
OPTIONS
SETPOINT
OCCDEFCS
OCCPC01S
OCCDEFCS
OCCPC02S
ECONOMZR
GENERAL
TSTAT
SETPOINT
48/50HG CENTURION
ROOFTOP: OccDefcS
OCCPC01S
DISPLAYAIR MANAGER AHU
CONTROLLER: SETPOINT
BASESYS
BYPASS
POINTS1
POINTS2
SETPOINT
CHILLERVISOR:
OCCDEFCS
OCCPC01S
POINTS
SETPOINT
COMFORTID VAV
TERMINAL CONTROL: OCCDEFCS
OCCPC64S
DISPLAY
SETPOINT
COMFORTID FAN
COIL CONTROLLER: OCCDEFCS
OCCPC64S
FSMSTAT1
FSMSTAT2
FSMSTPT
OCCDEFCS
OCCPC01S
FLOTRONIC SYSTEM
MANAGER:
OCCDEFCS
OCCPC02S
HWP01-32
HWP33-64
SWP65-96
SETPOINT
SETPT01
SETPOINT
SETPT02
50 VPAC:
SETPOINT

FS
-
8700
-
82 Carrier DataLink
Page
20
of
31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]
Equipment Type Table Name
SETPT03
SETPOINT
SETPT04
SETPOINT
SETPT05
SETPOINT
SETPT06
SETPOINT
SETPT07
SETPOINT
SETPT08
OCCPCxxC
OCCPC01
COMPRESS
CVC_PSWD
HEAT_EX
ISM_STAT
MAINSTAT
POWER
STARTUP
SETPOINT
OCCDEFCS
OCCPC01S
OCCDEFCS
OCCPC02S
19XR PIC II CHILLER:
OCCDEFCS
OCCPC03S
A_UNIT
CIRCADIO
CIRCA_AN
CIRCBDIO
CIRCB_AN
OPTIONS
SETPOINT
30GTN CHILLER:
OccDefcS
OCCPC01S
A_UNIT
CIRCADIO
CIRCA_AN
CIRCBDIO
CIRCB_AN
OPTIONS
SETPOINT
30GXNHXA CHILLER:
OccDefcS
OCCPC01S
ZONESTAT
SETPOINT
33CS VVT MONITOR: OccDefcS
OCCPC01S
DISPLAY40UV UNIT
VENTILATOR SETPOINT
STATUS0148/50F SERIES
ROOFTOP: STATUS02
Equipment Type Table Name
STATUS03
STATUS04
STATUS05
STATUS06
SETPOINT
OCCDEFCS
OCCPC01S
OCCDEFCS
OCCPC02S
STATUS01
STATUS02
STATUS03
STATUS04
STATUS05
STATUS06
SETPOINT
OCCDEFCS
OCCPC01S
48/50M SERIES
ROOFTOP:
OCCDEFCS
OCCPC02S
POINTS
SETPOINT
COMFORTID FAN
TERMINAL CONTROL: OCCDEFCS
OCCPC64S
CV_TSTAT
DXCOOL
STATUS01
STATUS02
SETPOINT
CONQUEST
ROOFTOP:
OccDefcS
OCCPC01S
CV_TSTAT
STATUS01
SETPOINT
PREMIERLINK
ROOFTOP
CONTROLLER: OCCDEFCS
OCCPC64S
BYPSSTATVVT BYPASS
CONTROLLER: SETPOINT
ZONESTAT
SETPOINT
VVT SLAVE STAT: OccDefcS
OCCPC01S
HWP01-32
HWP33-64
SWP65-96
SETPOINT
SETPT01
COMFORT
CONTROLLER
6400/1600: OCCPCxxC
OCCPC01