linux-gpib-general — linux-gpib package mailing list

Re: [Linux-gpib-general] PCMCIA GPIB help with linux-gpib-4.3.0

[dave p. <dpe...@gm...>]

Hi Mitchell,
The kernel module for ni_pcmcia and ni_pcmcia_accel is the tnt4882.ko
module which seems to exist from your dmesg.
We forgot to put a GPIB_CONFIG_PCMCIA config option into the Makefile when
autoconf was dropped for the kernel modules build.
Please edit the "all" target in the top level Makefile in the
linux-gpib-kernel-4.3.0 directory to look like so:
all:
    -$(MAKE) -C $(LINUX_SRCDIR) V=$(VERBOSE) modules \
        M="$(GPIB_SRCDIR)/drivers/gpib" \
        GPIB_TOP_DIR=$(GPIB_SRCDIR) \
        CONFIG_GPIB_ISA="$(ENABLE_ISA)" \
        HAVE_DEV_OF_NODE=$(HAVE_DEV_OF_NODE) \
        GPIB_CONFIG_KERNEL_DEBUG=$(GPIB_DEBUG) \
        GPIB_CONFIG_PCMCIA=1

Rebuild and install the kernel modules with the above modification and
reboot to test.
BTW: The gpib_config command should be: gpib_config --minor 0.
Cheers,
-Dave

On Tue, 7 Apr 2020 at 02:02, Mitchell Clement <mo....@gm...> wrote:

> Hi, I'm new to the Linux-GPIB community and am hoping to get some guidance
> on getting my National Instruments PCMCIA-GPIB card working with
> linux-gpib-4.3.0.
>
> TL;DR: Are there better instructions for getting PCMCIA cards to work with
> linux-gpib than is what is contained in "linux-gpib-user-4.3.0/INSTALL"?
>
> Full details:
> I am running CentOS 7.7.1908, with a custom kernel
> (3.10.0-1062.18.1.rt56.1044.el7.x86_64). I have successfully built the
> kernel driver and installed the user space package. The instructions
> contained in the linux-gpib-user-4.3.0/INSTALL file appear to be very
> outdated for PCMCIA, as it makes reference to the cardmgr daemon (as far as
> I know cardmgr was replaced by pccardctl and lspcmcia). I edited the
> "board_type" field in "/etc/gpib.conf" to "ni_pcmcia". As instructed, I
> copied the etc/pcmcia subdirectory to /etc/pcmcia. I am assuming the script
> "/etc/pcmcia/linux-gpib-pcmcia" is supposed to be run somehow, when a
> pcmcia card is inserted, but I am unable to get it to run from the
> terminal. I am able to insert the kernel module drivers: gpib_common,
> nec7210, tnt4882, but when try issuing the command:
> $ sudo gpib_config 0
> , I get:
> failed to configure boardtype: ni_pcmcia
> failed to configure board
> main: Invalid argument
> I checked the output of dmesg after inserting the drivers and see that the
> following interfaces get registered:
> [ 1495.671213] gpib: registered ni_isa interface
> [ 1495.671220] gpib: registered ni_isa_accel interface
> [ 1495.671223] gpib: registered ni_nat4882_isa interface
> [ 1495.671225] gpib: registered ni_nat4882_isa_accel interface
> [ 1495.671227] gpib: registered ni_nec_isa interface
> [ 1495.671229] gpib: registered ni_nec_isa_accel interface
> [ 1495.671231] gpib: registered ni_pci interface
> [ 1495.671233] gpib: registered ni_pci_accel interface
> ni_pcmcia is nowhere to be found. Looking in the tnt4882 driver source, I
> see that all the above listed interfaces have definitions in
> "tnt4882_init.c" which I assume contains all the initialization routines
> when the drive module is inserted in the kernel. The pcmcia init routines
> are found in "tnt4882_cs.c". It seems that PCMCIA is a dying bus interface
> and am wondering if maybe the ni_pcmcia routines should have been added to
> "tnt4882_init.c" some time ago or am I doing something wrong? Thanks for
> the help and reading my lengthy email.
>
> Mitchell
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] PCMCIA GPIB help with linux-gpib-4.3.0

[Mitchell C. <mo....@gm...>]

Hi, I'm new to the Linux-GPIB community and am hoping to get some guidance
on getting my National Instruments PCMCIA-GPIB card working with
linux-gpib-4.3.0.

TL;DR: Are there better instructions for getting PCMCIA cards to work with
linux-gpib than is what is contained in "linux-gpib-user-4.3.0/INSTALL"?

Full details:
I am running CentOS 7.7.1908, with a custom kernel
(3.10.0-1062.18.1.rt56.1044.el7.x86_64). I have successfully built the
kernel driver and installed the user space package. The instructions
contained in the linux-gpib-user-4.3.0/INSTALL file appear to be very
outdated for PCMCIA, as it makes reference to the cardmgr daemon (as far as
I know cardmgr was replaced by pccardctl and lspcmcia). I edited the
"board_type" field in "/etc/gpib.conf" to "ni_pcmcia". As instructed, I
copied the etc/pcmcia subdirectory to /etc/pcmcia. I am assuming the script
"/etc/pcmcia/linux-gpib-pcmcia" is supposed to be run somehow, when a
pcmcia card is inserted, but I am unable to get it to run from the
terminal. I am able to insert the kernel module drivers: gpib_common,
nec7210, tnt4882, but when try issuing the command:
$ sudo gpib_config 0
, I get:
failed to configure boardtype: ni_pcmcia
failed to configure board
main: Invalid argument
I checked the output of dmesg after inserting the drivers and see that the
following interfaces get registered:
[ 1495.671213] gpib: registered ni_isa interface
[ 1495.671220] gpib: registered ni_isa_accel interface
[ 1495.671223] gpib: registered ni_nat4882_isa interface
[ 1495.671225] gpib: registered ni_nat4882_isa_accel interface
[ 1495.671227] gpib: registered ni_nec_isa interface
[ 1495.671229] gpib: registered ni_nec_isa_accel interface
[ 1495.671231] gpib: registered ni_pci interface
[ 1495.671233] gpib: registered ni_pci_accel interface
ni_pcmcia is nowhere to be found. Looking in the tnt4882 driver source, I
see that all the above listed interfaces have definitions in
"tnt4882_init.c" which I assume contains all the initialization routines
when the drive module is inserted in the kernel. The pcmcia init routines
are found in "tnt4882_cs.c". It seems that PCMCIA is a dying bus interface
and am wondering if maybe the ni_pcmcia routines should have been added to
"tnt4882_init.c" some time ago or am I doing something wrong? Thanks for
the help and reading my lengthy email.

Mitchell

Re: [Linux-gpib-general] Problem installing driver on CentOS8

[Søren K. <sq...@dt...>]

Hi Frank.


Thanks a lot for the suggestion.

I tried it yesterday, and changing uaccess.h fixed the issue and the
driver now works as it should and I can 'talk' to the Solartron 1260 FRA :-)

I am sorry that i din not have time to test the suggestion before now,
but our IT department had messed up on the network configuration for
that server and i was not that keen on messing with a server where it
sometimes got the wrong IP address.....


Again, thanks a lot for the help.


Best regards

Søren koch


On 2/20/20 12:03 AM, Frank Mori Hess wrote:
> On Wed, Feb 19, 2020 at 5:11 AM Søren Koch via Linux-gpib-general
> <lin...@li...> wrote:
>> I have just tried to installl Linux-gpib-4.3 on a new CentOS 8 system,
>> and i get the following error when running make:
>> error: macro "access_ok" passed 3 arguments, but takes just 2
> It looks like redhat backported the linux 5.0 change to access_ok to
> their 4.18 kernel.  You can work around the problem by editing
> linux-gpib-kernel/compat/include/linux/uaccess.h and forcing it to use
> the definition of COMPAT_ACCESS_OK
>  that uses the 2 argument version of access_ok

-- 
Søren Koch
Senior Development Engineer
Mob: +45 21325247
sq...@dt...
Fysikvej
Building 310
2800 Kgs. Lyngby

Re: [Linux-gpib-general] Problem installing driver on CentOS8

[Frank M. H. <fm...@gm...>]

On Wed, Feb 19, 2020 at 5:11 AM Søren Koch via Linux-gpib-general
<lin...@li...> wrote:
> I have just tried to installl Linux-gpib-4.3 on a new CentOS 8 system,
> and i get the following error when running make:

> error: macro "access_ok" passed 3 arguments, but takes just 2

It looks like redhat backported the linux 5.0 change to access_ok to
their 4.18 kernel.  You can work around the problem by editing
linux-gpib-kernel/compat/include/linux/uaccess.h and forcing it to use
the definition of COMPAT_ACCESS_OK
 that uses the 2 argument version of access_ok

