FieldServer FS-8700-80 - Manual (Page 33)

McQuay Micro Tech Open Protocol Driver Manual Page 33 of 43
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 Action
McQuay:#15 Err. MapDesc=%s. Field Name/Address
Required.
Neither a field name nor an address was specified. The
driver does not know what location to read. Specify a
field name from Appendix C.3.5
McQuay:#16 Err. MapDesc=%s. No Node.
Each Map Descriptor must be connected to a node. This is
done by specifying a node name. 5
McQuay:#17 Err. MapDesc=%s. Md too short.
The offset added to the length of the Map Descriptor
extends beyond the Data Array. Increase the Data Array
length. 5
McQuay:#18 Err. MapDesc=%s. Cannot write
'Everything'.
When using ‘everything’ as a field name the Map
Descriptor function must be Rdbc or Rdb as this is a read
only function.5
McQuay:#19 do diagnostic 3
Call FieldServer Technical Support. A developer
diagnostic has been called and should not have been.
McQuay:#20 do diagnostic 1
McQuay:#21 do diagnostic 2
McQuay:#22 Err. Illegal Node_ID [%d] - Set to 1
Check configuration file, a Node_ID is out of range. 6
McQuay:#25 Err. Max Len=1 when Bytes_Per_Field >
1. MD=%s. The length parameter must be set to 1 when a Map
Descriptor has the Bytes_Per_Field parameter specified5
McQuay:#26 Err. Max Bytes_Per_Field=4. MD=%s.
Legal values for the Bytes_Per_Field parameter are whole
numbers in the range 1 to 4 inclusive. 5
McQuay:#27* Err. Response=NAK. Read Manual.
Maybe password or Node_ID
This message is printed if a NAK response is received in
the first few polls to a node. The driver guesses that the
reason is that the Node_ID/route or password has been
incorrectly specified in the configuration file. Verify these
settings. The message is printed once and suppressed for
subsequent occurrences. Refer to Appendix B.2
McQuay:#28* Err. Device responded with a NAK.
The message is printed and then suppressed for
subsequent occurrences, but the NAK stat is incremented
for each occurrence. The driver is reporting that the
McQuay device responded with a NAK under different
circumstances from msg#27 which is printed if the NAK is
received during the first few polls. The message indicates
that the McQuay device could not respond. If the NAK's
are occasional, assume that noise has corrupted an
occasional message. If they occur frequently assume a
systematic or connection error. Refer to Appendix B.2.
McQuay : #29 FYI. Config requires non-critical
update. Route parameter is not used any more. In
driver version V1.05a and later either use
NODE_HI(0-F) and \NODE_LO(0-F) or NODE_ID(0-
255), use Node_Id(256) only if it is required that
connected Mcquay panel should respond regardless
of its own internal address
For Driver versions 1.05a and later, the route parmeter is
replaced by NODE_HI(0-F) and NODE_LO(0-F). NODE_ID
is still supported for backward compatibility with previous
driver versions. Use NodeID(0-255), use Node_Id(256)
only if it is required that connected Mcquay panel should
respond regardless of its own internal address
6
6 Correct the configuration by editing the CSV file and downloading it to the FieldServer, then reset the FieldServer for the changes to take
effect.