GPIB Warning - Unable to Read All Data
These remedies apply to the case when you receive some data and you get this warning message:
'gpib' unable to read all requested data
ASCII Data
When using the GPIB interface for:
Reading ASCII (text) data using the
fscanf
,fgets
, orfgetl
functions
these are possible causes and remedies:
Cause | Solution |
---|---|
TheEOIMode property is not set correctly. |
Verify that theEOIMode property is set to the value required by your device. You can set it toon oroff , andon is the default. For more information about setting the property, seeWrite and Read GPIB Data. |
TheEOIMode property is set tooff , but theEOSMode andEOSCharCode properties might not be configured to the same setting as the instrument. |
Verify that theEOSMode andEOSCharCode properties are configured to the same settings as your device. For more information about setting the properties, seeEOSMode andEOSCharCode . |
Communication with the device was interrupted. | Check your device connection. For more information about troubleshooting configuration and connection, seeTroubleshooting GPIB Interface. |
Binary Data
When using the GPIB interface for:
Reading binary data using the
fread
function
these are possible causes and remedies:
Cause | Solution |
---|---|
Device did not send all the requested data. | Check your device connection. For more information about troubleshooting configuration and connection, seeTroubleshooting GPIB Interface. |
There was a data format mismatch. | 验证设备的数据格式匹配specified read format. Data format is set using thePrecision property. For more information about supported precisions, seefread . |
The number of values to read was not specified and was set to theInputBufferSize by default. |
Set the number of values to read using thesize argument on thefread function, or change theInputBufferSize property. For more information about setting the property, seeInputBufferSize . For information about setting number of values to read, seefread . |
Binblock Data
When using the GPIB interface for:
Reading binblock (binary-block) data using the
binblockread
function
these are possible causes and remedies:
Cause | Solution |
---|---|
The timeout value might be too short for the amount of data being read. | Increase theTimeout property value. For more information about setting the property, seeTimeout . |
Communication with the device was interrupted. | Check your device connection. For more information about troubleshooting configuration and connection, seeTroubleshooting GPIB Interface. |
More Troubleshooting Help
For more information about troubleshooting the GPIB interface, including supported platforms, adaptor requirements, configuration and connection, and other troubleshooting tips, seeTroubleshooting GPIB Interface.