[Linux-gpib-general] Problem installing driver on CentOS8

[Søren K. <sq...@dt...>]

Hi all.


I have just tried to installl Linux-gpib-4.3 on a new CentOS 8 system,
and i get the following error when running make:


[root@trolley-08 linux-gpib-kernel-4.3.0]# make
make -C /lib/modules/`uname -r`/build V=0 modules \
    M="$PWD/drivers/gpib" \
    GPIB_TOP_DIR=$PWD \
    CONFIG_GPIB_ISA="" \
    HAVE_DEV_OF_NODE= \
    GPIB_CONFIG_KERNEL_DEBUG=0
make[1]: Entering directory '/usr/src/kernels/4.18.0-147.5.1.el8_1.x86_64'
  CC [M] 
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.o
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:
In function ‘read_ioctl’:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:565:52:
error: macro "access_ok" passed 3 arguments, but takes just 2
  if(!COMPAT_ACCESS_OK(VERIFY_WRITE, userbuf, remain))
                                                    ^
In file included from ./include/asm-generic/termios.h:6,
                 from ./arch/x86/include/uapi/asm/termios.h:1,
                 from ./include/uapi/linux/termios.h:6,
                 from ./include/linux/tty.h:7,
                 from
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/ibsys.h:5,
                 from
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:18:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/compat/include/linux/uaccess.h:26:2:
error: ‘access_ok’ undeclared (first use in this function)
  access_ok(type, addr, size)
  ^~~~~~~~~
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:565:6:
note: in expansion of macro ‘COMPAT_ACCESS_OK’
  if(!COMPAT_ACCESS_OK(VERIFY_WRITE, userbuf, remain))
      ^~~~~~~~~~~~~~~~
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/compat/include/linux/uaccess.h:26:2:
note: each undeclared identifier is reported only once for each function
it appears in
  access_ok(type, addr, size)
  ^~~~~~~~~
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:565:6:
note: in expansion of macro ‘COMPAT_ACCESS_OK’
  if(!COMPAT_ACCESS_OK(VERIFY_WRITE, userbuf, remain))
      ^~~~~~~~~~~~~~~~
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:
In function ‘command_ioctl’:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:640:51:
error: macro "access_ok" passed 3 arguments, but takes just 2
  if(!COMPAT_ACCESS_OK(VERIFY_READ, userbuf, remain))
                                                   ^
In file included from ./include/asm-generic/termios.h:6,
                 from ./arch/x86/include/uapi/asm/termios.h:1,
                 from ./include/uapi/linux/termios.h:6,
                 from ./include/linux/tty.h:7,
                 from
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/ibsys.h:5,
                 from
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:18:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/compat/include/linux/uaccess.h:26:2:
error: ‘access_ok’ undeclared (first use in this function)
  access_ok(type, addr, size)
  ^~~~~~~~~
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:640:6:
note: in expansion of macro ‘COMPAT_ACCESS_OK’
  if(!COMPAT_ACCESS_OK(VERIFY_READ, userbuf, remain))
      ^~~~~~~~~~~~~~~~
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:
In function ‘write_ioctl’:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:719:51:
error: macro "access_ok" passed 3 arguments, but takes just 2
  if(!COMPAT_ACCESS_OK(VERIFY_READ, userbuf, remain))
                                                   ^
In file included from ./include/asm-generic/termios.h:6,
                 from ./arch/x86/include/uapi/asm/termios.h:1,
                 from ./include/uapi/linux/termios.h:6,
                 from ./include/linux/tty.h:7,
                 from
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/ibsys.h:5,
                 from
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:18:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/compat/include/linux/uaccess.h:26:2:
error: ‘access_ok’ undeclared (first use in this function)
  access_ok(type, addr, size)
  ^~~~~~~~~
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.c:719:6:
note: in expansion of macro ‘COMPAT_ACCESS_OK’
  if(!COMPAT_ACCESS_OK(VERIFY_READ, userbuf, remain))
      ^~~~~~~~~~~~~~~~
make[3]: *** [scripts/Makefile.build:313:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys/osfuncs.o]
Error 1
make[2]: *** [scripts/Makefile.build:553:
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/sys] Error 2
make[1]: *** [Makefile:1547:
_module_/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib] Error 2
make[1]: Leaving directory '/usr/src/kernels/4.18.0-147.5.1.el8_1.x86_64'
make: [Makefile:9: all] Error 2 (ignored)
[root@trolley-08 linux-gpib-kernel-4.3.0]#

I can run make install, but I can not load the driver:

[root@trolley-08 linux-gpib-kernel-4.3.0]# make install
make -C /lib/modules/`uname -r`/build V=0 modules_install\
    M="$PWD/drivers/gpib" \
    GPIB_TOP_DIR=$PWD \
    INSTALL_MOD_DIR=gpib
make[1]: Entering directory '/usr/src/kernels/4.18.0-147.5.1.el8_1.x86_64'
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/agilent_82350b/agilent_82350b.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/agilent_82350b/agilent_82350b.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/agilent_82350b/agilent_82350b.ko:
No such file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/agilent_82357a/agilent_82357a.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/agilent_82357a/agilent_82357a.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/agilent_82357a/agilent_82357a.ko:
No such file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/cb7210/cb7210.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/cb7210/cb7210.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/cb7210/cb7210.ko: No such
file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/cec/cec_gpib.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/cec/cec_gpib.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/cec/cec_gpib.ko: No such
file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/hp_82335/hp82335.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/hp_82335/hp82335.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/hp_82335/hp82335.ko: No
such file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/hp_82341/hp_82341.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/hp_82341/hp_82341.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/hp_82341/hp_82341.ko: No
such file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/ines/ines_gpib.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/ines/ines_gpib.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/ines/ines_gpib.ko: No such
file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/lpvo_usb_gpib/lpvo_usb_gpib.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/lpvo_usb_gpib/lpvo_usb_gpib.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/lpvo_usb_gpib/lpvo_usb_gpib.ko:
No such file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/nec7210/nec7210.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/nec7210/nec7210.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/nec7210/nec7210.ko: No
such file or directory
  INSTALL
/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/ni_usb/ni_usb_gpib.ko
cp: cannot stat
'/root/linux-gpib-4.3.0/linux-gpib-kernel-4.3.0/drivers/gpib/ni_usb/ni_usb_gpib.ko':
No such file or directory
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory:
crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
crypto/bio/bss_file.c:79
sign-file:
/lib/modules/4.18.0-147.5.1.el8_1.x86_64/gpib/ni_usb/ni_usb_gpib.ko: No
such file or directory
  DEPMOD  4.18.0-147.5.1.el8_1.x86_64
make[1]: Leaving directory '/usr/src/kernels/4.18.0-147.5.1.el8_1.x86_64'
[root@trolley-08 linux-gpib-kernel-4.3.0]#


When running modprobe I get this:

[root@trolley-08 linux-gpib-kernel-4.3.0]# modprobe tnt4882
modprobe: FATAL: Module tnt4882 not found in directory
/lib/modules/4.18.0-147.5.1.el8_1.x86_64
[root@trolley-08 linux-gpib-kernel-4.3.0]#

(I am using a NI-gpib card and on CentOS7 it worked with version 4.2.0)


I have also tried without luck to install 4.2.0, but apparently the
change from CewntOS7 to 8 broke something....


My system is a fully updated and freshly installed CentOS8:

[root@trolley-08 linux-gpib-kernel-4.3.0]# uname -a
Linux trolley-08.energy.dtu.dk 4.18.0-147.5.1.el8_1.x86_64 #1 SMP Wed
Feb 5 02:00:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@trolley-08 linux-gpib-kernel-4.3.0]#


I hope that someone can help out so I can get the driver to install
properly.


Best regards


-- 
Søren Koch
Senior Development Engineer
DTU Energy
-------------------------------------------
Technical University of Denmark
Department of Energy Conversion and Storage
Fysikvej
Building 310, 1.sal
2800 Kongens Lyngby
Direct +45 46775816
sq...@dt...
http://www.ecs.dtu.dk

Re: [Linux-gpib-general] Fwd: Re: gpib0 device missing

[Bruno G. <bg...@au...>]

Thank you all for your help.

