Documentation

This is machine translation

Translated by Microsoft
Mouse over text to see original. Click the button below to return to the English verison of the page.

GPIB Driver Limitations by Vendor

ICS Electronics

The ICS Electronics™ GPIB adaptor does not support asynchronous read and write operations, and therefore, ICS GPIB objects do not support the following toolbox functions and properties:

  • readasync

  • async flag for the fprintf and fwrite

  • BytesAvailableFcn

  • OutputEmptyFcn

Keysight (formerly Agilent Technologies)

The Keysight™ GPIB driver has these limitations:

  • Asynchronous read and write operations are not supported. Therefore, Keysight GPIB objects do not support the following toolbox functionality:

    • The readasync function

    • The async flag for the fprintf and fwrite functions

    • BytesAvailableFcn and OutputEmptyFcn properties

  • The End Or Identify (EOI) line is not asserted when the End-Of-String (EOS) character is written to the hardware. Therefore, when the EOSMode property is configured to write and the EOIMode property is configured to on, the EOI line is not asserted when the EOSCharCode property value is written to the hardware.

  • All eight bits are used for the EOS comparison. Therefore, the only value supported by the CompareBits property is 8.

  • A board index value of 0 is not supported.

  • An error is not reported for an invalid primary address. Instead, the read and write operations will time out.

Measurement Computing Corporation (MCC)

The Measurement Computing™ Corporation GPIB driver does not support asynchronous notification for the completion of read and write operations. Therefore, Measurement Computing Corporation GPIB objects do not support the following toolbox functionality:

  • The readasync function

  • The async flag for the fprintf and fwrite functions

  • The BytesAvailableFcn and OutputEmptyFcn properties

Was this topic helpful?