FieldServer FS-8700-86 Computer Drive User Manual

A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-86 Carrier DataPort
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after August 2008
Driver Version:
Document Revision:
1.03
11
FS-8700-86 Carrier DataPort
Table of Contents
TABLE OF CONTENTS
1.
2.
CARRIER DATAPORT DESCRIPTION ........................................................................................... 3
DRIVER SCOPE OF SUPPLY.......................................................................................................... 3
2.1.
Supplied by FieldServer Technologies for this driver ................................................................. 3
3.
4.
HARDWARE CONNECTIONS ......................................................................................................... 4
CONFIGURING THE FIELDSERVER AS A CARRIER DATAPORT CLIENT................................ 5
4.1.
Data Arrays ................................................................................................................................. 5
4.2.
Client Side Connections.............................................................................................................. 6
4.3.
Client Side Node Descriptors...................................................................................................... 7
4.4.
Client Side Map Descriptors ....................................................................................................... 8
4.4.1. FieldServer Related Map Descriptor Parameters ................................................................... 8
4.4.2. Driver Related Map Descriptor Parameters ............................................................................ 8
4.4.3. Timing Parameters .................................................................................................................. 8
4.4.4. Map Descriptor Example 1 – Read ......................................................................................... 9
5.
CONFIGURING THE FIELDSERVER AS A CARRIER DATAPORT SERVER ............................ 10
5.1.
Data Arrays ............................................................................................................................... 10
5.2.
Server Side Connections .......................................................................................................... 11
5.3.
Server Side Node Descriptors .................................................................................................. 11
5.4.
Server Side Map Descriptors .................................................................................................... 12
5.4.1. FieldServer Specific Map Descriptor Parameters ................................................................. 12
5.4.2. Driver Specific Map Descriptor Parameters .......................................................................... 12
5.4.3. Timing Parameters ................................................................................................................ 13
5.4.4. Map Descriptor Example. ...................................................................................................... 14
APPENDIX A.
ADVANCED TOPICS.................................................................................................... 15
Appendix A.1.
Field Status & Field Engineering Units....................................................................... 15
Appendix A.2.
Field / Variable Names ............................................................................................... 16
Appendix A.3.
Map Descriptor Length Explained .............................................................................. 19
Appendix A.4.
How the Client stores the states/values of the Table Variables................................. 19
Appendix A.4.1.
Discrete States........................................................................................................ 19
Appendix A.4.2.
Time Values ............................................................................................................ 20
Appendix A.4.3.
Numeric Values....................................................................................................... 21
Appendix A.4.4.
Occupancy Strings / Values.................................................................................... 21
APPENDIX B.
Appendix B.1.
Appendix B.2.
Appendix B.3.
Appendix B.4.
TROUBLE SHOOTING/CONNECTIONS - TIPS AND HINTS ..................................... 22
Connection problems. ................................................................................................ 22
Timeouts..................................................................................................................... 22
Determining Storage Locations .................................................................................. 22
How to build a script file that tests a customer log. .................................................... 23
APPENDIX C.
DRIVER NOTES ........................................................................................................... 26
Appendix C.1.
Driver Limitations and Exclusions .............................................................................. 26
APPENDIX D.
DRIVER ERROR MESSAGES ..................................................................................... 27
Appendix D.1.
Driver Stats ................................................................................................................ 31
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
1.
Page 3 of 32
Carrier DataPort Description
The Carrier DataPort driver allows the FieldServer to transfer data to and from devices over either RS232 or RS-485 using Carrier DataPort protocol. The FieldServer can emulate either a Server or Client.
The DataPort device provides a gateway to CCN devices. This driver polls the DataPort device which in
turn reads data from the CCN devices. Up to 15 system elements may be connected to a DataPort
Device.
Carrier limits the number of CCN devices that can polled from a DataPort Device and also limits the data
that can be transferred between some CCN devices and the DataPort device. For information on these
limitations please consult the Carrier Corporation.
The driver is an active Client driver. This means that it initiates read polls with the DataPort device which
is expected to provide responses. Server functionality is provided by the driver too.
The driver is configured to allow a single Data Table (usually the Display Table) to be read from the CCN
devices via the DataPort device. As the table typically contains more than one data element, the
retrieved data is stored in a number of consecutive Data Array locations in the FieldServer. The driver
can provide descriptions for each of the table values retrieved.
The driver has no advanced knowledge of the CCN devices and their Data Tables. This means that the
driver handles each table in a generic way, without regard for the particular variables that constitute the
tables. The most important consequence of this is that the variable values are stored in the order in
which they appear in the response from the DataPort device. It is not possible to map particular variable
values to particular locations in the FieldServer Data Arrays.
2.
Driver Scope of Supply
2.1.
Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART #
FS-8917-02
FS-8917-17
SPA59132
FS-8700-86
DESCRIPTION
RJ45 to DB9F connector adapter
RJ45 to DB25M connection adapter
RS-485 connection adapter
Driver Manual.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
3.
Page 4 of 32
Hardware Connections
The FieldServer is connected to the Carrier DataPort device as shown below.
Configure the DataPort Device according to manufacturer’s instructions. This driver requires that the
DataPort device’s DTPCONFIG table has been configured prior to connection with a FieldServer. In
addition, consult the manufacturer’s information on connecting Carrier Device’s to CCN network.
Note: Typical connections are 9600,N,8,1.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
4.
Page 5 of 32
Configuring the FieldServer as a Carrier DataPort Client
It is not possible to complete a configuration for communication with a DataPort device until you are
familiar with the data available from the devices connected to the DataPort. The DataPort device does not
provide a method for discovering the data tables and variables that are available in all the Carrier devices.
Configuring the DataPort driver as a Client is easy; however, you will not be able to complete the server
side configuration until you have a list of the variables and the order in which the DataPort device will
report them. The driver is capable of helping you determine this information but cannot auto-complete the
configuration. This method is discussed in Appendix A.
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 DataPort Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to
enable the FieldServer for Carrier DataPort 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
Section Title
Data_Arrays
Column Title
Data_Array_Name
Function
Provide name for Data Array
Data_Format
Provide data format. Each Data Array
can only take on one format.
Data_Array_Length
Number of Data Objects. Must be larger
than the data storage area required for
the data being placed in this array.
Legal Values
Up to 15 alphanumeric characters
FLOAT, BIT, UInt16, SInt16,
Packed_Bit, Byte, Packed_Byte,
Swapped_Byte
1-10,000
Example
// Data Arrays
//
Data_Arrays
Data_Array_Name,
DA_AI_01,
DA_AO_01,
DA_DI_01,
DA_DO_01,
Data_Format,
UInt16,
UInt16,
Bit,
Bit,
Data_Array_Length
200
200
200
200
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
4.2.
Page 6 of 32
Client Side Connections
Section Title
Connections
Column Title
Baud*
Specify baud rate.
Parity*
Data_Bits*
Specify parity
Specify data bits
Legal Values
P1-P8, ( R1, R2 with
1
converter)
600 , 1200, 2400, 9600
(Vendor limitation)
None (Vendor limitation)
8 (Vendor limitation)
Stop_Bits*
Specify stop bits.
1 (Vendor limitation)
Protocol
Handshaking*
Specify protocol used
Specify hardware handshaking
Poll _Delay*
Time between internal polls
CarrierDP
None
0-32000
second
Port
Function
Specify which port the device is connected to the
FieldServer
seconds,
1
Specifies the max amount of time the driver must
wait for a complete response.
Timeout
2
Application
Start_Method*
If the Data Port table is long then increase the
timeout above the default until timeout errors
disappear.
Refer to notes in Appendix B.3
If the parameter is not configured or set to 0
(default), the driver will identify the start of a
message as FORMFEED (0x0C) and the end as two
carriage returns (0x0D 0x0D)
When the parameter is set to 1, the first carriage
return (0x0D) will be considered the start of the
message (all characters before the first carriage
return will be ignored). and the end as two carriage
returns (0x0D 0x0D)
2 seconds
Print_storage_locations
1,0
Example
//
Client Side Connections
Connections
Port, Baud,
P8,
9600,
Parity,
None,
Data_Bits,
8
,
Stop_Bits,
1
,
Protocol ,
CarrierDP,
Handshaking,
None
,
Poll_Delay
0.100s
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.
2
See Appendix B.1 for additional information
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
4.3.
Page 7 of 32
Client Side Node Descriptors
Section
Title
Nodes
Column
Title
Node_Name
Function
Legal Values
Provide name for node
Up
to
alphanumeric
characters
32
These correspond to the ‘devices’ configured in the
DTPConfig. Thus the Node_ID is not the address of the final
CCN device.
Node_ID
Protocol
Port
1-15
The DataPort 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.
Specify protocol used
Specify which port the device is connected to the FieldServer
CarrierDP
3
P1-P8, R1-R2
Example
//
Client Side Nodes
Nodes
Node_Name,
FAN1 ,
Node_ID,
1
,
Protocol ,
CarrierDP,
Port
P8
3
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
4.4.
Page 8 of 32
Client Side Map Descriptors
4.4.1.
FieldServer Related Map Descriptor Parameters
Column Title
Map_Descriptor_Name
Data_Array_Name
Function
Name of this Map Descriptor
Name of Data Array where data is
to be stored in the FieldServer
Data_Array_Location
Starting location in Data Array
Function
Function of Client Map Descriptor
4.4.2.
Legal Values
Up to 32 alphanumeric characters
One of the Data Array names from
“Data Array” section above
0 to maximum specified in “Data
Array” section above
Rdbc, Wrbc, Wrbx
Driver Related Map Descriptor Parameters
Column Title
Function
Node_Name
Name of Node to fetch data from
Data_Type
This commonly used parameter is not
required for this driver.
Length
Address
Store_As*
Length of Map Descriptor. When reading a
compete table, set the length to the
maximum number of data values you want
stored.
Legal Values
One of the node names
specified in “Client Node
Descriptor” above
1 – 1000
Additional information on the length
parameter is provided in Appendix A.3.
This commonly used parameter is not required for this driver.
Use the ASCII or AsciiLog format when
you are discovering the variables
ASCII, AsciiLog, Values
contained in a table by reading a table.
Refer to Appendix A for more information.
DA_Byte_Name*
If defined, the driver stores the ‘field status’
value in this array.
DA_Float_Name*
If defined, the driver stores the ‘field units’
value in this array.
4.4.3.
Timing Parameters
Column Title
Scan_Interval
Function
Rate at which data is polled
The name of a Data Array
defined in the Data_Array
section of the configuration file.
The name of a Data Array
defined in the Data_Array
section of the configuration file.
Legal Values
>0.1s
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
Map Descriptor Example 1 – Read
Page 9 of 32
The
driver
generates a read
poll continuously.
Function,
Rdbc
,
The Node_Name
connects the Map
Descriptor to a
Node definition.
Data_Array_Offset,
0
,
Length,
100 ,
The length is set
to a number big
enough to contain
all
the
table’s
variables.
Node_Name,
FAN01 ,
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
Offset zero is used
by the driver to
report how many
value were stored.
Responses
get
stored in this Data
Array.
Table
element
x gets
stored at offset x,
where x is a nonzero integer.
Data_Array_Name,
Da_Display ,
Client Side Map Descriptors
Map Descriptors
Map_Descriptor_Name,
Read_Table_Md
,
//
Scan_Interval
5.0s
The values extracted from the response will be stored in the array called DA_DISPLAY. Ensure that it is suitable format for storing number –
st
nd
FLOAT is suggested. The driver stores the value of the 1 element at offset 1, the 2 element at offset 2 ….and the driver stores the number of
table elements whose values have been successfully stored at offset zero.
Some basics first: The Map Descriptor is connected to a node by means of 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. The poll will be generated every 5
seconds in this example.
This example illustrates how to read data from the DataPort.
4.4.4.
FS-8700-86 Carrier DataPort
FS-8700-86 Carrier DataPort
5.
Page 10 of 32
Configuring the FieldServer as a Carrier DataPort Server
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 DataPort Client.
The FieldServer can be configured to emulate a Carrier DataPort Device. The user is able to define a
variable quantity of variables. The FieldServer may be polled and will respond like a DataPort device.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order
to enable the FieldServer for Carrier DataPort 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.
Data Arrays
Section Title
Data_Arrays
Column Title
Function
Data_Array_Name
Provide name for Data Array
Data_Format
Provide data format. Each Data Array can
only take on one format.
Data_Array_Length
Number of Data Objects. Must be larger
than the data storage area required for
the data being placed in this array.
Legal Values
Up
to
15
alphanumeric
characters
Float,
Bit,
Uint16,
Sint16,
Packed_Bit, Byte, Packed_Byte,
Swapped_Byte
1-10,000
Example
// Data Arrays
//
Data_Arrays
Data_Array_Name,
DA_AI_01,
DA_AO_01,
DA_DI_01,
DA_DO_01,
Data_Format,
Uint16,
Uint16,
Bit,
Bit,
Data_Array_Length
200
200
200
200
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
5.2.
Page 11 of 32
Server Side Connections
Section Title
Connections
Column Title
Port
Function
Specify which port the device is connected to
the FieldServer
Legal Values
P1-P8, ( R1-R2 with converter)
4
Baud*
Specify baud rate
Parity*
Data_Bits*
Specify parity
Specify data bits
300, 600 , 1200, 2400, 9600
(Vendor limitation)
None (Vendor limitation)
8 (Vendor limitation)
Stop_Bits*
Specify stop bits
1 (Vendor limitation)
Protocol
Specify protocol used
Specify hardware handshaking
CarrierDP
None
Handshaking*
Example
//
Server Side Connections
Connections
Port,
Baud,
P8,
9600,
5.3.
Parity,
None,
Data_Bits,
8
,
Stop_Bits,
1
,
Protocol ,
CarrierDP,
Handshaking,
None
,
Poll_Delay
0.100s
Server Side Node Descriptors
Section Title
Nodes
Column Title
Node_Name
Function
Legal Values
Up to 32 alphanumeric
characters
Provide name for Node
DataPort station address of physical Server Node.
Node_ID
These correspond to the ‘devices’ configured in the
DTPConfig. Thus the Node_ID is not the address of
the final CCN device.
1-15
Protocol
The DataPort 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.
Specify protocol used
CarrierDP
Example
//
Server Side Nodes
Nodes
Node_Name,
FAN1 ,
Node_ID,
1
,
Protocol ,
CarrierDP,
Port
P8
5
4
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
5
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 received on.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
5.4.
Page 12 of 32
Server Side Map Descriptors
5.4.1.
FieldServer Specific Map Descriptor Parameters
Column Title
Map_Descriptor_Name
Data_Array_Name
Function
Name of this Map Descriptor
Name of Data Array where data is
to be stored in the FieldServer
Data_Array_Location
Starting location in Data Array
Function
Function of Client Map Descriptor
5.4.2.
Driver Specific Map Descriptor Parameters
Column Title
Node_Name
Length
Legal Values
Up to 32 alphanumeric characters
One of the Data Array names from
“Data Array” section above
0 to maximum specified in “Data
Array” section above
passive
6
Table_Name*
Function
Name of Node to fetch data from
Length of Map Descriptor. When reading a
compete table, set to the maximum number of
data values to be stored.
The name of the table to be polled, e.g.
DISPLAY. This parameter is for display purposes
only. The driver does not use the value of this
parameter.
Some system elements have multiple instances
of the same table name. For example, the
Terminal System Manager has 64 Temperature
Zone configuration tables. The individual tables
are named TZONE1 though TZONE64. These
tables are accessed by using both the primary &
secondary table names.
Legal Values
One of the Node Names
specified in “Server
Node Descriptor” above
1 – 1000
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.
E.g. ‘TZCONF TZONE1’
6
Field_Name
This is the field variable pneumonic.
Field_Description
Returned when a Client does a read.
Field_Units
Returned when a Client does a read. If units
have no meaning for the variable set to zero.
Field Status*
This parameter is used to set data quality
information that is returned when the Client polls
for data. If omitted and DA_Byte_Name has not
been specified the driver returns zero as the
status value.
An Ascii string which
may not contain spaces.
Max length 8 characters.
An Ascii string which
may contain spaces.
Max
length
24
characters.
A whole number. See
Appendix A.1
A whole number. See
Appendix A.1 for more
information.
Additional information on the length parameter is provided in Appendix A.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Column Title
DA_Byte_Name*
On_String
Off_String
Length
5.4.3.
Page 13 of 32
Function
If this parameter is defined then its value must be
the name of a Data Array. Instead of the driver
returning a static Field Status, it will extract the
value located at the given offset and use this
value as the Field Status.
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:
NUMERIC – a number
TIME - a time value formatted as hh:mm
STRING - a string of bytes
DOW – occupancy string
When using the string keyword the driver reads x
consecutive array elements and treats them as
ASCII character values in forming the response.
X is defined by the length parameter.
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 a keywords described above then
simply put a dash in this field.
Always set the length to 1 unless you use the key
word ‘STRING’ as the On_String parameter.
Legal Values
The name of Data Array
defined in the Data
Arrays section.
NUMERIC
TIME
STRING
DOW
Or any other Ascii string
which may not contain
spaces.
An ASCII string which
may not contain spaces.
1
Timing Parameters
Column Title
Function
Scada_Hold_Timeout
Specifies time Server side waits before responding to Client
that node is offline on FieldServer Client side.
Legal
Values
>1.0s
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
Map Descriptor Example.
Page 14 of 32
Node_Name,
Node_1,
Node_1,
Node_1,
Node_1,
Node_1,
Node_1,
Node_1,
Node_1,
Node_1,
Node_1,
Field_Name,
MODE
,
ALARM
,
CSPT
,
SPT
,
RAT
,
SAT
,
FANSTAT,
CCAP
,
HCAP
,
FLTSTAT,
Field_Description,
Desired Mode ,
Equipment Status,
Controlling Setp.,
Controlling Temp,
Space Temp,
Supply Air Temp.,
Fan Mode,
Cooling Capacity,
Heating Capacity,
Filter Status,
Field_Units,
,
,
dF
,
dF
,
dF
,
dF
,
,
%
,
%
,
,
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.
Table_Name,
DISPLAY,
DISPLAY,
DISPLAY,
DISPLAY,
DISPLAY,
DISPLAY,
DISPLAY,
DISPLAY,
DISPLAY,
DISPLAY,
On_String,
ON
,
ALARM ,
NUMERIC ,
NUMERIC,
NUMERIC ,
NUMERIC,
ON,
NUMERIC,
NUMERIC,
DIRTY,
Off_String,
OFF
,
NORMAL,
-,
-,
-,
-,
OFF
,
,
,
CLEAN ,
Data_Array_Offset,
01
,
02
,
03
,
04,
05,
06,
07,
08,
09,
10,
Length,
1,
1,
1,
1,
1,
1,
1,
1,
1,
1,
If the value of the array named
TABLE_DISPLAY, offset 10 is a 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.
Data_Array_Name,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
TABLE_DISPLAY,
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
All the Server Map
Descriptors
are
passive.
Function,
passive,
passive,
passive,
passive,
passive,
passive,
passive,
passive,
passive,
passive,
Server Side Map Descriptors
Map Descriptors
Map_Descriptor_Name,
Display_MD01,
Display_MD02
,
Display_MD03
,
Display_MD04
,
Display_MD05
,
Display_MD06
,
Display_MD07
,
Display_MD08
,
Display_MD09
,
Display_MD10
,
//
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 too. ). The fields
are returned in the order in which you define them in the configuration file.
5.4.4.
FS-8700-86 Carrier DataPort
FS-8700-86 Carrier DataPort
Page 15 of 32
Appendix A. Advanced Topics
Appendix A.1.
Field Status & Field Engineering Units
The following tables duplicate information available from Carrier Corporation. We provide it for
reference purposes. It is best to ask the vendor for current data.
Value Engineering Units
000
no units
Value Engineering Units
Value
051
feet per minute
260
thousands of cubic feet
052
262
per minute
thousands of cubic feet
053
263
per hour
054
tons
264
055
tons per hour
267
056
revolutions per minute
270
057
percent open
272
058
hours
273
059
gallons
274
064
on/off input
276
065
off/on input
288
066
input pulses on
289
067
input pulses off
290
068
seconds
291
069
normal/alarm
292
070
Hz
293
080
minutes
295
081
hours
296
082
revolutions per minute
297
124
clock
298
001
degrees F
002
degrees F
003
004
005
006
007
008
010
011
013
014
015
016
017
018
020
032
033
percent
inches of water
milliamps
delta degrees F
degrees F
delta degrees F
Volts
degrees F
percent
inches of water
milliamps
delta degrees F
degrees F
delta degrees F
pounds per square inch
gallons per minute
gallons per hour
thousands of gallons per
126
minute
thousands of gallons per
128
hour
pounds per square inch,
133
gauge
pounds per hour
137
thousands of pounds per
138
hour
BTUs per hour
144
thousands of BTUs
145
inches of water
146
inches of mercury
192
kilowatt hours
193
kilowatts
194
degrees F
195
percent relative humidity 208
amps
254
volts
256
cubic feet per minute
257
cubic feet per hour
258
034
035
036
037
038
039
040
041
042
043
044
045
046
047
048
049
050
Engineering Units
Pascal
delta degrees C
degrees C
delta degrees C
degrees C
Pascal
delta degrees C
degrees C
delta degrees C
kiloPascals
liters per minute
liter per hour
cubic meters per minute
cubic meters per hour
kiloPascals
kilograms per hour
kilowatt hours
kilowatts
millimeters of water
millimeters of mercury
ASCII
299
kilowatt hours
no units
300
kilowatts
milliamp
301
degrees C
pounds per square inch
302
percent relative humidity
volts
303
amps
kilowatts
kilowatt hours/pulse
pulses
on/off output
off/on output
pulsed on output
pulsed off output
steps
ASCII
no units
degrees C
degrees C
304
305
306
307
310
311
312
313
314
315
volts
cubic meters per minute
cubic meters per hour
meters per second
tons
tons per hour
revolutions per hour
percent open
hours
liters
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Error Conditions
Conditions
No Force
Fire
Safety
Service Tool
Supervisor
Monitor
Minimum-off
Control
BEST
Temp Override
Loadshed
Page 16 of 32
A
0
16
32
48
64
80
96
112
128
144
160
B
1
17
33
49
65
81
97
113
129
145
161
Force Conditions
C
D
2
3
18
19
34
35
50
51
66
67
82
83
98
99
114
115
130
131
146
147
162
163
E
4
20
36
52
68
84
100
116
132
148
164
F
5
21
37
53
69
85
101
117
133
149
165
Error Conditions:
A
no error
B
hardware or communications error
C
software error
D
low alarm limit exceeded (analog point),or point in alarm (discrete point)
E
high alarm limit exceeded
F
unconfigured point (VVT Gateway only)
Force Conditions:
No Force
Fire
Safety
Service Tool
Supervisor
Monitor
Minimum-off
Control
BEST
Temp Override
Loadshed
Appendix A.2.
forced by fire alarm equipment
forced by internal safety override
forced by CCN Service Tool
forced by local Building Supervisor
forced by remote Building Supervisor
forced by minimum off time requirement
forced by System Software Option
forced by BEST program
forced by temperature override
forced by Loadshed System Software Option
Field / Variable Names
A list of variable names vs. table names vs. equipment types is not provided in this manual. The
reasons for this are that they are not all available to us they can be configured in some devices using
software provided by the Carrier Corporation.
Consult the points list with the literature provided with each type of equipment from Carrier to obtain
variable names. Alternately use the software provided by Carrier to browse the network and
determine the table and variable names.
This driver may also be used to obtain a list of variable names for a given table. On the following
pages are sample Map Descriptors which may be included in the configuration to help obtain this
information. FieldServer recommends that if these Map Descriptors are used to obtain variable name
information, they should be removed from the final configuration as they will consume resource and
processing time.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
Page 17 of 32
Function,
rdbc
,
Node_Name,
FAN01 ,
Length,
1000 ,
Storet_As
ASCII
This is what tells the
driver to dump the
table, its variables
names and variable
descriptions in ASCII
format.
Scan_Interval,
5.0s
,
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
The s=Data Array DA_DUMP has been
defined with format BYTE. When viewing
this table with RUINET display the array
in ‘STRING’ format so that you can read
it.
Data_Array_Offset,
0
,
Data_Array_Length
2000
Data_Array_Name,
DA_DUMP
,
Data_Format,
BYTE,
Map Descriptors
Map_Descriptor_Name,
Md1
,
Data_Arrays
Data_Array_Name,
DA_DUMP,
This example illustrates how to create a Map Descriptor which reads a table and dumps the response in ASCII format to a Data Array so that
RUINET( a utility provided with the FieldServer) can be used to browse and read the results.
FS-8700-86 Carrier DataPort
Page 18 of 32
Function,
rdbc
,
Node_Name,
FAN01 ,
Length,
1000 ,
Scan_Interval,
5.0s
,
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
T01> ASCII Dump Requested for MD=<MapDesc1>
T01> Field1 99.0
000 000 Desc1 1 1
T01> Field2 98.0
000 000 Desc2222222
T01> Field3
on 000 000 33333 33333 3
T01> Field4
Off 000 000 44444444444444
T01> Field5
Off 000 000 5555 55555555
T01> Field6
Off 000 000 6666666666666
T01> Field7
Off 000 000 7
T01> Field8
Off 000 000 888 888 88888
T01> Field9
Off 000 000 99999999999 3
T01> Fielda
DIRTY 000 000 aaaaaaaaaaaaa
T01> Fieldb 0.0
000 000 bbbb
T01> Fieldc
Off 000 000 c
T01> Fieldd -1.0
000 000 ddddddddddddd
The following fragment from the error log is typical of the response to a Map Descriptor like the one above.
Data_Array_Offset,
0
,
Data_Array_Length
2000
Data_Array_Name,
Da_Dump
,
Data_Format,
BYTE,
Map Descriptors
Map_Descriptor_Name,
Md1
,
Data_Arrays
Data_Array_Name,
DA_DUMP,
Storet_As
AsciiLog
This example illustrates how to make a Map Descriptor which reads a table and dumps the response in ASCII format to the error log. The error log
can be dumped to a file on your computer using RUIDEBUG (a utility supplied with your FieldServer)
FS-8700-86 Carrier DataPort
FS-8700-86 Carrier DataPort
Appendix A.3.
Page 19 of 32
Map Descriptor Length Explained
The Length parameter is specified as part of the Map Descriptor.
Client Reads:
The length means: “The number of table variable’s whose values are to be stored when the response
is received.” If you do not know the length of the table in advance, set the length to a larger number
(e.g. 100). The driver will process the response; if the table contains more than 100 elements then
some data will be discarded.
Server:
The length parameter is used when the server returns a value that is a string. The length is used to
tell the driver how many characters to extract from consecutive array location to form the response
string. When the server returns a value that is a number, state or time the length should always be 1.
Appendix A.4.
How the Client stores the states/values of the Table Variables.
Appendix A.4.1.
Discrete States
When a Carrier DataPort device reports the state of a table variable which has a discrete state, it
reports the state as a keyword like on/off. This driver converts the keywords to facilitate reading
by other devices.
The driver is programmed to recognize the keywords listed below. The user can add keywords
by specifying additional information in the configuration file.
State Word
CLEAN
DIRTY
HEAT
COOL
ON
OFF
Value
1
0
1
0
1
0
State Word
ABNORMAL
NORMAL
LOCAL
REMOTE
LOCAL R
RUNNING
Value
1
0
0
1
0
1
State Word
OPEN
CLOSE
CLOSED
ALARM
Value
1
0
0
1
If the driver doesn’t recognize the state word, it stores the characters of the state word as decimal
values based on their ASCII value. the number of characters stored is dependent on the length
parameter.
For example, say the driver responds, reporting a variable to be a state ‘INCREDIBLE’. If the
length parameter of the polling Map Descriptor is 1 then the driver stores the first character of the
word incredible; by storing a value of 73 (An uppercase ‘I’ is the seventy third character in the
ASCII alphabet.).
st
The driver recognizes discrete state words by checking the 1 character of the value field. If it is a
non-digit then it is regarded as a state word. The comparison against keywords in the list is done
without respect for the case of the letters.
Unrecognized Discrete State Words
If the driver does not recognize the discrete state word that has been used it will report the
following error - CarrDP:#24 Err. MD=<MapDesc1> discrete state word not recognized.
The unrecognized discrete word can be found by extracting 10 characters from the line starting at
the 10th character. Once the 10 characters have been extracted they are left and right trimmed
to remove leading and trailing spaces.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Page 20 of 32
In the following two examples the keywords that are not recognized are 'Reset T' and 'Tripout'
respectively
CarrDP:#24 Err. MD=<MapDesc1> discrete state word not recognized.
T02>
<MODE
Reset T 000 000 Control Mode
>
T02> CarrDP:#24 Err. MD=<MapDesc1> discrete state word not recognized.
T02>
<STATUS Tripout 000 000 Run Status
>
In the following example the keyword '********' is not being recognized. If this message is printed
it is necessary to consult Carrier Corp. to learn why a variables’ value is printed as '********'. It
may be that the value is over range or invalid.
T02> CarrDP:#24 Err. MD=<MapDesc1> discrete state word not recognized.
T02>
<CHWPD ********** 020 000 Chilled Water Delta P
>
T02>
Extending the List of Discrete State Words
You can extend the list of state words the driver recognizes by modifying the configuration CSV
file.
The following example adds three state words. If a device reports the state of the variable as
LIGHT then the driver will store the value of 1, if on the other hand the state is reported as DARK
then the driver will store the value zero.
State Words
Keyword
starts a new
section
of
the CSV file.
The name will be
stripped of all
spaces between the
last character and
the comma.
Driver_Table
Carrier_Attr_State_Name,
LIGHT
,
DARK
,
Normally the values
will be 1/0 for the
on/off states but the
driver
does
not
restrict the value.
Carrier_Attr_State_Value,
1
,
0
,
Protocol must
be defined on
every line.
Protocol
CarrierDP
CarrierDP
This method may be used to change the values of any of the driver’s default state words by
duplicating the word and specifying a new value in the configuration file.
Appendix A.4.2.
Time Values
If the driver receives a variable value reported in the format hh:mm then the driver stores a
number obtained by multiplying the hours by 60 and adding the minutes. The driver recognizes a
rd
st
time value by checking the 3 character for a colon and checking that the 1 character is a digit.
Value_Stored = hh * 60 + mm
E.g. 5:30pm is reported as 17:20 and is stored as 17*60 + 20 = 1040.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Appendix A.4.3.
Page 21 of 32
Numeric Values
The driver recognizes numeric values by checking the first character of the value field. If it is a
digit then the field is treated as a number.
Appendix A.4.4.
Occupancy Strings / Values
If the value returned for a variable is 8 characters long and each of the characters is a one or a
zero then the driver regards this as an occupancy string an converts it to a binary coded decimal
value and then stores this value.
E.g.: 00101010 = 42 decimal
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Page 22 of 32
Appendix B. Trouble Shooting/Connections - Tips and Hints
Appendix B.1.
Connection problems.
Confirm that the device you are trying to attach to the FieldServer is in fact a DataPort device and not
a DataLink device which looks very similar but connects differently.
A DataLink device will require the DataLink driver – FieldServer part # FS-8700-82. Please contact
FieldServer to request an exchange of driver.
Appendix B.2.
Timeouts
Some Data Port tables are long and result in messages of up to 6.5 kB being sent from the data port
to the FieldServer. The default timeout is insufficient in such cases.
In resolving one customer’s connection problems a timeout of 4 s on a table of 134 entries was found
to produce good results.
Please read the notes provided with Error message #25 in section Appendix D of this manual.
Appendix B.3.
Determining Storage Locations
Set the Application parameter to ‘Print_storage_locations’ on the connection to tell the driver to print
messages each time it stores data. The driver dumps messages in the error log reporting the Data
Array name, offset, value and the ‘line’ from which the data was extracted.
Remove the parameter to stop the messages being printed.
Example:
In the line below the driver reports that the line beginning ‘hd_pos_a…..’ was processed and that the
value 0.0 was stored in DA_D2_01 at offset 149.
T02> DPStore:DA=DA_D2_01 Off=49 Val=0.00 <hd_pos_a 0.0
T02> See above===>hd_pos_a 0.0
003 000 Head Press A
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Appendix B.4.
Page 23 of 32
How to build a script file that tests a customer log.
The following brief notes are intended for configuration engineers who are expected to be familiar
with the FieldServer.
•
•
•
•
Take the hex log file and convert to ASCII using special chars (this is an option of the log file
converter)
Choose a response line from near the end of the log (most recent). Check the line is complete.
Place the line inside an INI file. Make the following changes
• Replace [NP] with [FF]
• Replace [SP] with a space
• Replace [NULL] with a space.
Use the following files as a guide.
Client.csv
Data_Arrays
Data_Array_Name,
DA_D1_01,
Connections
Port ,
P1,
Parity,
None,
Nodes
Node_Name,
Node_A ,
Data_Format,
Float,
Baud,
9600,
Node,
1,
Map_Descriptors
Map_Descriptor_Name,
CMD_GP_01,
Data_Bits,
8,
Protocol,
CarrierDP,
Data_Array_Name,
DA_D1_01,
Data_Array_Length
500
Stop_Bits,
1,
Handshaking,
None,
Protocol,
CarrierDP,
Timeout,
60s,
Print_storage_locations
Yes
Port
P1
Data_Array_Offset,
0,
Function,
Rdbc,
Node_Name,
Node_A,
Length,
202,
Scan_Interval,
5.0s
Server.csv
Data_Arrays
Data_Array_Name,
TABLE_DISPLAY,
Connections
Port ,
P1,
Parity,
None,
Nodes
Node_Name,
Node_A ,
Node,
1,
Data_Format,
Float,
Baud,
1200,
Data_Array_Length
500
Data_Bits,
8,
Stop_Bits,
1,
Handshaking,
None,
Protocol,
CarrierDP,
Protocol,
CarrierDP,
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
Data_Array_Name,
TABLE_DISPLAY,
Data_Array_Offset,
0,
Function,
Passive,
Node_Name,
Node_A,
Table_Name,
DISPLAY,
Field_Name,
Field1,
Field_Description,
Desc1 1 1,
Page 24 of 32
Field_Units,
Length,
202,
On_String,
NI°UMERIC,
Off_String,
-,
Length
1
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
[FF]
0
000 000 GENERAL PARAMETERS
[CR]
0
000 000
[CR]ctr_type Remote 000 000 Control Type
[CR]status
Off 000 000
Run Status
[CR]CHIL_S_S 0
000 000 CCN Chiller Start/Stop [CR]CHIL_OCC 1
000 000 Chiller Occupied?
[CR]MIN_LEFT 1.0
000 000 Minutes Left for
Start [CR]HC_SEL 0
000 000 Heat/Cool Select
[CR]RECL_SEL 0
000 000 Heat Reclaim Select [CR]
0
000 000
[CR]ALM
Normal
000 000 Alarm State
[CR]alarm_1 0
000 000 Current Alarm 1
[CR]alarm_2 0
000 000 Current Alarm 2
[CR]alarm_3 0
000 000 Current Alarm 3
[CR]alarm_4 0
000 000 Current Alarm 4
[CR]alarm_5 0
000 000 Current Alarm 5
[CR]
0
000 000
[CR]CAP_T 0
003 000
Percent Total Capacity [CR]DEM_LIM 100
003 000 Active Demand Limit Val [CR]LAG_LIM 100
003 000 Lag Capacity Limit Value[CR]SP
46.4
001 000 Current
Setpoint
[CR]SP_OCC 1
000 000 Setpoint Occupied?
[CR]CTRL_PNT 46.4
001 000 Control Point
[CR]CTRL_WT 47.7
001 000 Controlled Water Temp
[CR]OAT
48.8
001 000 External Temperature [CR]
0
000 000
[CR]EMSTOP 0
000 000 Emergency Stop
[CR]
0
000 000
CIRCUIT A ANALOG VALUES [CR]
0
000 000
[CR]CAPA_T 0
003 000 Percent Total Capacity [CR]DP_A 45.7
020 000 Discharge Pressure
[CR]SP_A 43.2
020 000 Suction Pressure
[CR]CPA1_OP 45.9
020 000 Oil Pressure Cp1
[CR]CPA2_OP 45.4
020 000 Oil Pressure Cp2
[CR]DOP_A1
2.5
020 000 Oil Press Difference Cp1[CR]DOP_A2 2.1
020 000 Oil Press Difference Cp2[CR]CPA1_ECP 43.3
020 000 Economizer Pressure Cp1 [CR]CPA2_ECP 43.3
020 000 Economizer Pressure Cp2 [CR]SCT_A 50.1
001 000 Saturated Condensing Tmp[CR]SST_A 48.0
001 000 Saturated Suction Temp [CR]CPA1_DGT 48.1
001
000 Discharge Gas Temp Cp 1 [CR]CPA2_DGT 48.6
001 000 Discharge Gas Temp Cp 2 [CR]dt_a 48.6
001 000 Average Discharge Gas Tp[CR]CPA1_TMP 48.0
001
000 Motor Temperature Comp 1[CR]CPA2_TMP 47.5
001 000 Motor Temperature Comp 2[CR]CPA1_CUR 0
047 000 Motor Current Comp 1 [CR]CPA2_CUR 0
047
000 Motor Current Comp 2 [CR]EXV_A 0.0
003 000 EXV Position
[CR]hd_pos_a 0.0
003 000 Head Press Actuator Pos [CR]PINCH_A -0.3
006 000 Cooler
Exchange Delta T [CR]MTQ_RESA 8.7
000 000 Motor Cool TQ in Kohms [CR]CPA1_PUL 30
000 000 Motor Cooling Puls Cycle[CR]
0
000 000 CIRCUIT A
DISCRETE
[CR]
0
000 000
[CR]CP_A1 0
000 000 Compressor 1 Output
[CR]cpa1_mc1 0
000 000 Cp1 Mtr Cool Solenoid
1[CR]cpa1_mc2 0
000 000 Cp1 Mtr Cool Solenoid 2[CR]cpa1_ols 0
000 000 Cp1, Oil Solenoid Out [CR]CP_A2 0
000 000 Compressor 2 Output [CR]cpa2_mc1
0
000 000 Cp2 Mtr Cool Solenoid 1[CR]cpa2_mc2 0
000 000 Cp2 Mtr Cool Solenoid 2[CR]cpa2_ols 0
000 000 Cp2, Oil Solenoid Out [CR]ldr_1_a 0
000 000
Cir A, Loader 1 Output [CR]ldr_2_a 0
000 000 Cir A, Loader 2 Output [CR]oil_h_a 1
000 000 Cir A, Oil Heater Output[CR]oil_l_a 1
000 000 Cir A, Oil Level Input
[CR]oilpmp_a 0
000 000 Cir A, Oil Pump Output [CR]refa_iso 0
000 000 Cir A Refrig Isolate Out[CR]
0
000 000
[CR]
0
000 000 FANS
OUTPUT
[CR]fan_a1 0
000 000 Fan Output DO # 1
[CR]fan_a2 0
000 000 Fan Output DO # 2
[CR]fan_a3 0
000 000 Fan Output DO # 3
[CR]fan_a4 0
000 000 Fan Output DO # 4
[CR]fan_a5 0
000 000 Fan Output DO # 5
[CR]fan_a6 0
000 000 Fan Output DO # 6
[CR]fan_a7 0
000 000 Fan Output DO # 7
[CR]fan_a8 0
000 000 Fan Output DO # 8
[CR]FAN_ST_A 0
000 000 Fan Staging Number
[CR]
0
000 000 CIRCUIT B
ANALOG VALUES [CR]
0
000 000
[CR]CAPB_T 0
003 000 Percent Total Capacity [CR]DP_B 45.3
020 000 Discharge Pressure
[CR]SP_B
43.1
020 000 Suction Pressure
[CR]CPB1_OP 44.2
020 000 Oil Pressure Cp1
[CR]CPB2_OP 0.0
020 000 Oil Pressure Cp2
[CR]DOP_B1 1.3
020 000
Oil Press Difference Cp1[CR]DOP_B2 0.0
020 000 Oil Press Difference Cp2[CR]CPB1_ECP 42.9
020 000 Economizer Pressure Cp1 [CR]CPB2_ECP 42.9
020 000
Economizer Pressure Cp2 [CR]SCT_B 49.7
001 000 Saturated Condensing Tmp[CR]SST_B 47.8
001 000 Saturated Suction Temp [CR]CPB1_DGT 48.6
001 000
Discharge Gas Temp Cp 1 [CR]CPB2_DGT 0.0
001 000 Discharge Gas Temp Cp 2 [CR]dt_b
48.6
001 000 Average Discharge Gas Tp[CR]CPB1_TMP 48.1
001 000
Motor Temperature Comp 1[CR]CPB2_TMP 0.0
001 000 Motor Temperature Comp 2[CR]CPB1_CUR 0
047 000 Motor Current Comp 1 [CR]CPB2_CUR 0
047 000
Motor Current Comp 2 [CR]EXV_B 0.0
003 000 EXV Position
[CR]hd_pos_b 0.0
003 000 Head Press Actuator Pos [CR]PINCH_B -0.3
006 000 Cooler
Exchange Delta T [CR]MTQ_RESB 8.5
000 000 Motor Cool TQ in Kohms [CR]CPB1_PUL 30
000 000 Motor Cooling Puls Cycle[CR]
0
000 000 CIRCUIT B
DISCRETE
[CR]
0
000 000
[CR]CP_B1 0
000 000 Compressor 1 Output
[CR]cpb1_mc1 0
000 000 Cp1 Mtr Cool Solenoid
1[CR]cpb1_mc2 0
000 000 Cp1 Mtr Cool Solenoid 2[CR]cpb1_ols 0
000 000 Cp1, Oil Solenoid Out [CR]CP_B2 0
000 000 Compressor 2 Output [CR]cpb2_mc1
0
000 000 Cp2 Mtr Cool Solenoid 1[CR]cpb2_mc2 0
000 000 Cp2 Mtr Cool Solenoid 2[CR]cpb2_ols 0
000 000 Cp2, Oil Solenoid Out [CR]ldr_1_b 0
000 000
Cir B, Loader 1 Output [CR]ldr_2_b 0
000 000 Cir B, Loader 2 Output [CR]oil_h_b 1
000 000 Cir B, Oil Heater Output[CR]oil_l_b 1
000 000 Cir B, Oil Level Input
Server.ini (all one single line)
Map_Descriptors
Map_Descriptor_Name,
Server.ini,
// When the Map Descriptor name contain ".ini" then this is assumed to be a file
// name and the file is read and xmitted byte for byte with the following exceptions.
//
When a square bracket is encountered then this is assumed to contain a special char
//
The special chard is sent and not the square brackets and its contents.
// Only one line is read. The first
// The line must be less than 20k bytes
FS-8700-86 Carrier DataPort
Page 25 of 32
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
[CR]oilpmp_b 0
000 000 Cir B, Oil Pump Output [CR]refb_iso 0
000 000 Cir B Refrig Isolate Out[CR]
0
000 000
[CR]
0
000 000 FANS
OUTPUT
[CR]fan_b1 0
000 000 Fan Output DO # 1
[CR]fan_b2 0
000 000 Fan Output DO # 2
[CR]fan_b3 0
000 000 Fan Output DO # 3
[CR]fan_b4 0
000 000 Fan Output DO # 4
[CR]fan_b5 0
000 000 Fan Output DO # 5
[CR]fan_b6 0
000 000 Fan Output DO # 6
[CR]fan_b7 0
000 000 Fan Output DO # 7
[CR]fan_b8 0
000 000 Fan Output DO # 8
[CR]FAN_ST_B 0
000 000 Fan Staging Number
[CR]
0
000 000 UNIT
DISCRETE IN
[CR]onoff_sw 0
000 000 Remote On/Off Switch [CR]hc_sw 0
000 000 Remote Heat/Cool Switch [CR]recl_sw 0
000 000 Remote Reclaim
Switch [CR]sept_sw 0
000 000 Remote Setpoint Switch [CR]limit_sw 0
000 000 Limit Switch Status [CR]lock_1 0
000 000 Interlock Status
[CR]pump_def 0
000 000 Pump Run Status
[CR]condflow 0
000 000 Condenser Flow Status [CR]elec_box 1
000 000 Electrical Box Safety Sw[CR]
0
000 000
[CR]
0
000 000 UNIT DISCRETE OUT
[CR]CLPUMP_1 0
000 000 Cooler Pump #1 Command [CR]CLPUMP_2 0
000 000 Cooler Pump #2 Command
[CR]ROT_PUMP 0
000 000 Rotate Pumps Now
[CR]COND_PMP 0
000 000 Condenser Pump Command [CR]COOLHEAT 0
000 000 Cooler Heater Command
[CR]SAFE_ALM 0
000 000 Critical Alarm Signal [CR]
0
000 000
[CR]
0
000 000 UNIT ANALOG
[CR]COOL_EWT 48.0
001 000
Cooler Entering Fluid [CR]COOL_LWT 47.7
001 000 Cooler Leaving Fluid [CR]COND_EWT 0.0
001 000 Condenser Entering Fluid[CR]COND_LWT 0.0
001 000
Condenser Leaving Fluid [CR]CHWSTEMP -40.7
001 000 CHWS Temperature
[CR]EXT_VDC 0.0
010 000 External 0-10 Vdc Signal[CR]COND_SP 104.0
001 000
Current Cond Setpoint [CR]tot_curr 0
047 000 Chiller Total Current [CR]
0
000 000 RECLAIM ANALOG PARAM [CR]HR_EWT 0.0
001 000 Reclaim
Entering Fluid [CR]HR_LWT 0.0
001 000 Reclaim Leaving Fluid [CR]hr_sp 104.0
001 000 Reclaim Fluid Setpoint [CR]sct_a_sp 118.4
001 000 Cir A SCT Control Point
[CR]sct_b_sp 118.4
001 000 Cir B SCT Control Point [CR]pmpd_p_a 0.0
020 000 Cir A Pumpdown Pressure [CR]pmpd_p_b 0.0
020 000 Cir B Pumpdown Pressure
[CR]hr_v_pos 20.0
003 000 HR Cond Valve Position [CR]
0
000 000
[CR]
0
000 000 RECLAIM DISCRETE PARAM [CR]RECL_SEL 0
000 000 Heat Reclaim Select
[CR]condflow 0
000 000 Condenser Flow Status [CR]hr_val_a 0
000 000 Cir A Reclaim Valve Stat[CR]hr_val_b 0
000 000 Cir B
Reclaim Valve Stat[CR]pd_val_a 0
000 000 A Pumpdown Valve Status [CR]pd_val_b 0
000 000 B Pumpdown Valve Status [CR]hrstat_a 0
000 000 Circuit A Reclaim
Status[CR]hrstat_b 0
000 000 Circuit B Reclaim Status[CR]cond_htr 1
000 000 Reclaim Condenser Heater[CR]
0
000 000 OPERATING MODES
[CR]Mode[07] 0
000 000 Startup Delay in effect [CR]Mode[08] 0
000 000 Second Setpoint in Use [CR]Mode[09] 0
000 000 Reset in Effect
[CR]Mode[10] 0
000 000 Demand Limit Active
[CR]Mode[11] 0
000 000 Ramp Loading Active
[CR]Mode[12] 0
000 000 Low Source Protection [CR]Mode[13] 0
000 000 Low
Cooler Suction Cir A[CR]Mode[14] 0
000 000 Low Cooler Suction Cir B[CR]Mode[15] 0
000 000 Low Dis Superheat Cir A[CR]Mode[16] 0
000 000 Low Dis Superheat
Cir B[CR]Mode[17] 0
000 000 High Pres Override Cir A[CR]Mode[18] 0
000 000 High Pres Override Cir B[CR]Mode[19] 0
000 000 High Current Over Cir A
[CR]Mode[20] 0
000 000 High Current Over Cir B [CR]Mode[21] 0
000 000 Reclaim Active?
[CR]Mode[22] 0
000 000 Cooler Heater Active? [CR]Mode[23] 0
000 000 Cooler Pumps Rotation? [CR]Mode[24] 0
000 000 Pump Periodic Start? [CR]Mode[25] 0
000 000 Night Capacity Active? [CR]Mode[26] 0
000 000 System
Manager Active? [CR]Mode[27] 0
000 000 Master Slave Active? [CR][CR]
//only 1st line is used
FS-8700-86 Carrier DataPort
FS-8700-86 Carrier DataPort
Page 26 of 32
Appendix C. Driver Notes
Appendix C.1.
Driver Limitations and Exclusions
The Carrier DataPort driver does not support the following functions. Send Data Periodically, Stop
Sending, Xoff, Xon, Omit 24 Character description, Include 24 Character description, Read
Configuration.
The Carrier DataPort driver is not capable of configuring the DataPort device. Software provided by
the Carrier Corporation is required to do this. The DataPort device requires configuration, so that it
connects to the appropriate CCN devices on the CCN communications network.
If the total length of the response from a read table query is more than 3000 bytes long, the driver will
produce an error.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Page 27 of 32
Appendix D. Driver Error Messages
The driver reports information and errors to you in the form of messages printed to the error log. Those
messages marked with a * are only printed once even if they occur repeatedly.
Error Message
CarrierDP:1
FYI.
The
MapDesc called <%s> is too
short
CarrierDP:2 FYI. You could
have used a MapDesc
called <%s> to expose
diagnostic info.
CarrierDP:3
Err.
Illegal
Node_ID=%d Valid=1..15
CarrierDP:4 FYI. Address
has no meaning. Best set to
0 MapDesc=<%s>
CarrDP:#5 Err. DataPort is
read only. No wrbc/x.
MapDesc=<%s>
CarrDP:#6 Err. Fieldname
max
length
=8.
MapDesc=<%s>
CarrDP:#7 Err. Field Desc.
max
length
=%d.
MapDesc=<%s>
CarrierDP:8 Err. Length
required. MapDesc=<%s>
CarrierDP:9 FYI. Duplicate
state=<%s>. Value has
been updated from=%d
to=%d
CarrierDP:10 Err. No space.
Driver
rejects
value
state=<%s> value=%d
CarrierDP:11 FYI. User
added value state=<%s>
value=%d
CarrierDP:12 Err. Length
too short to store all.
MD=<%s>
Explanation
The length of the Map Descriptor used to expose driver statistics is too
short. Set the length to at least 1000 by editing the CSV file. Then reset
the FieldServer. You can ignore this message if you wish – the driver will
abandon statistics which require the length of the Map Descriptor to be
increased.
You can safely ignore this message. It is a prompt. Read Appendix D.1 of
this manual for more information.
Valid node numbers are in the range 1 to 15 inclusive. Read section 4.3
*
for more information.
You can safely ignore this message. The address parameter is
commonly used in FieldServer configurations but it has no meaning in
the configuration of this driver. It is best to remove the parameter from
*
the configuration or set its value to 0.
The Carrier DataPort device is read only. You cannot have a Map
Descriptor which writes to the device. Delete the Map Descriptor or
*
changing it to a read
You can use no more than 8 characters to define a field name and no
*
more than 24 to define the field description.
The length parameter must be set in the configuration file and it must be
set to a value greater than zero. Appendix A.3 provides additional
*
information.
You have specified a discrete state word in the configuration file which
duplicates one already in the list. The driver uses the new value specified
in the CSV file to replace the previous value. Thus it is possible to
change the values for the driver’s default discrete state words. You can
safely ignore this message; it is for your information only.
The driver has limited space to store discrete state keywords added in
the configuration file. The maximum is 150 words including the driver’s
defaults. Remove some of the keywords you have added to the
*
configuration file
You can safely ignore this message; it is for your information only. Each
time a new discrete state word is added to the driver from the
configuration file, the driver reports the new word and its value.
The driver reports that the read table command resulted in more
variables being returned than you have reserved space for (with the
*
length parameter). Increase the length parameter.
*
Correct the error by editing the configuration CSV file, downloading the corrected file to the FieldServer
and then resetting the FieldServer.
*
Correct the error by editing the configuration CSV file, downloading the corrected file to the FieldServer
and then resetting the FieldServer.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Error Message
CarrierDP:13
FYI.
Diagnostic send error #1
response.
CarrierDP:14
FYI.
Diagnostic cancelled slave
response
CarrDP:#15 Err. Field Units
required. MapDesc=<%s>
CarrDP:#16
FYI.
Use
DA_Byte_Name for server
status values. MD=<%s>
CarrDP:#17
FYI.
Use
DA_Byte_Name for 'status'
value storage. MD=<%s>
CarrDP:#18
FYI.
Use
DA_Float_Name for 'units'
value storage. MD=<%s>
CarrDP:#19
Err.
'Table_Name'
has
no
meaning. MapDesc=<%s>
CarrDP:#20
Err.
'Field_Name'
has
no
meaning. MapDesc=<%s>
Page 28 of 32
Explanation
These messages are for FieldServer engineers. If any either is ever
printed in the error log please call FieldServer support and report the
message.
A server side Map Descriptor requires that the Engineering units are
defined. More information about this field is provided in section 0 and
Appendix A.1
This message may be safely ignored. It is provided for your information
only. It reminds you that you can use a secondary Data Array connected
to the server side Map Descriptor to store ‘status’ value which will be
returned when the server is polled. This is an alternate way of allowing
the driver to determine the ‘status’ values. More information on status
values is provided in Appendix A.1
This message may be safely ignored. It is provided for your information
only. It reminds you that you can use a secondary Data Array connected
to the Client side Map Descriptor to have the driver store ‘status’ value
when a poll response is obtained. If this secondary array is not defined
then the status values are ignored. More information on status values is
provided in Appendix A.1
This message may be safely ignored. It is provided for your information
only. It reminds you that you can use a secondary Data Array connected
to the Client side Map Descriptor to have the driver store ‘engineering
units’ values when a poll response is obtained. If this secondary array is
not defined then the ‘units’ values are ignored. More information on ‘units’
values is provided in Appendix A.1
On the Client side the parameters ‘Table_Name’ and ‘Field_Name’ have
*
no meaning and must be removed from the Map Descriptor.
CarrDP:#21 Err. 'On_String'
required. MapDesc=<%s>
CarrDP:#22
'Field_Name'
MapDesc=<%s>
CarrDP:#23
'Field_Desc'
MapDesc=<%s>
Err.
required.
On the server side, each Map Descriptor must have these parameters
defined. Read section 0 and review the example in section 1.1.1 for more
*
information.
Err.
required.
CarrDP:#24 Err. MD=<%s>
discrete state word not
recognized.
CarrDP:#25 Err. This driver
On the line immediately following this error the driver reports the
response that generated the error. The driver will store a value that is the
ASCII code for the first character of the discrete state reported.
Identification of the unrecognized discrete state word as well as
information on how to extend the list of recognized discrete state words is
*
provided in Appendix A.4.1.
The length of the response from each different Carrier device and for
*
Correct the error by editing the configuration CSV file, downloading the corrected file to the FieldServer
and then resetting the FieldServer.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Error Message
works
best with
timeouts.
long
CarrDP:#26 FYI. No data
was stored for MD=%s
CarrDP:#27 Err. Can’t open
slave.log
CarrDP:#28 FYI. Response
was sent from slave.log
(Hex file)
Page 29 of 32
Explanation
each table is different. The driver does not know the length of the
responses. The Carrier devices take some time between receiving a poll
and sending a response. The amount of time is proportional to the length
of the response (and hence, to the size of the table.) If the device takes
too long the driver may timeout as the default timeout is 2.0 seconds. It is
strongly recommended that you set the timeout to a large value (like 30
seconds) to start with. The effect of having a large timeout is to
1) allow the driver enough time to receive the response and
2) Increase the amount of time before the driver reports the timeout if
there is a genuine timeout event.
This message is printed when a response is received but the driver did
not find any information in the response that it could use to store. If the
problem occurs repeatedly then take a log and call tech Support after you
have tried the following diagnostic steps. 1) Check connection stats – If
bytes received per message is < 100 then it is likely that the device you
are polling is not responding properly or that a port setting is invalid.
Check the port settings.
This message should only be printed in simulation mode (QA testing). If
you see this message call Tech Support.
This message should only be printed in simulation mode (QA testing). If
you see this message call Tech Support.
This message could be produced when the characters which signal the
end of a response are missing and the next response is appended to the
st
1 in the input buffer. In such cases the buffer may overflow.
This message is printed once and then suppressed. However each time
the event occurs, the STREAMING stat is incremented by one.
CarrDP:#29 Err. The input
buffer has overflowed.
If the stat is produced rarely then you could assume that that an
occasional corrupt/incomplete message has produced the error.
If it occurs all the time, then assume that the response is too large to fit in
the input buffer.
CarrDP: #30
CarrDP:#31 Err. Line has
missing CR. Some data not
stored
CarrDP:#32
Err.
Many
missing CR's. Abandon
store... MD=%s
Most FST drivers have an input buffer of 3080 bytes This driver has a
buffer size of 16000 bytes. The buffer size is hard coded so you will need
to capture a log and send an error report to FST.
When parsing a response, the driver processes the response line by line.
A single response may consist of a number of lines. Each line is
terminated with a Carriage Return (CR). If a single CR is missing then
the driver sees two lines as a single line. In versions prior to 1.03eA the
driver used the line number as the offset, therefore values extracted from
subsequent lines were stored at the incorrect offset. Now the driver
ignores the corrupted line and advances the line counter by 2 continuing
the parsing and storing of extracted values. The values associated with
the corrupted response line are not updated. This is reflected in the line
count stored at offset zero. The driver detects lines with missing CR's by
checking the line length. If the driver senses that more than two or more
consecutive CR's are missing then the driver abandons the parse and
store and prints error #32. If different parts of the response have missing
CR's message #31 will be printed more than once per response. There
is no direct corrective action you can take. The errors arise from dropped
bytes in the response. If the error occurs frequently you will need to
check that the data transmission is not being adversely affected by noise.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Error Message
Page 30 of 32
Explanation
There DataPort device responded but the response reports an error. The
error number is printed in the message. The message also reports the
name of the node that was polled.
The following 6 errors are documented. For other errors contact the
Carrier Vendor.
#1 Invalid Command : The digit 1 returned as an error code means that
the last ASCII character sent to the DATAPORT by the off-network
device is not one that the DATAPORT recognizes as a command.
#2 No Display Table : The digit 2 returned as an error code means that
the off-network device has commanded the DATAPORT to transmit data
from a controller that is properly configured in the DATAPORT, but the
controller does not contain a point display table.
CarrDP:#33 Err. DataPort
responded with Err=%d.
Device=%s
#3 CCN Bus Communication Error: The digit 3 returned as an error code
means that the DATAPORT cannot transmit data from the requested
controller because a communication error occurred while the
DATAPORT was acquiring data from that controller.
#4 Database Full : The digit 4 returned as an error code means that the
off-network device has commanded the DATAPORT to transmit data
from a controller that is properly configured in the DATAPORT, but the
controller is beyond the 900 point limit. For example, if controllers 1
through 10 each contain 90 points, a command for the DATAPORT to
transmit data from controller 11, 12, 13, 14, or 15 will result in error code
4.
#5 DATAPORT Busy : The digit 5 returned as an error code means that
a static data update is in progress, preventing the DATAPORT from
responding successfully to a Send Controller Data Command or a Send
Data Periodically command.
#6 Controller Not Configured : The digit 6 returned as an error code
means that the off-network device has commanded the DATAPORT to
transmit data from a controller that is not configured in the DATAPORT.
For example, if only controllers 1 through 5 are configured in the
DATAPORT, a command of 0 (Send Controller Data for Controller 15)
will result in error code 6.
CarrDP:#99 Err. Cant open
INI file for response.
This message should only be printed in simulation mode (QA testing). If
you see this message call Tech Support.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Appendix D.1.
Page 31 of 32
Driver Stats
The driver reports statistics according to the FieldServer standards. The following notes describe
some aspects of standard statistic reporting which are peculiar to this driver.
•
All error responses from the Carrier DataPort device are recorded as PROTOCOL ERRORS,
In addition to the standard FieldServer communication statistics described above and in the
FieldServer Instruction Manual, this driver can also expose some driver statistics by writing data to a
Data Array. A special Map Descriptor is required. The driver recognizes the Map Descriptor by its
name which must be "CarrierDP-stats”.
The following example shows how this special Map Descriptor can be configured. You can copy this
section of text directly into your CSV file.
Nodes
Node_Name ,
CarrDP_stats ,
Station,
1
,
Protocol
CarrierDP
Data_Arrays
Data_Array_Name ,
DA_CARRIERDP_STATS ,
Data_Format,
UINT32 ,
Data_Array_Length
2000
Map_Descriptors
Map_Descriptor_Name,
CarrierDP-Stats ,
Data_Array_Name ,
DA_CARRIERDP_STATS,
Data_Array_Offset,
0
,
Function,
passive ,
Node_Name ,
CarrDP_stats,
Length,
500
When the driver sees this Map Descriptor it uses the Data Array DA_CARRIER_STATS (in this
example) to store driver specific statistics. Only one of these Map Descriptors may be specified per
FieldServer.
The driver stores the following data. The location in the Data Array is obtained by multiplying the
port number by 50 and then using the location offset indicated in the table below.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8700-86 Carrier DataPort
Page 32 of 32
Array Offset is based on Port Number
P1 P2 P3 P4 P5 P6 P7
0
50
100 150 200 250 300
1
51
101 151 201 251 301
2
52
102 152 202 252 302
3
53
103 153 203 253 303
P8
350
351
352
353
Description
Available for future use
Available for future use
Available for future use
Available for future use
4
54
104 154 204 254 304 354
Number of bytes sent by Client driver
5
55
105 155 205 255 305 355
6
7
9
56
57
58
106 156 206 256 306 356
107 157 207 257 307 357
108 158 208 257 307 357
8
10
11
59
60
61
109 159 210 260 310 360
110 160 210 260 310 360
111 161 211 261 311 361
Number of messages sent by Client
Number of response messages received by
Client
Available for future use
Most recent response error
Number of times Client receives an error
response
Error #1 Invalid Command
Error #2 No Display Table
12
13
14
15
16
17
18
19
20
21
22
23
24
62
63
64
65
66
67
68
69
70
71
72
73
74
112
113
114
115
116
117
118
119
120
121
122
123
124
Error #3 CCN Bus Communication Error
Error #4 Database Full
Error #5 DATAPORT Busy
Error #6 Device Not Configured
Error #7
Error #8
Error #9
Error #10
Error #11
Error #12
Error #13
Error #14
Some other error
25
75
125 175 225 275 325 375
Number of response bytes received by Client
26
76
126 176 226 276 326 376
Number of times Client has timeout out waiting
for (response)
27
77
127 177 227 277 327 377
Number of times Client prints a timeout SDO
message.
162
163
164
165
166
167
168
169
170
171
172
173
174
212
213
214
215
216
217
218
219
220
221
222
223
224
262
263
264
265
266
267
268
269
270
271
272
273
274
312
313
314
315
316
317
318
319
320
321
322
323
324
362
363
364
365
366
367
368
369
370
371
372
373
374
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com