Specifications

Chapter 3 73

Troubleshooting

Frequently Encountered Diagnostic Messages

Warning/Error Messages

Error messages that appear on the second line of the Test Set’s display

frequently occur while any of the SERVICE4 program diagnostic tests

are running. The most complete and general list of error messages is in

the “Error Messages” chapter of the Test Set’s Reference Guide. (Some

messages relating specifically to troubleshooting can be found in

Appendix A , “Error Messages,” on page 321.) Some of the messages you

can expect to occur while running the SERVICE4 program diagnostic

tests are as follows:

• Direct latch write occurred. Cycle power when done

servicing. The SERVICE4 program commonly generates this

message. This message appears the first time the diagnostic

program directly addresses a latch. The message should be ignored

and cleared when you make a normal (not a diagnostic)

measurement with the Test Set. To clear this message the Test Set

should be turned off and back on again.

• Change Ref Level, Input Port or Attenuator (if using

“Hold”). This message, and similar messages, can be generally

ignored.

• Printer does not respond. This usually indicates that one or

more settings on the TESTS (Printer Setup) screen are set

incorrectly for your printer. Also, check that the printer’s power is on

and that it is correctly cabled. For GPIB printers make sure the

printer is correctly addressed. If a serial printer is used, you may

have to change the serial communication settings on the I/O

CONFIGURE screen (press

Shift then Inst Config to get to this

screen). The message times out after a few seconds, and the output

destination is changed to CRT by the program.

• ERROR 173 IN XXXX Active/system controller req’d (where

”XXXX” represents a line number). Indicates that the Test Set’s

internal IBASIC computer must be set as a system controller for

some reason. This usually indicates that the Printer Port field of

the TESTS (Printer Setup) screen was set to HP-IB but the Mode field

on the I/O CONFIGURE screen is set to Talk&Lstn instead of

Control. Change the mode setting to Control and run the

diagnostic again.