## Troubleshooting Data Acquisition

If a problem occurs with data acquisition, check the following items.

The causes and measures for items without a mark are common to RS-232C, GP-IB, USB, and LAN.

### Communication cannot be performed properly.

- Are the RS-232C settings (baud rate, data length, parity, and stop bit) of the IM3590 and computer the same? [RS-232C]
- Set the message terminator (delimiter) of the controller properly.
- See "Message Terminator"

### The keys do not work after communication.

- Press the LOCAL key on the panel of the instrument to cancel the remote state.
- Is the LLO (local lock out) command being sent? [GP-IB]
- Send the GTL command to switch to the local state.

### A command was sent but the operation is not performed.

- Use *ESR? to view the contents of the standard event status register and check what the error is.

### Several queries were sent, but only one response was returned.

- Did an error occur?
- Perform one read for each query sent. If you want to read the data in one go, use a message separator and include everything on one line.

### The response message of the query differs from the indication on the panel.

- The response message is created at the point in time when the instrument received the query, so it may not match the indication for the point in time when the data was read by the controller.

### Sending the *TRG command results in a beep sound.

- Is the trigger set to the internal trigger?
- The *TRG command is only valid for the external trigger setting. An execution error occurs with the internal trigger setting.