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 # DESCRIPTION
FS-8917-02 RJ45 to DB9F connector adapter
FS-8917-17 RJ45 to DB25M connection adapter
SPA59132 RS-485 connection adapter
FS-8700-86 Driver Manual.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
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
4. 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 Function Legal Values
Data_Array_Name Provide name for Data Array Up to 15 alphanumeric characters
Specify which port the device is connected to the
FieldServer
Baud* Specify baud rate.
Parity* Specify parity
Data_Bits*
Stop_Bits*
Protocol
Specify data bits
Specify stop bits.
Specify protocol used CarrierDP
Handshaking* Specify hardware handshaking
Poll _Delay*
Time between internal polls
Specifies the max amount of time the driver must
wait for a complete response.
Timeout2
If the Data Port table is long then increase the
timeout above the default until timeout errors
disappear.
Application
Refer to notes in Appendix B.3 Print_storage_locations
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)
Start_Method*
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)
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
Data_Array_Location Starting location in Data Array
Function Function of Client Map Descriptor Rdbc, Wrbc, Wrbx
Name of Data Array where data is
to be stored in the FieldServer
One of the Data Array names from
“Data Array” section above
0 to maximum specified in “Data
Array” section above
4.4.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
One of the node names
Node_Name Name of Node to fetch data from
Data_Type
Length
Address This commonly used parameter is not required for this driver.
Store_As*
DA_Byte_Name*
DA_Float_Name*
This commonly used parameter is not
required for this driver.
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.3.
Use the ASCII or AsciiLog format when
you are discovering the variables
contained in a table by reading a table.
Refer to Appendix A for more information.
If defined, the driver stores the ‘field status’
value in this array.
If defined, the driver stores the ‘field units’
value in this array.
specified in “Client Node
Descriptor” above
1 – 1000
ASCII, AsciiLog, Values
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.
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled >0.1s
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
table elements whose values have been successfully stored at offset zero.
value were stored.
FS-8700-86 Carrier DataPort Page 10 of 32
5. 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.4.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
Data_Array_Location Starting location in Data Array
Function Function of Client Map Descriptor passive
Name of Data Array where data is
to be stored in the FieldServer
One of the Data Array names from
“Data Array” section above
0 to maximum specified in “Data
Array” section above
5.4.2. Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
One of the Node Names
Node_Name Name of Node to fetch data from
Length of Map Descriptor. When reading a
Length6
Table_Name*
Field_Name This is the field variable pneumonic.
Field_Description Returned when a Client does a read.
Field_Units
Field Status*
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.
E.g. ‘TZCONF TZONE1’
Returned when a Client does a read. If units
have no meaning for the variable set to zero.
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.
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.
An Ascii string which
may not
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.
6
Additional information on the length parameter is provided in Appendix A.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
If this parameter is defined then its value must be
DA_Byte_Name*
On_String
Off_String
Length
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.
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
5.4.3. 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
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 Value Engineering Units Value Engineering Units
000 no units 051 feet per minute 260 Pascal
001 degrees F 052
002 degrees F 053
003 percent 054 tons 264 delta degrees C
004 inches of water 055 tons per hour 267 degrees C
005 milliamps 056 revolutions per minute 270 Pascal
006 delta degrees F 057 percent open 272 delta degrees C
007 degrees F 058 hours 273 degrees C
008 delta degrees F 059 gallons 274 delta degrees C
010 Volts 064 on/off input 276 kiloPascals
011 degrees F 065 off/on input 288 liters per minute
013 percent 066 input pulses on 289 liter per hour
014 inches of water 067 input pulses off 290 cubic meters per minute
015 milliamps 068 seconds 291 cubic meters per hour
016 delta degrees F 069 normal/alarm 292 kiloPascals
017 degrees F 070 Hz 293 kilograms per hour
018 delta degrees F 080 minutes 295 kilowatt hours
020 pounds per square inch 081 hours 296 kilowatts
032 gallons per minute 082 revolutions per minute 297 millimeters of water
033 gallons per hour 124 clock 298 millimeters of mercury
034
035
minute
hour
126 ASCII 299 kilowatt hours
128 no units 300 kilowatts
per minute
per hour
262 delta degrees C
263 degrees C
036
037 pounds per hour 137 pounds per square inch 302 percent relative humidity
038
039 BTUs per hour 144 kilowatts 304 volts
040 thousands of BTUs 145 kilowatt hours/pulse 305 cubic meters per minute
041 inches of water 146 pulses 306 cubic meters per hour
042 inches of mercury 192 on/off output 307 meters per second
043 kilowatt hours 193 off/on output 310 tons
044 kilowatts 194 pulsed on output 311 tons per hour
045 degrees F 195 pulsed off output 312 revolutions per hour
046 percent relative humidity 208 steps 313 percent open
047 amps 254 ASCII 314 hours
048 volts 256 no units 315 liters
049 cubic feet per minute 257 degrees C
050 cubic feet per hour 258 degrees C
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Conditions
No Force 0
Fire 16
Safety 32
Service Tool 48
Supervisor 64
Monitor 80
Minimum-off 96
Control 112
BEST 128
Temp Override 144
Loadshed 160
113
129
145
161
114
130
146
162
115
131
147
163
100
116
132
148
164
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 forced by fire alarm equipment
Safety forced by internal safety override
Service Tool forced by CCN Service Tool
Supervisor forced by local Building Supervisor
Monitor forced by remote Building Supervisor
Minimum-off forced by minimum off time requirement
Control forced by System Software Option
BEST forced by BEST program
Temp Override forced by temperature override
Loadshed forced by Loadshed System Software Option
Appendix A.2. 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
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
FS-8700-86 Carrier DataPort Page 19 of 32
Appendix A.3. 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 Value State Word Value State Word Value
CLEAN 1 ABNORMAL 1 OPEN 1
DIRTY 0 NORMAL 0 CLOSE 0
HEAT 1 LOCAL 0 CLOSED 0
COOL 0 REMOTE 1 ALARM 1
ON 1 LOCAL R 0
OFF 0 RUNNING 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.).
The driver recognizes discrete state words by checking the 1st 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
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.
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.
State Words
The name will be
stripped of all
spaces between the
last character and
the comma.
Normally the values
will be 1/0 for the
on/off states but the
driver does not
restrict the value.
Protocol must
be defined on
every line.
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
time value by checking the 3rd character for a colon and checking that the 1st 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
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
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
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
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
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 Explanation
The length of the Map Descriptor used to expose driver statistics is too
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>
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
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.
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
Array Offset is based on Port Number
P1 P2 P3 P4 P5 P6 P7 P8 Description
0 50 100 150 200 250 300 350 Available for future use
1 51 101 151 201 251 301 351 Available for future use
2 52 102 152 202 252 302 352 Available for future use
3 53 103 153 203 253 303 353 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 Number of messages sent by Client
6 56 106 156 206 256 306 356
7 57 107 157 207 257 307 357 Available for future use
9 58 108 158 208 257 307 357 Most recent response error