3. Supported Hardware

3.1. Supported Hardware Matrix

Table 2. Linux-GPIB Supported Hardware Matrix

makemodelkernel driver moduleboard_type (for /etc/gpib.conf)
Agilent (HP)82341Chp_82341.kohp_82341
Agilent (HP)82341Dhp_82341.kohp_82341
Agilent82350Bagilent_82350b.koagilent_82350b
Agilent82357Aagilent_82357a.koagilent_82357a
Capital Equipment CorporationPC-488pc2_gpib.kopcII
Capital Equipment CorporationPCI-488cec_gpib.kocec_pci
CONTECGP-IB(PC)pc2_gpib.kopcIIa
HamegHO80pc2_gpib.kopcII
HamegHO80-2ines_gpib.koines_isa
Hewlett PackardHP82335hp82335.kohp82335
Hewlett PackardHP27209hp82335.kohp82335
InesGPIB-HS-NTines_gpib.koines_isa
InesGPIB for Compact PCIines_gpib.koines_pci, ines_pci_unaccel
InesGPIB for PCIines_gpib.koines_pci, ines_pci_unaccel
InesGPIB for PCMCIAines_gpib.koines_pcmcia, ines_pcmcia_unaccel
InesGPIB PC/104ines_gpib.koines_isa
IotechGP488Bpc2_gpib.kopcIIa
KeithleyKPCI-488cec_gpib.kocec_pci
KeithleyMBC-488pc2_gpib.kopcII
Measurement Computing (Computer Boards)CPCI-GPIBcb7210.kocbi_pci, cbi_pci_accel
Measurement Computing (Computer Boards)ISA-GPIBcb7210.kocbi_isa, cbi_isa_accel
Measurement Computing (Computer Boards)ISA-GPIB/LCcb7210.kocbi_isa
Measurement Computing (Computer Boards)ISA-GPIB-PC2Apc2_gpib.kopcIIa (nec7210 chip), pcIIa_cb7210 (cb7210 chip)
Measurement Computing (Computer Boards)PCI-GPIB/1Mcb7210.kocbi_pci, cbi_pci_accel
Measurement Computing (Computer Boards)PCI-GPIB/300Kcb7210.kocbi_pci
Measurement Computing (Computer Boards)PCMCIA-GPIBcb7210.kocbi_pcmcia, cbi_pcmcia_accel
National InstrumentsAT-GPIB (with NAT4882 chip)tnt4882.koni_nat4882_isa, ni_nat4882_isa_accel
National InstrumentsAT-GPIB (with NEC7210 chip)tnt4882.koni_nec_isa, ni_nec_isa_accel
National InstrumentsAT-GPIB/TNTtnt4882.koni_isa, ni_isa_accel
National InstrumentsGPIB-USB-Bni_usb_gpib.koni_usb_b
National InstrumentsPCI-GPIBtnt4882.koni_pci
National InstrumentsPCI-GPIB+tnt4882.koni_pci
National InstrumentsPCM-GPIBtnt4882.koni_pci
National InstrumentsPXI-GPIBtnt4882.koni_pci
National InstrumentsPCIIpc2_gpib.kopcII
National InstrumentsPCIIapc2_gpib.kopcIIa
National InstrumentsPCII/IIapc2_gpib.kopcII or pcII_IIa (depending on board switch)
National InstrumentsPCMCIA-GPIBtnt4882.koni_pcmcia, ni_pcmcia_accel
QuancomPCIGPIB-1ines_gpib.koines_pci, ines_pci_unaccel

3.2. Board-Specific Notes

3.2.1. Agilent (HP) 82341

After power-up, the Agilent 82341 boards require a firmware upload before they can be used. This can be accomplished using the "--init-data" option of gpib_config. The firmware data can be found in the gpib_firmware tarball available from the Linux-GPIB home page. Note the C and D versions use different firmware data.

If you specify a non-zero base address in /etc/gpib.conf, the driver will assume you are trying to configure a 82341C. Otherwise, the driver will use the kernel's ISAPNP support to attempt to configure an 82341D.

The 82341 does not support detection of an end-of-string character in hardware, it only automatically detects the when the EOI line is asserted. Thus if you use the REOS flag for a read, the board's fifos will not be used for the transfer. This will greatly reduce the maximum transfer rate for your board (which may or may not be noticeable depending on the device you are talking to).

3.2.2. Agilent 82350B

The Agilent 82350B does not support detection of an end-of-string character in hardware, it only automatically detects the when the EOI line is asserted. Thus if you use the REOS flag for a read, the board's fifos will not be used for the transfer. This will greatly reduce the maximum transfer rate for your board (which may or may not be noticeable depending on the device you are talking to).

3.2.3. Agilent 82357A

The Agilent 82357A requires a firmware upload (before gpib_config is run) to become functional after being plugged in. The linux-gpib tarball contains hotplug scripts for automatically running the fxload program to upload the firmware (and to run gpib_config after the firmware is uploaded). However, the actual firmware data itself must be obtained seperately, as part of the gpib_firmware tarball available from the Linux-GPIB home page.

The 82357A has a few limitations due to its firmware code:

  • It cannot be run as a device, it must be the system controller.

  • It cannot be assigned a secondary address.

  • It cannot do 7 bit compares when looking for an end-of-string character (it always compares all 8 bits).

3.2.4. National Instruments GPIB-USB-B

The USB-B requires a firmware upload (before gpib_config is run) to become functional after being plugged in. The linux-gpib tarball contains hotplug scripts for automatically running the fxload program to upload the firmware (and to run gpib_config after the firmware is uploaded). However, the actual firmware data itself must be obtained seperately, as part of the gpib_firmware tarball available from the Linux-GPIB home page.