2 Troubleshooting Guidelines
Troubleshooting Overview
A suggested troubleshooting flowchart for the 82350, installed instruments, and the Agilent IO Libraries Suite follows. We suggest that you start at Step 1 and then go to Step 2 and then to Step 3, as required.
1 82350 Hardware Checks
Typical Causes
Bad GPIB cables/connections or power not ON for PC or instruments.
2 82350 Software Checks |
|
|
| 3 IO Libraries Checks |
|
|
| ||
| ||||
|
|
|
|
|
|
|
|
|
|
Typical Causes |
| Typical Causes |
| ||
GPIB card drivers not installed |
| Agilent IO Libraries Suite not |
| ||
or GPIB card not properly |
| installed or improper IO |
| ||
configured. |
| Libraries Suite configuration |
|
Check Cables/
Connections/Power
Check Device Manager
Other Hardware Checks
After Doing These Checks:
-If the cause is not identified, see GPIB Software Checks
-If the cause is identified as an 82350 hardware problem, contact Agilent to return the 82350.
Check for GPIB
Driver Files
Disable Connection Expert
Check BIOS/Interrupts
Settings
Set 82350 Read/Write
Performance Mode
After Doing These Checks:
-If the cause is not identified, see Agilent IO Libraries Checks
-If the cause is identified, but the problem cannot be fixed, contact Agilent for support.
Check IO Libraries Suite
Installation
Check IO Control
Operation
Install Libraries (if GPIB
Already Installed)
After Doing These Checks:
-If the cause is not identified or the problem cannot be fixed, contact Agilent for support.
Figure 2-1 Troubleshooting overview
34 | 82350B Installation and Configuration Guide |
