FieldServer FS-8704-49 Appendix C. Troubleshooting Tips Appendix C.1. Bad Values

Models: FS-8704-49

1 48
Download 48 pages 32.01 Kb
Page 33
Image 33

FS-8700-49_Data_Aire_DAP

Page 33 of 48

Appendix C. Troubleshooting Tips

Appendix C.1. Bad Values

In the event that the driver cannot correctly decode the raw bytes it will generally write a value which indicates bad data. In most cases the indicating value is -1 or 65535 (depending on data type). When setting bits for status fields the driver will not write new data to the array if the incoming byte is invalid. Consult the error log for indication of this type of problem.

Example: Valid ASCII digits are 0...9, A...F. If a byte is being parsed and a hex digit is expected but not found then the driver considers this an error and writes the bad value indication OR produces an error message when the bad value indication cannot be used.

Appendix C.2. Dead Nodes

When a node is absent or dies, the driver may go idle and stop communicating with all other nodes. This problem is specific to the Data Aire devices.

Appendix C.3. Noise

A high percentage of responses on the secondary port are preceded with noise. The driver is generally able to filter this noise because legitimate characters in a response are limited to the ASCII character set and a few control characters. The driver does not filter noise in the middle of a message. Thus the message will fail (generally as a checksum failure) when there is noise in the middle of a message. This is normal for most drivers.

Appendix C.4. Ignored Messages

Ignored messages which are messages sent by a DAP/DART for which the driver cannot find an appropriate Map Descriptor are reported by the driver. This simply indicates that a message containing information that is not required is being discarded. The current version of the driver ignores a few messages relating to the status of the DART device. Later versions of the driver will be capable of storing these messages and the number of ignored messages will decrease.

Appendix C.5. Driver limitation

Unable to reset run times.

Appendix C.6. Baud Rate.

Rev 9.5 of the DAP firmware changed the baud rate from 2400 to 9600. All units must have the same baud rate on the network. The customer should check the firmware version of each unit and record these in a table. FieldServer recommends that all units have the same version due to the fact that instability between different versions has been experienced.

Appendix C.7. Wiring.

This must be completed exactly as specified by Data Aire. Variations in the wiring invariably causes problems. The wit=ring/installation guide is available from Data Aire.

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 33
Image 33
FieldServer FS-8704-49 Appendix C. Troubleshooting Tips Appendix C.1. Bad Values, Appendix C.2. Dead Nodes