A:
A send/receive function timeout error occurs if the other device does not respond to send/receive for a certain period of time.
A GPIB error occurs if the GPIB cable is not connected or if the other device is not switched on,
At least the GPIB cable is connected and the other device is switched on.
In general, the following factors can cause a timeout error.
1) [Master/Slave] The GPIB device address setting is different.
The GPIB device address is set by each device, but the GPIB device address specified in the send/receive function is different.
Check the GPIB device address.
2) [Master/Slave] The delimiter code setting is different.
The delimiter code is set by each device, but the delimiter code setting on the board is different from this.
Try changing the delimiter in the send/receive Diagnosis program.
3) [Master] The command to the device is different.
This is a case where the commands to be communicated are different.
If the transmission succeeds but the reception fails, this is highly likely to be the case.
The commands to the device differ for each device, so please refer to the manual for each device.
( Many devices seem to prepare data by applying a trigger (GET command), so it is recommended to execute the trigger in Diagnosis program and then try reception.)
4)[Slave] Communication timing is not correct.
The slave can send and receive after the master designates the talker and the listener.
In order to match the communication timing with the master, it is recommended to check the talker and the listener designation from the master before sending and receiving.
Please refer Practical sample item on [Tutorial]-[Communication in Slave Mode (Non-controller)]-[Data Transmitting/Receiving] topic.
5)[Master] Not leveraging SRQ.
If you attempt to send or receive data from the master while the slave is measuring, the slave may not respond correctly.
In general, the slave devices have a function that executes SRQ on the master when a time-consuming process is completed.
Therefore, we recommend that the master wait for SRQ before sending or receiving data.
For information about whether the slave device has the SRQ function and the communication sequence, refer to the instruction manual of your device.
6)[Master] The slave device communication processing is slow.
Depending on the slave device, communication processing may not be able to keep up.
This may be resolved by adding a weight between GPIB commands and transmitted/received data.
The amount of weight required depends on the device, so try starting with a longer weight.
For details, refer to the "Wait time between GPIB commands and data" item in [Tutorial]-[ Property Settings] topic.
The default timeout time setting is 10 seconds.
The timeout time setting can be changed using the GpibSetTimeOut() function, so changing this is one countermeasure.
The setting range is the specified value (0 to FFFFFFFFFFH) x 1 [msec] (0 msec to 4294967295 msec).
However, if 0 is specified, no timer check is performed. In other words, no timeout occurs.
Processing may not be completed depending on the communication status with the remote device.