I just had to load the appropriate module.. (tnt4882, obtained from 
https://linux-gpib.sourceforge.io/doc_html/supported-hardware.html).

So I ran:
modprobe tnt4882
and then the command gpib_config worked fine.

Thank you again for your quick helps.

Cheers,

Bruno

On 2/18/20 11:19 AM, Richard Klingler wrote:
> From my memory I would say you don't have privileges to access 
> /dev/gpib0...
>
> So add your user account to the gpib group...
>
> cheers
> richard
>
>
> Am Di., 18. Feb. 2020 um 11:13 Uhr schrieb Bruno Garbin 
> <bg...@au... <mailto:bg...@au...>>:
>
>     Hi
>
>     The card is recognized. lspci gives
>     10:00.0 Communication controller: National Instruments PCI-GPIB
>     (rev 01)
>
>     Also I issued the commands
>
>       * depmod -ae (make it possible for modprobe to see the new modules)
>       * modprobe gpib_common
>       * modprobe agilent_82357a
>
>     Now the /dev/gpib[0-15] devices are created !!
>     However, ibtest fails :
>
>     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]: 10
>     trying to open pad = 10 on /dev/gpib0 ...
>     libgpib: IBOPENDEV ioctl failed
>     libgpib: error in is_cic()!
>     ibdev error
>
>     ibsta = 0x8000  < ERR >
>     iberr= 0
>     EDVR 0: OS error
>
>     ibcntl = 19
>     Aborted (core dumped)
>
>     Any idea ?
>
>     Thanks in advance
>
>     On 2/18/20 10:20 AM, Richard Klingler wrote:
>>     Well
>>
>>     Is your GPIB adapter recognized by Linux at all? DO you see it
>>     with lsusb/lspci?
>>
>>     To my (older ;o) knowledge it won't create any /dev/gpibX entries
>>     when there is no adapter recognized...
>>
>>     cheers
>>     richard
>>
>>
>>     Am Di., 18. Feb. 2020 um 10:13 Uhr schrieb Bruno Garbin
>>     <bg...@au... <mailto:bg...@au...>>:
>>
>>         Dear all,
>>
>>         can anyone help?
>>
>>         Thank you in advance,
>>
>>         Bruno
>>
>>         -------- Forwarded Message --------
>>         Subject: 	Re: [Linux-gpib-general] gpib0 device missing
>>         Date: 	Sat, 15 Feb 2020 11:23:16 +0100
>>         From: 	Bruno Garbin <bg...@au...>
>>         <mailto:bg...@au...>
>>         To: 	Thomas Klima <ele...@gm...>
>>         <mailto:ele...@gm...>
>>
>>
>>
>>         Hi Thomas,
>>
>>         thanks for your reply.
>>
>>         I just installed the kernel drivers in the same way
>>         (configure, make, make install) and run the command gpib_config.
>>         This returned me the error:
>>         failed to open device file '/dev/gpib0'
>>         main: No such file or directory
>>
>>         Do you have any idea of what is going wrong here?
>>
>>         Thank you in advance.
>>
>>         Kind regards,
>>
>>         Bruno garbin
>>
>>
>>         On 15/02/20 10:53 am, Thomas Klima wrote:
>>>         Hi,
>>>
>>>         On Fri, 14 Feb 2020 18:40:22 +0100
>>>         Bruno Garbin <bg...@au...>
>>>         <mailto:bg...@au...> wrote:
>>>>         I have installed linux-gpib on my machine (kernel 5.3.0-28
>>>>         Ubuntu
>>>>         18.04) and /dev/gpib0 is not created after the install of
>>>>         linux-gpib-user-4.3.0. What should I do ?
>>>         You need the kernel drivers (linux-gpib-kernel-...), a
>>>         config file
>>>         (/etc/gpib.conf) and then run gpib_config - this creates the
>>>         device
>>>         files under /dev
>>>
>>>         hth,
>>>         Thomas
>>>
>>>
>>>         _______________________________________________
>>>         Linux-gpib-general mailing list
>>>         Lin...@li...
>>>         <mailto:Lin...@li...>
>>>         https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>         _______________________________________________
>>         Linux-gpib-general mailing list
>>         Lin...@li...
>>         <mailto:Lin...@li...>
>>         https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>
>>
>>
>>     _______________________________________________
>>     Linux-gpib-general mailing list
>>     Lin...@li...  <mailto:Lin...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>     _______________________________________________
>     Linux-gpib-general mailing list
>     Lin...@li...
>     <mailto:Lin...@li...>
>     https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Fwd: Re: gpib0 device missing

[Richard K. <ric...@gm...>]

>From my memory I would say you don't have privileges to access /dev/gpib0...

So add your user account to the gpib group...

cheers
richard


Am Di., 18. Feb. 2020 um 11:13 Uhr schrieb Bruno Garbin <
bg...@au...>:

> Hi
>
> The card is recognized. lspci gives
> 10:00.0 Communication controller: National Instruments PCI-GPIB (rev 01)
>
> Also I issued the commands
>
>    - depmod -ae (make it possible for modprobe to see the new modules)
>    - modprobe gpib_common
>    - modprobe agilent_82357a
>
> Now the /dev/gpib[0-15] devices are created !!
> However, ibtest fails :
>
> 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]: 10
> trying to open pad = 10 on /dev/gpib0 ...
> libgpib: IBOPENDEV ioctl failed
> libgpib: error in is_cic()!
> ibdev error
>
> ibsta = 0x8000  < ERR >
> iberr= 0
> EDVR 0: OS error
>
> ibcntl = 19
> Aborted (core dumped)
>
> Any idea ?
>
> Thanks in advance
>
> On 2/18/20 10:20 AM, Richard Klingler wrote:
>
> Well
>
> Is your GPIB adapter recognized by Linux at all? DO you see it with
> lsusb/lspci?
>
> To my (older ;o) knowledge it won't create any /dev/gpibX entries when
> there is no adapter recognized...
>
> cheers
> richard
>
>
> Am Di., 18. Feb. 2020 um 10:13 Uhr schrieb Bruno Garbin <
> bg...@au...>:
>
>> Dear all,
>>
>> can anyone help?
>>
>> Thank you in advance,
>>
>> Bruno
>> -------- Forwarded Message --------
>> Subject: Re: [Linux-gpib-general] gpib0 device missing
>> Date: Sat, 15 Feb 2020 11:23:16 +0100
>> From: Bruno Garbin <bg...@au...>
>> <bg...@au...>
>> To: Thomas Klima <ele...@gm...> <ele...@gm...>
>>
>> Hi Thomas,
>>
>> thanks for your reply.
>>
>> I just installed the kernel drivers in the same way (configure, make,
>> make install) and run the command gpib_config.
>> This returned me the error:
>> failed to open device file '/dev/gpib0'
>> main: No such file or directory
>>
>> Do you have any idea of what is going wrong here?
>>
>> Thank you in advance.
>>
>> Kind regards,
>>
>> Bruno garbin
>>
>>
>> On 15/02/20 10:53 am, Thomas Klima wrote:
>>
>> Hi,
>>
>> On Fri, 14 Feb 2020 18:40:22 +0100
>> Bruno Garbin <bg...@au...> <bg...@au...>
>> wrote:
>>
>> I have installed linux-gpib on my machine (kernel 5.3.0-28 Ubuntu
>> 18.04) and /dev/gpib0 is not created after the install of
>> linux-gpib-user-4.3.0. What should I do ?
>>
>> You need the kernel drivers (linux-gpib-kernel-...), a config file
>> (/etc/gpib.conf) and then run gpib_config - this creates the device
>> files under /dev
>>
>> hth,
>> Thomas
>>
>>
>> _______________________________________________
>> Linux-gpib-general mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>
>> _______________________________________________
>> Linux-gpib-general mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>
>
>
> _______________________________________________
> Linux-gpib-general mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Fwd: Re: gpib0 device missing

[Bruno G. <bg...@au...>]

Hi

The card is recognized. lspci gives
10:00.0 Communication controller: National Instruments PCI-GPIB (rev 01)

Also I issued the commands

  * depmod -ae (make it possible for modprobe to see the new modules)
  * modprobe gpib_common
  * modprobe agilent_82357a

Now the /dev/gpib[0-15] devices are created !!
However, ibtest fails :

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]: 10
trying to open pad = 10 on /dev/gpib0 ...
libgpib: IBOPENDEV ioctl failed
libgpib: error in is_cic()!
ibdev error

ibsta = 0x8000  < ERR >
iberr= 0
EDVR 0: OS error

ibcntl = 19
Aborted (core dumped)

Any idea ?

Thanks in advance

