Menu
▾
▴
[Linux-gpib-general] Fwd: Looking for sample steps to install GPIB drivers on kernel 2.6.24 through 2.6.33
|
From: Jon P. <jjp...@uc...> - 2010-12-09 18:51:08
|
---------- Forwarded message ---------- From: Jon Pimentel <jjp...@uc...> Date: Thu, Dec 9, 2010 at 10:19 AM Subject: Re: [Linux-gpib-general] Looking for sample steps to install GPIB drivers on kernel 2.6.24 through 2.6.33 To: Asher <as...@gm...> Hey Asher, I don't have time go through your exact situation with not being able to get your board to work, but I have had similar problems in the past and spent weeks trying to fix the problem. I still have my notes that I have copied below, I hope this helps: note: on ubuntu the directory I think is different for /dev/bus/usb, so you might have to do a search on the internet *Device * (any device) not found on GPIB network **Steps to get gpib network working on laptop *** 1. Plug in the gpib USB cable *** 2. type "lsusb" and write down the Bus number (e.g 004) and Device number (e.g 003) *** 3. cd into the gpib_firmware-2005-09-06 directory *** 4. cd into the agilent_82357a directory *** 5. type sudo fxload -D /dev/bus/usb/004/003 -I 82357a_fw.hex *** and press enter *** 6. If that doesn't work, replace 004 with the Bus number and 003 with the device number and run sudo fxload -D /dev/bus/usb/004/003 -I 82357a_fw.hex ***again *** 7. Type dmesg and press enter to confim that this output (or something similar) appears: ***[ 273.368173] Linux-GPIB 3.2.14 Driver ***[ 273.400811] agilent_82357a_gpib driver loadingprobe succeeded for path: usb-0000:00:04.0-4 ***[ 273.400885] usbcore: registered new interface driver agilent_82357a_gpib ***[ 273.400893] gpib: registered agilent_82357a interface ***[ 273.406932] gpib: (debug) request module returned 256 ***[ 273.407006] attached to bus interface 0, addr *** 8. You should be able to control the instruments now with your PERL scripts. However, if you cannot, type 'sudo ibtest'in *** 9. press d (for device) *** 10. type 0 and press enter *** 11. type w and press enter *** 12. type "output on" (without quotes) and press enter *** 13. now try controlling the instruments *** if you still get errors, try typing "output on" with different device addresses instead of 0. Or try this: *** 14. type b (for board) after typing sudo ibtest *** 15. enter "host" (without quotes) and press enter *** 16. press w *** 17. type "output on" (without quotes) and press enter *** 18. now try controlling the instruments *** 19. If that doesn't work, try reloading the driver using *** sudo fxload -t fx2 -D /dev/bus/usb/004/003 -I /usr/share/usb/agilent_82357a/measat_releaseX1.8.hex *** with 004 and 003 replaced with the bus and device number, respectively. Guide to install linux-gpib modules after updating/upgrading the linux kernel to the newest version: # Download the linux-gpib.tar.gz file (ex: linux-gpib-3.2.14.tar.gz) from http://sourceforge.net/projects/linux-gpib/files/ # Extract the files into a folder # cd into that folder and run the following commands: # sudo ./configure # sudo ./make # sudo ./make install # Now if you check /lib/modules/`uname -r`/ you should see a folder called 'gpib' and inside there should be agilent_82357a/ with the module inside # Now after running the fxload command, the driver should load automatically On Thu, Dec 9, 2010 at 10:13 AM, Asher <as...@gm...> wrote: > I'm also trying to set up the NI-GPIB-USB-HS on debian (ubuntu) and > installed the libgpib package via Synaptic. > /dev/gpib0 through /dev/gpib15 now exist. > However when I plug my device into the computer I can't seem to access it. > I tried running ibtest but I get the following error: > Do you wish to open a (d)evice or an interface (b)oard? > (you probably want to open a device): d > enter primary gpib address for device you wish to open [0-30]: 0 > trying to open pad = 0 on /dev/gpib0 ... > libgpib: ibBoardOpen failed to open device file /dev/gpib0 > libgpib: No such device or address > libgpib: error in is_cic()! > ibdev error > ibsta = 0x8000 < ERR > > iberr= 0 > EDVR 0: OS error > ibcnt = 9 > Aborted > here is my gpib.conf entry for my device: > interface { > minor = 0 > board_type = "ni_usb_b" > name = "GPIB-USB-HS" > pad = 3 > sad = 0 > eos = 0x0d > set-reos = yes > set-bin = no > set-xeos = no > set-eot = yes > master = no > } > I'm pretty new to this, so I could be missing something obvious. Any help > would be appreciated. If you need anymore info I can attempt to provide it. > Thanks, > Asher > >> >> Hi, >> >> Thomas Dorsey píše v Po 29. 11. 2010 v 12:33 -0700: >> >> > Hi, >> >> > >> >> > I am using Debian stable and possibly later kernels with RT-PREEMPT >> > patch. >> >> > I need to use the NI-USB-GPIB-HS now and hopefully transition to the >> >> > Agilent 5010A at a later date. >> >> > >> >> > 1) Has anyone ever verified if the GPIB drivers work with >> > NI-USB-GPIB_HS? >> >> there is some level of confusion. I believe I see it working with HSII, >> >> which does not need firmware upload: >> >> ID 3923:709b National Instruments Corp. >> >> > 2) Can you point me to any information with step by step installation >> >> > procedure. >> >> > a) The debian apt-get process fails to work correctly >> >> I have it running on Ubunut. Compiling from SVN works: >> >> svn co >> >> https://linux-gpib.svn.sourceforge.net/svnroot/linux-gpib/trunk/linux-gpib >> >> cd linux-gpib >> >> ./configure >> >> make >> >> su # or change to root >> >> make install >> >> > 3) I will eventually figure this out crawling through the code and >> > reading >> >> > Kernel manuals but until then I'm stuck using windows and ni bloat... >> >> Let me know if you found something interesting. It should work. For some >> >> example drivers for Keithley picoAmp and a lot of other GPIB >> >> instruments, feel free to check http://rts2.org >> >> Good luck. >> >> Petr > > ------------------------------------------------------------------------------ > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > |
