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, or fgetl functions
these are possible causes and remedies:
| Cause | Solution |
|---|---|
The EOIMode property is not set correctly. | Verify that the EOIMode property is set to the
value required by your device. You can set it to on
or off, and on is the default. For
more information about setting the property, see Writing and Reading Data . |
The EOIMode property is set to
off, but the EOSMode and
EOSCharCode properties might not be configured to
the same setting as the instrument. | Verify that the EOSMode and
EOSCharCode properties are configured to the same
settings as your device. For more information about setting the
properties, see EOSMode and
EOSCharCode. |
| Communication with the device was interrupted. | Check your device connection. For more information about troubleshooting configuration and connection, see Troubleshooting 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, see Troubleshooting GPIB Interface. |
| There was a data format mismatch. | Verify that the device data format matches the specified read format.
Data format is set using the Precision property. For
more information about supported precisions, see fread. |
The number of values to read was not specified and was set to the
InputBufferSize by default. | Set the number of values to read using the size
argument on the fread function, or change the
InputBufferSize property. For more information
about setting the property, see InputBufferSize. For
information about setting number of values to read, see fread. |
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 the Timeout property value. For more
information about setting the property, see Timeout. |
| Communication with the device was interrupted. | Check your device connection. For more information about troubleshooting configuration and connection, see Troubleshooting 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, see Troubleshooting GPIB Interface.