192
────────────────────────────────────────────────────
8.9 Notes on Interface
────────────────────────────────────────────────────
8.9.1 GP-IB Troubleshooting
Symptom Cause/Treatment
The GP-IB has stopped working
completely.
Are the cables properly connected?
Is the device address for the 3332 set correctly?
Does some other device have the same device address?
Are all the devices powered on?
After transmission on the GP-IB
bus, the keys on the 3332 freeze
up and have no effect.
Press the LOCAL key on the front panel of the 3332 to
release the remote state.
Has a LLO (Local Lock-Out) command been transmitted?
Transmit a GTL command to put the 3332 into the local
state.
When attempting to read data
using a HP-Basic ENTER
statement, the GP-IB bus hangs.
Be sure to transmit one query before each Basic ENTER
statement.
Have any of these transmitted queries resulted in an error?
Although a command has been
transmitted, nothing has
happened.
Using the "
*
ESR?" query, inspect the standard event status
register, and check what type of error has occurred.
Sending several queries, produces
only one response.
Has an error occurred?
Send the queries one at a time, and read the responses
individually.
When you want to read them in all at once, try doing so by
putting them all on one line separated by the message
separator character.
Have you used the "
*
IDN?" query?
Sometimes service requests are
not generated.
Have the service request enable register and the various
event status enable registers been correctly set?
Clear all the event registers at the end of SRQ processing
subroutines by using the "
*
CLS" command. If an event bit
is not cleared, no service request will be generated for that
event.
If service requests may be generated by performing
sampling processing twice or more successively, make sure
that the SRQ processing subroutine can be completed within
200 ms.
8.9 Notes on Interface
If the GP-IB appears to be malfunctioning, refer to the information below
before calling for servicing.
To Next Page
Loading...
