Appendix


Appendix 1  Troubleshooting the RS-232C Faults

Check the items in the following table in the event of operating 
problems with the RS-232C interface.


Symptom

 (1)The RS-232C does not operate at all.
      -1.Is the cable properly connected?
       >> Refer to the instruction manual.
                (Chapter13, 13.1 Connecting the RS-232C Cable)
      -2.Is the unit correctly set?
           >> Refer to the instruction manual.
                (Chapter13, 13.2 Setting the RS-232C Interface)
      -3.Are all the devices that are connected powered on?

 (2)An attempt to read data using the CALL RECEIVE statement causes
    the RS-232C bus to hang.
      -1.Each and every CALL RECEIVE statement must be 
         preceded by a query.
      -2.Is the query transmitted incorrect?

 (3)Although a command was transmitted,the unit did not operate.
      -1.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." 

 (4)Even though a number of queries were sent, only one response
    was received.
      -1.Has an error occurred?
      -2.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.

 (5)An overrun error or a framing error occurs.
      -1.Is the transfer rate too high?
           >> Reduce the transfer rate.