On 2/18/20 10:20 AM, Richard Klingler wrote:
> Well
>
> Is your GPIB adapter recognized by Linux at all? DO you see it with 
> lsusb/lspci?
>
> To my (older ;o) knowledge it won't create any /dev/gpibX entries when 
> there is no adapter recognized...
>
> cheers
> richard
>
>
> Am Di., 18. Feb. 2020 um 10:13 Uhr schrieb Bruno Garbin 
> <bg...@au... <mailto:bg...@au...>>:
>
>     Dear all,
>
>     can anyone help?
>
>     Thank you in advance,
>
>     Bruno
>
>     -------- Forwarded Message --------
>     Subject: 	Re: [Linux-gpib-general] gpib0 device missing
>     Date: 	Sat, 15 Feb 2020 11:23:16 +0100
>     From: 	Bruno Garbin <bg...@au...>
>     <mailto:bg...@au...>
>     To: 	Thomas Klima <ele...@gm...>
>     <mailto:ele...@gm...>
>
>
>
>     Hi Thomas,
>
>     thanks for your reply.
>
>     I just installed the kernel drivers in the same way (configure,
>     make, make install) and run the command gpib_config.
>     This returned me the error:
>     failed to open device file '/dev/gpib0'
>     main: No such file or directory
>
>     Do you have any idea of what is going wrong here?
>
>     Thank you in advance.
>
>     Kind regards,
>
>     Bruno garbin
>
>
>     On 15/02/20 10:53 am, Thomas Klima wrote:
>>     Hi,
>>
>>     On Fri, 14 Feb 2020 18:40:22 +0100
>>     Bruno Garbin <bg...@au...>
>>     <mailto:bg...@au...> wrote:
>>>     I have installed linux-gpib on my machine (kernel 5.3.0-28 Ubuntu
>>>     18.04) and /dev/gpib0 is not created after the install of
>>>     linux-gpib-user-4.3.0. What should I do ?
>>     You need the kernel drivers (linux-gpib-kernel-...), a config file
>>     (/etc/gpib.conf) and then run gpib_config - this creates the device
>>     files under /dev
>>
>>     hth,
>>     Thomas
>>
>>
>>     _______________________________________________
>>     Linux-gpib-general mailing list
>>     Lin...@li...
>>     <mailto:Lin...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>     _______________________________________________
>     Linux-gpib-general mailing list
>     Lin...@li...
>     <mailto:Lin...@li...>
>     https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general

Re: [Linux-gpib-general] Fwd: Re: gpib0 device missing

[Thomas K. <ele...@gm...>]

Hi,

what gpib hardware are you using?
Please post your gpib.conf and the tail of your syslog
(to see if the driver loading was successful)

have fun,
Thomas

On Tue, 18 Feb 2020 09:40:29 +0100
Bruno Garbin <bg...@au...> wrote:

> Dear all,
> 
> can anyone help?
> 
> Thank you in advance,
> 
> Bruno
> 
> -------- Forwarded Message --------
> Subject: 	Re: [Linux-gpib-general] gpib0 device missing
> Date: 	Sat, 15 Feb 2020 11:23:16 +0100
> From: 	Bruno Garbin <bg...@au...>
> To: 	Thomas Klima <ele...@gm...>
> 
> 
> 
> Hi Thomas,
> 
> thanks for your reply.
> 
> I just installed the kernel drivers in the same way (configure, make, 
> make install) and run the command gpib_config.
> This returned me the error:
> failed to open device file '/dev/gpib0'
> main: No such file or directory
> 
> Do you have any idea of what is going wrong here?
> 
> Thank you in advance.
> 
> Kind regards,
> 
> Bruno garbin
> 
> 
> On 15/02/20 10:53 am, Thomas Klima wrote:
> > Hi,
> >
> > On Fri, 14 Feb 2020 18:40:22 +0100
> > Bruno Garbin <bg...@au...> wrote:  
> >> I have installed linux-gpib on my machine (kernel 5.3.0-28 Ubuntu
> >> 18.04) and /dev/gpib0 is not created after the install of
> >> linux-gpib-user-4.3.0. What should I do ?  
> > You need the kernel drivers (linux-gpib-kernel-...), a config file
> > (/etc/gpib.conf) and then run gpib_config - this creates the device
> > files under /dev
> >
> > hth,
> > Thomas
> >
> >
> > _______________________________________________
> > Linux-gpib-general mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general  

Re: [Linux-gpib-general] Fwd: Re: gpib0 device missing

[Richard K. <ric...@gm...>]

Well

Is your GPIB adapter recognized by Linux at all? DO you see it with
lsusb/lspci?

To my (older ;o) knowledge it won't create any /dev/gpibX entries when
there is no adapter recognized...

cheers
richard


Am Di., 18. Feb. 2020 um 10:13 Uhr schrieb Bruno Garbin <
bg...@au...>:

> Dear all,
>
> can anyone help?
>
> Thank you in advance,
>
> Bruno
> -------- Forwarded Message --------
> Subject: Re: [Linux-gpib-general] gpib0 device missing
> Date: Sat, 15 Feb 2020 11:23:16 +0100
> From: Bruno Garbin <bg...@au...> <bg...@au...>
> To: Thomas Klima <ele...@gm...> <ele...@gm...>
>
> Hi Thomas,
>
> thanks for your reply.
>
> I just installed the kernel drivers in the same way (configure, make, make
> install) and run the command gpib_config.
> This returned me the error:
> failed to open device file '/dev/gpib0'
> main: No such file or directory
>
> Do you have any idea of what is going wrong here?
>
> Thank you in advance.
>
> Kind regards,
>
> Bruno garbin
>
>
> On 15/02/20 10:53 am, Thomas Klima wrote:
>
> Hi,
>
> On Fri, 14 Feb 2020 18:40:22 +0100
> Bruno Garbin <bg...@au...> <bg...@au...>
> wrote:
>
> I have installed linux-gpib on my machine (kernel 5.3.0-28 Ubuntu
> 18.04) and /dev/gpib0 is not created after the install of
> linux-gpib-user-4.3.0. What should I do ?
>
> You need the kernel drivers (linux-gpib-kernel-...), a config file
> (/etc/gpib.conf) and then run gpib_config - this creates the device
> files under /dev
>
> hth,
> Thomas
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] Fwd: Re: gpib0 device missing

[Bruno G. <bg...@au...>]

Dear all,

can anyone help?

Thank you in advance,

Bruno

-------- Forwarded Message --------
Subject: 	Re: [Linux-gpib-general] gpib0 device missing
Date: 	Sat, 15 Feb 2020 11:23:16 +0100
From: 	Bruno Garbin <bg...@au...>
To: 	Thomas Klima <ele...@gm...>



Hi Thomas,

thanks for your reply.

I just installed the kernel drivers in the same way (configure, make, 
make install) and run the command gpib_config.
This returned me the error:
failed to open device file '/dev/gpib0'
main: No such file or directory

Do you have any idea of what is going wrong here?

Thank you in advance.

Kind regards,

Bruno garbin


On 15/02/20 10:53 am, Thomas Klima wrote:
> Hi,
>
> On Fri, 14 Feb 2020 18:40:22 +0100
> Bruno Garbin <bg...@au...> wrote:
>> I have installed linux-gpib on my machine (kernel 5.3.0-28 Ubuntu
>> 18.04) and /dev/gpib0 is not created after the install of
>> linux-gpib-user-4.3.0. What should I do ?
> You need the kernel drivers (linux-gpib-kernel-...), a config file
> (/etc/gpib.conf) and then run gpib_config - this creates the device
> files under /dev
>
> hth,
> Thomas
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general

Re: [Linux-gpib-general] gpib0 device missing

[Thomas K. <ele...@gm...>]

Hi,

On Fri, 14 Feb 2020 18:40:22 +0100
Bruno Garbin <bg...@au...> wrote:
> I have installed linux-gpib on my machine (kernel 5.3.0-28 Ubuntu
> 18.04) and /dev/gpib0 is not created after the install of 
> linux-gpib-user-4.3.0. What should I do ?

You need the kernel drivers (linux-gpib-kernel-...), a config file
(/etc/gpib.conf) and then run gpib_config - this creates the device
files under /dev

hth,
Thomas

[Linux-gpib-general] gpib0 device missing

[Bruno G. <bg...@au...>]

Hi

I have installed linux-gpib on my machine (kernel 5.3.0-28 Ubuntu 18.04) 
and /dev/gpib0 is not created after the install of 
linux-gpib-user-4.3.0. What should I do ?

Thanks in advance

Bruno

Re: [Linux-gpib-general] Problem setting up two USB adapters; unable to attach any USB adapter to a port other than /dev/gpib0

[dave p. <dpe...@gm...>]

Hi Joerg,
Judging from this line:
Feb  9 10:32:39 raspberrypi /usr/local/lib/udev/gpib_udev_config:
gpib_config options: --minor 2 --board-type agilent_82357a
the script is working properly. Have you set the agilent to use minor 2 in
your gpib.conf as well ? Please send your gpib.conf and udev rules.
cheers,
-Dave

