93
────────────────────────────────────────────────────
7.6 Notes on RS-232C Interface
────────────────────────────────────────────────────
Symptom Cause/Treatment
The RS-232C has stopped
working completely.
Are the cables properly connected?
Are all the devices powered on?
Has the communication condition been correctly set?
Transmission on the RS-232C
is not taking place properly.
Is the controller delimiter set correctly?
(Refer to Section 7.2.7, "Delimiters".)
When attempting to read data
using a BASIC INPUT
statement, the RS-232C bus
hangs.
Be sure to transmit one query before each INPUT
statement.
Have any of these transmitted queries resulted in as
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.
Using the
ERRor?
query, and check whether
transmission error occurred on the RS-232C.
The amount of data read in is
insufficient.
If the data includes one or more commas, then try using a
LINE INPUT statement.
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 *IDN? query been used?
The response message to a
query differs from the display
on the front panel of the 3560
Due to the response message being produced at the
instant that the 3193 receives the query, there is a
possibility that it may not agree with the display at the
instant that the controller reads it in.
.6 Notes on RS-232C Interface
To Next Page
Loading...
