9 errors – Fluke TRACKERTM 90100 User Manual

Page 56

Advertising
background image

Model 90100
Operators Manual


5-10

5.9 Errors

During program operations, errors may appear. The error messages are grouped into input errors, a
hardware error, and communication errors.

INPUT ERRORS

Input errors may appear while changing Item values. When these errors occur, press any key to clear the
error and enter a different value. After clearing the error, you may press Escape to end editing. The input
errors are:

• Value must be greater than zero
• Must specify at least one digit
• Value must be less than 999.99

HARDWARE ERROR

A hardware error occurs when the program cannot perform a required hardware operation. The only
hardware error is a printer error. If the Customization software cannot send information to the printer, the
following message appears.

Printer Error

Press any key to clear the error. Correct the problem causing the error (for example, out of paper or the
printer is not on-line), and try printing again.

COMMUNICATION ERRORS

These errors indicate that the communications between the computer and the instrument is faulty.
Generally, the icon in the upper right corner indicates the status of the RS-232 connection. The following
errors indicate problems during actual communication. Press any key to clear the error.

Dosimeter is not connected

If the RS-232 connection becomes severed during communication, this error appears. Re-connect the
line and try the download again.

Upload/Download mismatch

If the information received from the 35360A does not match that sent by the Customization software, this
error appears. Generally, the downloaded information was out of the boundary given for the specific Item.
The Customization software retains the ORIGINAL text or value.

Finally, the Customization software checks the RS-232 connection at the beginning of the program. If it
detects that no instrument is connected, the program ends and an error message occurs. Check the
cable for breaks and confirm that the connections are solid. The program defaults to COM1: for the
communications port. If that port is in use, specify COM2: by placing /2 on the command line:

custom /2

Also, make sure that the instrument has been on for at least five seconds.

Advertising