On Sun, 9 Feb 2020 at 12:11, J. Sommersberg <js...@gm...> wrote:

> Hi,
>
> i have two  USB-GPIB adapters. Agilent 82357B ( 90 Bucks „new“ on ebay;
> most probably copy ) and Keithley KUSB-488.
> They are both working fine if only one is used.
> But i am not able to use them both attached at the same time.
>
> I did struggle a bit with the udev rules but am now pretty confident that
> i have that set up properly.
> Since product id or serial did not work reliable i cut it down to just the
> manufacturer to decide which port to use.
> If i interpret the below messages correct than it is successful.
> It just seems that somewhere in the process of attaching my wish is
> getting ignored.
> I switched between Keithley and Agilent for "—minor 1“ but it makes no
> difference.
> I also tried a higher port „—minor 2“ and that also makes no difference.
>
> From the below messages you can see that gpib_udev_config is sending the
> correct options to gpib_config.
> Next message is always "kernel: gpibx: exiting autospoll thread" ( where x
> is the corresponding number of „—-minor x“ option)
> Thereafter comes the "detach message" followed by the "attach to interface
> 0“ message.
> I did surf the source files a bit and in
> /linux-gpib-kernel/drivers/gpib/sys/init.c i found the function that is
> printing the „exiting autospoll thread“.
>
> static int autospoll_thread(void *board_void)
>
> -snip
>
> printk("gpib%i: exiting autospoll thread\n", board->minor);
>
>
> Another interesting aspect is that the „detached“ message will not appear
> after you pull the USB cable.
> It will appear after the next connect after „exiting autospoll“ message.
>
>
> Right know i dont have enough insight to the mechanism and the structure
> of the whole process so i can not troubleshoot further.
> Should i increase verbosity of the driver/module? How?
> Anything else i could try?
>
> Best regards
>
> Joerg
>
>
> ———————————————————copy & paste of /var/log/messages after a
> disonnect/connect----------------
>
>
> Feb  9 10:29:49 raspberrypi kernel: [  153.631303] usb 1-1.4: USB
> disconnect, device number 10
> Feb  9 10:32:35 raspberrypi kernel: [  319.302157] usb 1-1.4: new
> high-speed USB device number 11 using dwc_otg
> Feb  9 10:32:35 raspberrypi kernel: [  319.432611] usb 1-1.4: New USB
> device found, idVendor=0957, idProduct=0518, bcdDevice= 0.00
> Feb  9 10:32:35 raspberrypi kernel: [  319.432627] usb 1-1.4: New USB
> device strings: Mfr=0, Product=0, SerialNumber=0
> Feb  9 10:32:35 raspberrypi mtp-probe: checking bus 1, device 11:
> "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
> Feb  9 10:32:35 raspberrypi mtp-probe: bus: 1, device: 11 was not an MTP
> device
> Feb  9 10:32:35 raspberrypi /usr/local/lib/udev/gpib_udev_fxloader:
> loading firmware /usr/local/share/usb/agilent_82357a/measat_releaseX1.8.hex
> for 957/518/0 to /dev/bus/usb/001/011
> Feb  9 10:32:35 raspberrypi kernel: [  319.519318] usb 1-1.4: USB
> disconnect, device number 11
> Feb  9 10:32:37 raspberrypi kernel: [  321.352162] usb 1-1.4: new
> high-speed USB device number 12 using dwc_otg
> Feb  9 10:32:37 raspberrypi kernel: [  321.482606] usb 1-1.4: New USB
> device found, idVendor=0957, idProduct=0518, bcdDevice= 0.00
> Feb  9 10:32:37 raspberrypi kernel: [  321.482622] usb 1-1.4: New USB
> device strings: Mfr=0, Product=0, SerialNumber=0
> Feb  9 10:32:37 raspberrypi mtp-probe: checking bus 1, device 12:
> "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
> Feb  9 10:32:37 raspberrypi mtp-probe: bus: 1, device: 12 was not an MTP
> device
> Feb  9 10:32:37 raspberrypi /usr/local/lib/udev/gpib_udev_fxloader:
> loading firmware /usr/local/share/usb/agilent_82357a/measat_releaseX1.8.hex
> for 957/518/0 to /dev/bus/usb/001/012
> Feb  9 10:32:37 raspberrypi kernel: [  321.567331] usb 1-1.4: USB
> disconnect, device number 12
> Feb  9 10:32:39 raspberrypi kernel: [  323.402162] usb 1-1.4: new
> high-speed USB device number 13 using dwc_otg
> Feb  9 10:32:39 raspberrypi kernel: [  323.533080] usb 1-1.4: New USB
> device found, idVendor=0957, idProduct=0718, bcdDevice= 0.00
> Feb  9 10:32:39 raspberrypi kernel: [  323.533094] usb 1-1.4: New USB
> device strings: Mfr=1, Product=2, SerialNumber=5
> Feb  9 10:32:39 raspberrypi kernel: [  323.533104] usb 1-1.4: Product:
> 82357B ()
> Feb  9 10:32:39 raspberrypi kernel: [  323.533115] usb 1-1.4:
> Manufacturer: Agilent Technologies, Inc.
> Feb  9 10:32:39 raspberrypi kernel: [  323.533124] usb 1-1.4:
> SerialNumber: MY49451763
> Feb  9 10:32:39 raspberrypi kernel: [  323.534081] probe succeeded for
> path: usb-3f980000.usb-1.4
> Feb  9 10:32:39 raspberrypi mtp-probe: checking bus 1, device 13:
> "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
> Feb  9 10:32:39 raspberrypi mtp-probe: bus: 1, device: 13 was not an MTP
> device
> Feb  9 10:32:39 raspberrypi /usr/local/lib/udev/gpib_udev_config: entered
> for Product: 957/718/0 Devpath:
> /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0 Serial:
> MY49451763
> Feb  9 10:32:39 raspberrypi /usr/local/lib/udev/gpib_udev_config:
> gpib_config options: --minor 2 --board-type agilent_82357a
> Feb  9 10:32:39 raspberrypi kernel: [  323.630664] gpib2: exiting
> autospoll thread
> Feb  9 10:32:39 raspberrypi kernel: [  323.630710] agilent_82357a_detach:
> detached
> Feb  9 10:32:39 raspberrypi kernel: [  323.630838] attached to bus
> interface 0, address 0x00d05394
> Feb  9 10:32:39 raspberrypi kernel: [  323.932673] agilent_82357a_attach:
> attached
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] Problem setting up two USB adapters; unable to attach any USB adapter to a port other than /dev/gpib0

[J. S. <js...@gm...>]

Hi,

i have two  USB-GPIB adapters. Agilent 82357B ( 90 Bucks „new“ on ebay; most probably copy ) and Keithley KUSB-488.
They are both working fine if only one is used.
But i am not able to use them both attached at the same time.

I did struggle a bit with the udev rules but am now pretty confident that i have that set up properly.
Since product id or serial did not work reliable i cut it down to just the manufacturer to decide which port to use.
If i interpret the below messages correct than it is successful.
It just seems that somewhere in the process of attaching my wish is getting ignored.
I switched between Keithley and Agilent for "—minor 1“ but it makes no difference.
I also tried a higher port „—minor 2“ and that also makes no difference.

From the below messages you can see that gpib_udev_config is sending the correct options to gpib_config.
Next message is always "kernel: gpibx: exiting autospoll thread" ( where x is the corresponding number of „—-minor x“ option)
Thereafter comes the "detach message" followed by the "attach to interface 0“ message.
I did surf the source files a bit and in /linux-gpib-kernel/drivers/gpib/sys/init.c i found the function that is printing the „exiting autospoll thread“.
static int autospoll_thread(void *board_void)
-snip
printk("gpib%i: exiting autospoll thread\n", board->minor);

Another interesting aspect is that the „detached“ message will not appear after you pull the USB cable.
It will appear after the next connect after „exiting autospoll“ message.


Right know i dont have enough insight to the mechanism and the structure of the whole process so i can not troubleshoot further.
Should i increase verbosity of the driver/module? How?
Anything else i could try?

Best regards

Joerg


———————————————————copy & paste of /var/log/messages after a disonnect/connect----------------


