From: dave p. <dpe...@gm...> - 2022-08-01 19:19:33
|
Hi Jakub, One way to check is to look at: the output of the syslog lines with "gpib" in them and the output of "lsusb -d 3923:", with the adapter plugged in. cheers, -dave On Mon, 1 Aug 2022 at 15:02, Ladman Jakub <la...@vo...> wrote: > Hello > I am new to this maling-list and with only limited experience with GPIB > in general. > I have NI GPIB-USB-HS hardware, which I want to use with linux-gpib. > I have tried several versions of the linux-gpib (both kernel and user > part) including 4.3.4 and 4.3.5. with my computer with kernel: > > $ uname -r > > 5.15.0-43-generic (ubuntu 22.04) > Also my friends computer with kernel 3.16.0-4 (some old debian) and > linux-gpib-3.2.21, which he is using regularly with another piece of > GPIB-USB-HS interface. > The behavior was the same, with the exception that the error messages > were slightly different. > The kernel module ni_gpib_b.ko is successfuly loaded, the rights are > set, user is in the gpib group, the /dev/gpib0 is created among others. > > findlisteners lists my two devices (HP 3478A multimeter and AMREL > PPS-1002 power supply) at pads 22 and 12. > When trying to communicate with the devices from ibtest, ibterm or from > python script I've got something similar to this: > > ibterm>MODEL? > ibterm error: Unable to write to device at pad 12 > > or > :m > gpib status is: > ibsta = 0x8100 < ERR CMPL > > iberr= 0 > EDVR 0: OS error > > ibcnt = 5 > But everytime I tried this, the controlled devices were signalizing > "RMT" "TALK" or so on (from top of my head, because I am at different > place now) > > I was convinced, that the hardware is half dead until I checked it from > windows with NI software. > > I have installed whole bundle of software and then opened NI MAX. > > From there i was completely able to scan and detect the devices and to > communicate with those in the first place without any configuration. > > I have also tried the NI software for linux with ni488k.ko kernel > module (among others; instaled from official .deb package), but then > the kernel module seems to completely ignore the hardware device. The > userspace applications don't see any gpib interfaces. > > I dont know whether my device is a fake one or not, I bought it with > huge discount from china, but everyting seems legit. > > The packaging was nice and clean, there was safety sticker on the bubble > bag inside the box. > > The case is made of quality plastics, the color is as usual, the sticker > on it is looking ok, the CD-ROM or DVD-ROM included is looking good, the > booklet is good. There is "Made in Hungary" noted on everything which is > also legit because they have manufacturing plant in Hungary. > > Both the windows software from the 2016 CD/DVD and the lastest form > ni.com is functioning perfectly. > > Only the linux versions, both opensource and the ni provided are non > functional. > > Is there a posibility to check the firmware version and compare it to a > known to work interface piece? > > Any other tip? > > Thank you very much > Jakub Ladman > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > |