Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

interface device file seemingly not present following install

I installed an NI-488.2 PCI-GPIB on a Dell Precision 450 Workstation running Redhat Enterprise Linux 4.0WS.
The driver I used was Version 2.5 for Linux -- 32 Bit (ni488225L.iso).  The install seemingly ran with no errors. The GPIB Explorer shows an interface(GPIB0) of Type PCI-GPIB installed and the GPIB Troubleshooting Wizard shows the interface to be functioning properly.  I need to add this controller to the instrumentation being used by Agilent software ICCAP. When I had done this previously on Solaris I used the device file /dev/gpib0 to refer to the interface.  On this machine,  /dev/gpib0 does not exist and I have not been able to associate any of the files in /dev with the interface. Is there an NI tool I still need to run to create a device file for the interface? Do I have to make the device file myself?  major/minor numbers for the mknod command??? 
0 Kudos
Message 1 of 2
(2,899 Views)
Hi,

Unlike our Solaris driver, our current 488.2 driver for Linux does not support this method for device identification.  If it is essential to identify your device through this file, you may want to try using this open source GPIB driver package.  Please note that this driver/method is not tested or supported by National Instruments.  You will not be able to interface using LabVIEW or GPIB Explorer if you replace the NI 488.2 driver with the open source version.  However, if you are only going to be using the ICCAP software, this may be a method you would want to try.

Hope this helps!

Adam W
Applications Engineering
National Instruments

0 Kudos
Message 2 of 2
(2,886 Views)