Feb  9 10:29:49 raspberrypi kernel: [  153.631303] usb 1-1.4: USB disconnect, device number 10
Feb  9 10:32:35 raspberrypi kernel: [  319.302157] usb 1-1.4: new high-speed USB device number 11 using dwc_otg
Feb  9 10:32:35 raspberrypi kernel: [  319.432611] usb 1-1.4: New USB device found, idVendor=0957, idProduct=0518, bcdDevice= 0.00
Feb  9 10:32:35 raspberrypi kernel: [  319.432627] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb  9 10:32:35 raspberrypi mtp-probe: checking bus 1, device 11: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Feb  9 10:32:35 raspberrypi mtp-probe: bus: 1, device: 11 was not an MTP device
Feb  9 10:32:35 raspberrypi /usr/local/lib/udev/gpib_udev_fxloader: loading firmware /usr/local/share/usb/agilent_82357a/measat_releaseX1.8.hex for 957/518/0 to /dev/bus/usb/001/011
Feb  9 10:32:35 raspberrypi kernel: [  319.519318] usb 1-1.4: USB disconnect, device number 11
Feb  9 10:32:37 raspberrypi kernel: [  321.352162] usb 1-1.4: new high-speed USB device number 12 using dwc_otg
Feb  9 10:32:37 raspberrypi kernel: [  321.482606] usb 1-1.4: New USB device found, idVendor=0957, idProduct=0518, bcdDevice= 0.00
Feb  9 10:32:37 raspberrypi kernel: [  321.482622] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb  9 10:32:37 raspberrypi mtp-probe: checking bus 1, device 12: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Feb  9 10:32:37 raspberrypi mtp-probe: bus: 1, device: 12 was not an MTP device
Feb  9 10:32:37 raspberrypi /usr/local/lib/udev/gpib_udev_fxloader: loading firmware /usr/local/share/usb/agilent_82357a/measat_releaseX1.8.hex for 957/518/0 to /dev/bus/usb/001/012
Feb  9 10:32:37 raspberrypi kernel: [  321.567331] usb 1-1.4: USB disconnect, device number 12
Feb  9 10:32:39 raspberrypi kernel: [  323.402162] usb 1-1.4: new high-speed USB device number 13 using dwc_otg
Feb  9 10:32:39 raspberrypi kernel: [  323.533080] usb 1-1.4: New USB device found, idVendor=0957, idProduct=0718, bcdDevice= 0.00
Feb  9 10:32:39 raspberrypi kernel: [  323.533094] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Feb  9 10:32:39 raspberrypi kernel: [  323.533104] usb 1-1.4: Product: 82357B ()
Feb  9 10:32:39 raspberrypi kernel: [  323.533115] usb 1-1.4: Manufacturer: Agilent Technologies, Inc.
Feb  9 10:32:39 raspberrypi kernel: [  323.533124] usb 1-1.4: SerialNumber: MY49451763
Feb  9 10:32:39 raspberrypi kernel: [  323.534081] probe succeeded for path: usb-3f980000.usb-1.4
Feb  9 10:32:39 raspberrypi mtp-probe: checking bus 1, device 13: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Feb  9 10:32:39 raspberrypi mtp-probe: bus: 1, device: 13 was not an MTP device
Feb  9 10:32:39 raspberrypi /usr/local/lib/udev/gpib_udev_config: entered for Product: 957/718/0 Devpath: /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0 Serial: MY49451763
Feb  9 10:32:39 raspberrypi /usr/local/lib/udev/gpib_udev_config: gpib_config options: --minor 2 --board-type agilent_82357a
Feb  9 10:32:39 raspberrypi kernel: [  323.630664] gpib2: exiting autospoll thread
Feb  9 10:32:39 raspberrypi kernel: [  323.630710] agilent_82357a_detach: detached
Feb  9 10:32:39 raspberrypi kernel: [  323.630838] attached to bus interface 0, address 0x00d05394
Feb  9 10:32:39 raspberrypi kernel: [  323.932673] agilent_82357a_attach: attached

Re: [Linux-gpib-general] Which Agilent GPIB PCI card to buy?

[Søren K. <sq...@dt...>]

Hi Alex


We have used both NI-PCI and NI-PCIe GPIB-cards and both types works
with the driver (although I have to uncomment the mfh driver line in the
makefile due to som compatibility issues with CentOS7)

However, finding a computer with full size PCI slots is not easy these
days....


Regards

Søren


On 1/15/20 9:06 PM, daturach wrote:
> Hello Alex
>
> I am using a PCI-GPIB model fitted in an old PC. It's just for the fun
> of driving an old Marconi 2955. These boards are quite cheap. You
> should be able to get one for 100 bucks or so.
>
> Walter
>
>
> Le mer. 15 janv. 2020 à 16:12, Alexander Huemer
> <ale...@xx...> a écrit :
>
>     Hi
>
>     Thanks for the insights.
>     A friend of mine suggested to use National Instruments card
>     instead of
>     HP.
>     Taking a look at the supported-hardware page I don't see any notes
>     for
>     the NI PCI cards, which makes me believe they have proper
>     end-of-string
>     detection, therefore better performance and hence the better
>     choice than
>     HP.
>     Is that a correct conclusion?
>
>     It seems like there are a number of different models available
>     from NI. 
>     Anything in particular to prefer?
>
>     Thanks,
>     -Alex
>
>     On Fri, Jan 10, 2020 at 04:02:07PM +0100, dave penkler wrote:
>     > Hallo Alexander,
>     > From a user perspective they are pretty much the same as they
>     use the same
>     > driver. The main difference is that the 82350A requires a firmware
>     > udownload when initialising it. So the 82350B is preferable from
>     that
>     > point. See aslo
>     >
>     https://linux-gpib.sourceforge.io/doc_html/supported-hardware.html#AGILENT-82350B
>     >
>     > Regarding the non-system controller aspect: the cards can be
>     used in this
>     > mode but you need to understand the gpib protocol to program it.
>     > A simple example is here:
>     >
>     https://sourceforge.net/p/linux-gpib/code/HEAD/tree/trunk/linux-gpib-user/examples/slave_read_to_file.c
>     > cheers,
>     > -Dave
>     >
>     > On Fri, 10 Jan 2020 at 13:41, Alexander Huemer
>     <ale...@xx...>
>     > wrote:
>     >
>     > > Hi
>     > >
>     > > I would like to build a small box based on a Soekris 5501 to
>     be able to
>     > > interface various pieces of old test equipment via GPIB.
>     > >
>     > > In case that matters, the test equipment I have with GPIB
>     interfaces
>     > > are:
>     > > * HP 54200A (Oscilloscope)
>     > > * HP 66311B (Power supply)
>     > > * HP  3478A (Multimeter)
>     > > * Rohde & Schwarz CMD53 (Digital Radiocommunication Tester)
>     > >
>     > > I am considering to buy either:
>     > > * HP 82350A Rev. B
>     > > * HP 82350B Rev. A
>     > >
>     > > My question is whether there are any real-world differences
>     between
>     > > these cards from user perspective.
>     > > Looking at pictures of the boards, the implementations seems to be
>     > > significantly different. Having no practical experience with
>     linux-gpib
>     > > yet, I cannot say whether those differences have any effect to
>     the user.
>     > >
>     > > * HP 82350A Rev. B -> Xilinx XC5202 + PLX PCI9050
>     > > * HP 82350B Rev. A -> Xilinx XC2S100, no PLX
>     > >
>     > > My guess would be 'no difference', though I thought I'd ask
>     before I
>     > > buy.
>     > >
>     > > Second question:
>     > > Can these boards act as non-controllers on the bus? I wasn't
>     able to
>     > > find a good explanation of the technical situation in English,
>     only in
>     > > German[1] (my mother tongue).
>     > > Long story short: Some GPIB adapters for general purpose
>     computers can
>     > > react to ATN messages on the bus quickly enough to be able to
>     act as
>     > > non-controllers, some aren't. The time budget is pretty tight
>     for that,
>     > > 200ns, too quickly for interrupt-based implementations.
>     > >
>     > > I believe the ATN responses are the reason one would want to
>     use a PCI
>     > > board instead of a 82357A/B.
>     > > Whether that ATN thing is significantly relevant in another can of
>     > > worms, though we don't have to open that can of worms right now.
>     > >
>     > > -Alex
>     > >
>     > > [1]
>     https://www.mikrocontroller.net/articles/GPIB-RS232-Schnittstelle
>     > >
>     > >
>     > > _______________________________________________
>     > > Linux-gpib-general mailing list
>     > > Lin...@li...
>     <mailto:Lin...@li...>
>     > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>     > >
>
>
>     _______________________________________________
>     Linux-gpib-general mailing list
>     Lin...@li...
>     <mailto:Lin...@li...>
>     https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general

-- 
Søren Koch
Senior Development Engineer
Mob: +45 21325247
sq...@dt...
Fysikvej
Building 310
2800 Kgs. Lyngby

Re: [Linux-gpib-general] Which Agilent GPIB PCI card to buy?

[daturach <dat...@gm...>]

Hello Alex

