FieldServer Carrier DataPort FS-8700-86 - Manual (Page 28)

FS-8700-86 Carrier DataPort Page 28 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: [email protected]
Error Message Explanation
CarrierDP:13 FYI.
Diagnostic send error #1
response.
CarrierDP:14
FYI.
Diagnostic cancelled slave
response
These messages are for FieldServer engineers. If any either is ever
printed in the error log please call FieldServer support and report the
message.
CarrDP:#15 Err. Field Units
required. MapDesc=<%s>
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
CarrDP:#16 FYI. Use
DA_Byte_Name for server
status values. MD=<%s>
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
CarrDP:#17 FYI. Use
DA_Byte_Name for 'status'
value storage. MD=<%s>
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
CarrDP:#18 FYI. Use
DA_Float_Name for 'units'
value storage. MD=<%s>
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
CarrDP:#19 Err.
'Table_Name' has no
meaning. MapDesc=<%s>
CarrDP:#20 Err.
'Field_Name' has no
meaning. MapDesc=<%s>
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 Err.
'Field_Name' required.
MapDesc=<%s>
CarrDP:#23
Err.
'Field_Desc' required.
MapDesc=<%s>
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.
*
CarrDP:#24 Err. MD=<%s>
discrete state word not
recognized.
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.
*
CarrDP:#25 Err. This driver 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.