Check the items in the following table in the event of operating problems with the RS-232C interface.
Symptom | Likely causes and remedies |
The RS-232C does not operate at all. | Is the cable properly connected? Refer to the instruction manual. "Chapter13, 13.1 Connecting the RS-232C Cable" |
Is the unit correctly set? Refer to the instruction manual. "Chapter13, 13.2 Setting the RS-232C Interface" | |
Are all the devices that are connected powered on? | |
An attempt to read data using the CALL RECEIVE statement causes the RS-232C bus to hang. | Each and every CALL RECEIVE statement must be preceded by a query. |
Is the query transmitted incorrect? | |
Although a command was transmitted, the unit did not operate. | Use the "*ESR?" query to check the standard event status register for anomalies. See CHAPTER 1 , "1.2 The Status Byte and the Event Registers." |
Even though a number of queries were sent, only one response was received. | Has an error occurred? |
The response should be read immediately after each query. To read several responses in one operation, the corresponding queries must be combined into a single line using the message separator. | |
An overrun error or a framing error occurs. | Is the transfer rate too high? Reduce the transfer rate. |