I am using a PCI-GPIB model fitted in an old PC. It's just for the fun of
driving an old Marconi 2955. These boards are quite cheap. You should be
able to get one for 100 bucks or so.

Walter


Le mer. 15 janv. 2020 à 16:12, Alexander Huemer <ale...@xx...> a
écrit :

> Hi
>
> Thanks for the insights.
> A friend of mine suggested to use National Instruments card instead of
> HP.
> Taking a look at the supported-hardware page I don't see any notes for
> the NI PCI cards, which makes me believe they have proper end-of-string
> detection, therefore better performance and hence the better choice than
> HP.
> Is that a correct conclusion?
>
> It seems like there are a number of different models available from NI.
> Anything in particular to prefer?
>
> Thanks,
> -Alex
>
> On Fri, Jan 10, 2020 at 04:02:07PM +0100, dave penkler wrote:
> > Hallo Alexander,
> > From a user perspective they are pretty much the same as they use the
> same
> > driver. The main difference is that the 82350A requires a firmware
> > udownload when initialising it. So the 82350B is preferable from that
> > point. See aslo
> >
> https://linux-gpib.sourceforge.io/doc_html/supported-hardware.html#AGILENT-82350B
> >
> > Regarding the non-system controller aspect: the cards can be used in this
> > mode but you need to understand the gpib protocol to program it.
> > A simple example is here:
> >
> https://sourceforge.net/p/linux-gpib/code/HEAD/tree/trunk/linux-gpib-user/examples/slave_read_to_file.c
> > cheers,
> > -Dave
> >
> > On Fri, 10 Jan 2020 at 13:41, Alexander Huemer <ale...@xx...>
> > wrote:
> >
> > > Hi
> > >
> > > I would like to build a small box based on a Soekris 5501 to be able to
> > > interface various pieces of old test equipment via GPIB.
> > >
> > > In case that matters, the test equipment I have with GPIB interfaces
> > > are:
> > > * HP 54200A (Oscilloscope)
> > > * HP 66311B (Power supply)
> > > * HP  3478A (Multimeter)
> > > * Rohde & Schwarz CMD53 (Digital Radiocommunication Tester)
> > >
> > > I am considering to buy either:
> > > * HP 82350A Rev. B
> > > * HP 82350B Rev. A
> > >
> > > My question is whether there are any real-world differences between
> > > these cards from user perspective.
> > > Looking at pictures of the boards, the implementations seems to be
> > > significantly different. Having no practical experience with linux-gpib
> > > yet, I cannot say whether those differences have any effect to the
> user.
> > >
> > > * HP 82350A Rev. B -> Xilinx XC5202 + PLX PCI9050
> > > * HP 82350B Rev. A -> Xilinx XC2S100, no PLX
> > >
> > > My guess would be 'no difference', though I thought I'd ask before I
> > > buy.
> > >
> > > Second question:
> > > Can these boards act as non-controllers on the bus? I wasn't able to
> > > find a good explanation of the technical situation in English, only in
> > > German[1] (my mother tongue).
> > > Long story short: Some GPIB adapters for general purpose computers can
> > > react to ATN messages on the bus quickly enough to be able to act as
> > > non-controllers, some aren't. The time budget is pretty tight for that,
> > > 200ns, too quickly for interrupt-based implementations.
> > >
> > > I believe the ATN responses are the reason one would want to use a PCI
> > > board instead of a 82357A/B.
> > > Whether that ATN thing is significantly relevant in another can of
> > > worms, though we don't have to open that can of worms right now.
> > >
> > > -Alex
> > >
> > > [1] https://www.mikrocontroller.net/articles/GPIB-RS232-Schnittstelle
> > >
> > >
> > > _______________________________________________
> > > Linux-gpib-general mailing list
> > > Lin...@li...
> > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
> > >
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Which Agilent GPIB PCI card to buy?

[Alexander H. <ale...@xx...>]

Hi

Thanks for the insights.
A friend of mine suggested to use National Instruments card instead of 
HP.
Taking a look at the supported-hardware page I don't see any notes for 
the NI PCI cards, which makes me believe they have proper end-of-string 
detection, therefore better performance and hence the better choice than 
HP.
Is that a correct conclusion?

It seems like there are a number of different models available from NI.  
Anything in particular to prefer?

Thanks,
-Alex

On Fri, Jan 10, 2020 at 04:02:07PM +0100, dave penkler wrote:
> Hallo Alexander,
> From a user perspective they are pretty much the same as they use the same
> driver. The main difference is that the 82350A requires a firmware
> udownload when initialising it. So the 82350B is preferable from that
> point. See aslo
> https://linux-gpib.sourceforge.io/doc_html/supported-hardware.html#AGILENT-82350B
> 
> Regarding the non-system controller aspect: the cards can be used in this
> mode but you need to understand the gpib protocol to program it.
> A simple example is here:
> https://sourceforge.net/p/linux-gpib/code/HEAD/tree/trunk/linux-gpib-user/examples/slave_read_to_file.c
> cheers,
> -Dave
> 
> On Fri, 10 Jan 2020 at 13:41, Alexander Huemer <ale...@xx...>
> wrote:
> 
> > Hi
> >
> > I would like to build a small box based on a Soekris 5501 to be able to
> > interface various pieces of old test equipment via GPIB.
> >
> > In case that matters, the test equipment I have with GPIB interfaces
> > are:
> > * HP 54200A (Oscilloscope)
> > * HP 66311B (Power supply)
> > * HP  3478A (Multimeter)
> > * Rohde & Schwarz CMD53 (Digital Radiocommunication Tester)
> >
> > I am considering to buy either:
> > * HP 82350A Rev. B
> > * HP 82350B Rev. A
> >
> > My question is whether there are any real-world differences between
> > these cards from user perspective.
> > Looking at pictures of the boards, the implementations seems to be
> > significantly different. Having no practical experience with linux-gpib
> > yet, I cannot say whether those differences have any effect to the user.
> >
> > * HP 82350A Rev. B -> Xilinx XC5202 + PLX PCI9050
> > * HP 82350B Rev. A -> Xilinx XC2S100, no PLX
> >
> > My guess would be 'no difference', though I thought I'd ask before I
> > buy.
> >
> > Second question:
> > Can these boards act as non-controllers on the bus? I wasn't able to
> > find a good explanation of the technical situation in English, only in
> > German[1] (my mother tongue).
> > Long story short: Some GPIB adapters for general purpose computers can
> > react to ATN messages on the bus quickly enough to be able to act as
> > non-controllers, some aren't. The time budget is pretty tight for that,
> > 200ns, too quickly for interrupt-based implementations.
> >
> > I believe the ATN responses are the reason one would want to use a PCI
> > board instead of a 82357A/B.
> > Whether that ATN thing is significantly relevant in another can of
> > worms, though we don't have to open that can of worms right now.
> >
> > -Alex
> >
> > [1] https://www.mikrocontroller.net/articles/GPIB-RS232-Schnittstelle
> >
> >
> > _______________________________________________
> > Linux-gpib-general mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
> >

Re: [Linux-gpib-general] Which Agilent GPIB PCI card to buy?

[dave p. <dpe...@gm...>]

Hallo Alexander,
>From a user perspective they are pretty much the same as they use the same
driver. The main difference is that the 82350A requires a firmware
udownload when initialising it. So the 82350B is preferable from that
point. See aslo
https://linux-gpib.sourceforge.io/doc_html/supported-hardware.html#AGILENT-82350B

Regarding the non-system controller aspect: the cards can be used in this
mode but you need to understand the gpib protocol to program it.
A simple example is here:
https://sourceforge.net/p/linux-gpib/code/HEAD/tree/trunk/linux-gpib-user/examples/slave_read_to_file.c
cheers,
-Dave

On Fri, 10 Jan 2020 at 13:41, Alexander Huemer <ale...@xx...>
wrote:

