SECTION 9
DIAGNOSTICS
113
9
USER DIAGNOSTICS (cont’d)
PROBLEM
KEYS do not respond at all.
PROBABLE CAUSE
–
Keyboard is locked
SUGGESTED CURE:
Press
fn
and
EDIT
keys to unlock keyboard. Refer to section
4.6.3.10
PROBLEM
UPC does not respond to the GPIB
PROBABLE CAUSE
–
GPIB device address incorrect or not unique
SUGGESTED CURE:
Verify that the device address selected within the GPIB
controller software matches the GPIB device address within
the UPC. There may only be a single device at each GPIB
address. Refer to section 4.6.3.3 (UPC STATUS display) to
verify or set the GPIB device address within the UPC.
You may also use the UPC STATUS display to verify receipt
of an INTERFACE CLEAR (IFC) by the UPC from a GPIB
controller. Refer to section 4.6.3.3 (UPC STATUS display)
for usage of the IFC field.
The "LAST DATA BYTE" field indicates the data byte
received by the UPC from the GPIB when the UPC was
addressed as a listener. Normally if a properly terminated
command string was received by the UPC, the LAST DATA
BYTE received should be 0Ah (a Line Feed). The Line Feed
character or END signal (EOI) is the proper end of string
<eos> terminator. Refer to section 4.6.3.3 (UPC STATUS
display) for usage of the LAST DATA BYTE field.
Characters sent one at a time to the UPC via the GPIB when
the UPC is addressed to listen will be displayed in the LAST
DATA BYTE field.
Summary of Contents for UPC-1
Page 2: ......
Page 12: ...SECTION 1 GENERAL viii THIS PAGE INTENTIONALLY BLANK ...
Page 17: ...SECTION 1 GENERAL 5 PACIFIC Figure 1 3a SCU UPC 3 Figure 1 3b UPC 3 Figure 1 3c UPC 1 ...
Page 43: ...SECTION 4 OPERATION 31 PA CIFIC FIGURE 4 1 POWER SOURCE FRONT PANEL ...
Page 74: ...SECTION 4 OPERATION 62 90 0 100 0 85 95 100 90 FIGURE 4 6 2 1 EDITED WAVEFORM ...
Page 134: ...NOTES 122 NOTES ...