> Hi
>
> I would like to build a small box based on a Soekris 5501 to be able to
> interface various pieces of old test equipment via GPIB.
>
> In case that matters, the test equipment I have with GPIB interfaces
> are:
> * HP 54200A (Oscilloscope)
> * HP 66311B (Power supply)
> * HP  3478A (Multimeter)
> * Rohde & Schwarz CMD53 (Digital Radiocommunication Tester)
>
> I am considering to buy either:
> * HP 82350A Rev. B
> * HP 82350B Rev. A
>
> My question is whether there are any real-world differences between
> these cards from user perspective.
> Looking at pictures of the boards, the implementations seems to be
> significantly different. Having no practical experience with linux-gpib
> yet, I cannot say whether those differences have any effect to the user.
>
> * HP 82350A Rev. B -> Xilinx XC5202 + PLX PCI9050
> * HP 82350B Rev. A -> Xilinx XC2S100, no PLX
>
> My guess would be 'no difference', though I thought I'd ask before I
> buy.
>
> Second question:
> Can these boards act as non-controllers on the bus? I wasn't able to
> find a good explanation of the technical situation in English, only in
> German[1] (my mother tongue).
> Long story short: Some GPIB adapters for general purpose computers can
> react to ATN messages on the bus quickly enough to be able to act as
> non-controllers, some aren't. The time budget is pretty tight for that,
> 200ns, too quickly for interrupt-based implementations.
>
> I believe the ATN responses are the reason one would want to use a PCI
> board instead of a 82357A/B.
> Whether that ATN thing is significantly relevant in another can of
> worms, though we don't have to open that can of worms right now.
>
> -Alex
>
> [1] https://www.mikrocontroller.net/articles/GPIB-RS232-Schnittstelle
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] Which Agilent GPIB PCI card to buy?

[Alexander H. <ale...@xx...>]

Hi

I would like to build a small box based on a Soekris 5501 to be able to 
interface various pieces of old test equipment via GPIB.

In case that matters, the test equipment I have with GPIB interfaces 
are:
* HP 54200A (Oscilloscope)
* HP 66311B (Power supply)
* HP  3478A (Multimeter)
* Rohde & Schwarz CMD53 (Digital Radiocommunication Tester)

I am considering to buy either:
* HP 82350A Rev. B
* HP 82350B Rev. A

My question is whether there are any real-world differences between 
these cards from user perspective.
Looking at pictures of the boards, the implementations seems to be 
significantly different. Having no practical experience with linux-gpib 
yet, I cannot say whether those differences have any effect to the user.

* HP 82350A Rev. B -> Xilinx XC5202 + PLX PCI9050
* HP 82350B Rev. A -> Xilinx XC2S100, no PLX

My guess would be 'no difference', though I thought I'd ask before I 
buy.

Second question:
Can these boards act as non-controllers on the bus? I wasn't able to 
find a good explanation of the technical situation in English, only in 
German[1] (my mother tongue).
Long story short: Some GPIB adapters for general purpose computers can 
react to ATN messages on the bus quickly enough to be able to act as 
non-controllers, some aren't. The time budget is pretty tight for that, 
200ns, too quickly for interrupt-based implementations.

I believe the ATN responses are the reason one would want to use a PCI 
board instead of a 82357A/B.
Whether that ATN thing is significantly relevant in another can of 
worms, though we don't have to open that can of worms right now.

-Alex

[1] https://www.mikrocontroller.net/articles/GPIB-RS232-Schnittstelle

Re: [Linux-gpib-general] Help needed

[Adrian S. <ben...@gm...>]

Hi all,

I would like to thank Dave P. and Paul G. for their suggestions. I think we
all agree that all in all it is easier to read the data and plot it with
gnuplot or something else but I wanted to have the second option suggested
by Dave for the sake of completeness. Following Dave's suggestion I did the
following:

   - looked around through examples folder in linux-gpib-user-4.3.0 and
   found slave_read_to_file.c
   - configured the 70206A to plot on a listen only plotter
   - used the slave_read_to_file binary to capture the output to a file
   - issued plot command on the device

While that seemed to have worked and I managed to get valid PLT content,
this approach has some problems which I hope you can help me with:

   1. I cannot seem to reliably start the listener in order to capture the
   plotting content. I only managed once and I'm not sure as to what I did to
   make it work. Currently I start the same program (slave_read_to_file) and
   issue a PLOT command on the SA but nothing happens; the slave does not
   capture anything and the device remains in a blocked state.
   2. The slave_read_to_file uses ibrdf(). I looked into the source code
   and it seems that ibrdf() uses a buffer of 0x4000 bytes. This causes
   content to only be written to the file in 16KB chunks, so I get incomplete
   PLT content in the file whenever the plot size is not aligned to a 16KB
   boundary. One idea would be to be able to read one byte at a time and track
   the output and stop whenever the plot finishes.

How would you suggest I tackle these problems? I am a programmer by trade
so I'm not afraid to get my hands dirty with code. I'm mostly interested in
solving the 1st problem. Is there a way I can debug things? What is the
expected sequence of events in this particular setup?

Thank you very much,
Adrian

On Thu, Dec 19, 2019 at 7:27 PM dave penkler <dpe...@gm...> wrote:

> Generally it is easier to read the data and then use something like
> gnuplot to plot it. It is possible to plot to the card by sending the
> appropriate low level set talker and listener commands and then initiating
> the plot from the instrument while reading the plot output
> programmatically.
> cheers,
> -Dave
>
>
> On Thu, 19 Dec 2019, 18:01 Adrian Scripcă, <ben...@gm...> wrote:
>
>> Hello all,
>>
>> I am just getting started with linux-gpib and gpib in general and I would
>> require some guidance from more knowledgeable members.
>>
>> Context: I have some HP equipment (HP8656B and a 70000 series SA) which I
>> am trying to communicate with and an Agilent 82357B adapter bought from
>> eBay (most likely a clone but should do).
>>
>> I run a Ubuntu 19.10 distribution with 5.3.0-24-generic kernel so I
>> installed linux-gpib-4.3.0 first. Installation went painlessly. I finally
>> managed to connect to the equipment and issue commands, modifying and
>> querying the state.
>>
>> The next step however is to see whether I can obtain plot data from the
>> spectrum analyzer. So here goes my question: is there a way in which I can
>> emulate a listener with a given address on the GPIB bus and read data while
>> also being connected to the SA and issue commands to it?
>>
>> Sorry if my questions sound confusing but as I mentioned before this is
>> my first interaction with linux-gpib and gpib in general.
>>
>> Thank you,
>> Adrian
>>
>>
>>
>> _______________________________________________
>> Linux-gpib-general mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>>
>

Re: [Linux-gpib-general] Dave P - Send ma an e-mail

[cfo <xn...@lu...>]

On Thu, 19 Dec 2019 16:25:27 +0000, cfo wrote:

> Hi Dave
> 
Got your mail , and replied.
Don't think you got my reply , or it's in the spambox

Carsten

Re: [Linux-gpib-general] Help needed

[dave p. <dpe...@gm...>]

Generally it is easier to read the data and then use something like gnuplot
to plot it. It is possible to plot to the card by sending the appropriate
low level set talker and listener commands and then initiating the plot
from the instrument while reading the plot output programmatically.
cheers,
-Dave


On Thu, 19 Dec 2019, 18:01 Adrian Scripcă, <ben...@gm...> wrote:

> Hello all,
>
> I am just getting started with linux-gpib and gpib in general and I would
> require some guidance from more knowledgeable members.
>
> Context: I have some HP equipment (HP8656B and a 70000 series SA) which I
> am trying to communicate with and an Agilent 82357B adapter bought from
> eBay (most likely a clone but should do).
>
> I run a Ubuntu 19.10 distribution with 5.3.0-24-generic kernel so I
> installed linux-gpib-4.3.0 first. Installation went painlessly. I finally
> managed to connect to the equipment and issue commands, modifying and
> querying the state.
>
> The next step however is to see whether I can obtain plot data from the
> spectrum analyzer. So here goes my question: is there a way in which I can
> emulate a listener with a given address on the GPIB bus and read data while
> also being connected to the SA and issue commands to it?
>
> Sorry if my questions sound confusing but as I mentioned before this is my
> first interaction with linux-gpib and gpib in general.
>
> Thank you,
> Adrian
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] Dave P - Send ma an e-mail

[cfo <xn...@lu...>]

Hi Dave

A bit unorthodox , but i can't get through to you on your gmail 
(spambox ??)

Send me an e-mail - You have it ... 

Carsten
DK

[Linux-gpib-general] Help needed

[Adrian S. <ben...@gm...>]

Hello all,

I am just getting started with linux-gpib and gpib in general and I would
require some guidance from more knowledgeable members.

Context: I have some HP equipment (HP8656B and a 70000 series SA) which I
am trying to communicate with and an Agilent 82357B adapter bought from
eBay (most likely a clone but should do).

I run a Ubuntu 19.10 distribution with 5.3.0-24-generic kernel so I
installed linux-gpib-4.3.0 first. Installation went painlessly. I finally
managed to connect to the equipment and issue commands, modifying and
querying the state.

The next step however is to see whether I can obtain plot data from the
spectrum analyzer. So here goes my question: is there a way in which I can
emulate a listener with a given address on the GPIB bus and read data while
also being connected to the SA and issue commands to it?

Sorry if my questions sound confusing but as I mentioned before this is my
first interaction with linux-gpib and gpib in general.

Thank you,
Adrian