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

Re: [Linux-gpib-general] PCI-GPIB board with TNT5004 chip from NI

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

On Thu, Jun 6, 2019 at 11:12 AM W <dat...@gm...> wrote:
> I just got one of these boards. I had a quick look at the Supported Hardware Matrix and cannot find any kernel driver
> that would match the TNT5004 chip. I guess this board is just not supported, right?

You should try just adding your pci device id to the tnt4882 driver.
It will probably just work.  In the worst case, they have dropped some
backwards compatibility behavior from the tnt5004, and that will have
to be worked around.

[Linux-gpib-general] PCI-GPIB board with TNT5004 chip from NI

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

Hello

I just got one of these boards. I had a quick look at the Supported
Hardware Matrix and cannot find any kernel driver
that would match the TNT5004 chip. I guess this board is just not
supported, right?

And thanks for making this code available.

Walter

Re: [Linux-gpib-general] Errors with module ni_usb_gpib on CentOS 7.6

[Werner L. <wer...@ae...>]

Am 02.05.19 um 09:19 schrieb Werner Liffert:
> Am 30.04.19 um 17:27 schrieb Frank Mori Hess:
>> On Wed, Apr 24, 2019 at 9:06 AM Werner Liffert
>> <wer...@ae...> wrote:
>>> Hello
>>>
>>> I use for many years  GPIB-USB-HS cards from Ni without Problems.
>>> Last Installation: CentOS 7.5 (kernel 3.10.0-862.11.6.el7.x86_64),
>>> linux-gpib-3.2.21
>>>
>>>
>>> With the update from CentOS 7.5 to 7.6 (kernel
>>> 3.10.0-957.10.1.el7.x86_64) i receive the following error messages:
>>>
>> Try SVN or a newer release, 3.2.21 is from 2014.  Do the 4.x
>> linux-gpib releases not compile against your kernel?
>>
> Hi
>
> after eliminate  the fmh_gpibi (error: implicit declaration of 
> function ‘of_find_node_by_path’),
> the linux-gpib-4.2.0 do compile without error.
>
> May  1 14:59:28 mcp21 kernel: Linux-GPIB 4.2.0 Driver
> May  1 14:59:34 mcp21 kernel: ni_usb_gpib driver loading
> May  1 14:59:34 mcp21 kernel: ni_usb_gpib: probe succeeded for path: 
> usb-0000:00:1a.0-1.4
> May  1 14:59:34 mcp21 kernel: usbcore: registered new interface driver 
> ni_usb_gpib
> May  1 14:59:34 mcp21 kernel: gpib: registered ni_usb_b interface
> May  1 14:59:50 mcp21 kernel: ni_usb_gpib: attach
> May  1 14:59:50 mcp21 kernel: #011attached to bus interface 0, address 
> 0xffff8daf0ae46000
> May  1 14:59:50 mcp21 kernel: #011product id=0x709b
> May  1 14:59:50 mcp21 kernel: ni_usb_hs_wait_for_ready: board serial 
> number is 0x13cc599
> May  1 14:59:50 mcp21 kernel: 
> /usr/share/linux-gpib-4.2.0/linux-gpib-kernel-4.2.0/drivers/gpib/ni_usb/ni_usb_gpib.c: 
> ni_usb_hs_wait_for_ready exit retval=0
>
>
> Now i receive on the first ibwrt-command an error:
>
> returnvalue=8100  iberr=0  errno=25
>
> Any idea?
>
> Kind regards
>
> Werner
>
>
>
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
Hi

Sorry was my mistake. The old user-library was linked. Now it works

Thanks for help

Kind regards

Werner

Re: [Linux-gpib-general] Errors with module ni_usb_gpib on CentOS 7.6

[Werner L. <wer...@ae...>]

Am 30.04.19 um 17:27 schrieb Frank Mori Hess:
> On Wed, Apr 24, 2019 at 9:06 AM Werner Liffert
> <wer...@ae...> wrote:
>> Hello
>>
>> I use for many years  GPIB-USB-HS cards from Ni without Problems.
>> Last Installation: CentOS 7.5 (kernel 3.10.0-862.11.6.el7.x86_64),
>> linux-gpib-3.2.21
>>
>>
>> With the update from CentOS 7.5 to 7.6 (kernel
>> 3.10.0-957.10.1.el7.x86_64) i receive the following error messages:
>>
> Try SVN or a newer release, 3.2.21 is from 2014.  Do the 4.x
> linux-gpib releases not compile against your kernel?
>
Hi

after eliminate  the fmh_gpibi (error: implicit declaration of function 
‘of_find_node_by_path’),
the linux-gpib-4.2.0 do compile without error.

May  1 14:59:28 mcp21 kernel: Linux-GPIB 4.2.0 Driver
May  1 14:59:34 mcp21 kernel: ni_usb_gpib driver loading
May  1 14:59:34 mcp21 kernel: ni_usb_gpib: probe succeeded for path: 
usb-0000:00:1a.0-1.4
May  1 14:59:34 mcp21 kernel: usbcore: registered new interface driver 
ni_usb_gpib
May  1 14:59:34 mcp21 kernel: gpib: registered ni_usb_b interface
May  1 14:59:50 mcp21 kernel: ni_usb_gpib: attach
May  1 14:59:50 mcp21 kernel: #011attached to bus interface 0, address 
0xffff8daf0ae46000
May  1 14:59:50 mcp21 kernel: #011product id=0x709b
May  1 14:59:50 mcp21 kernel: ni_usb_hs_wait_for_ready: board serial 
number is 0x13cc599
May  1 14:59:50 mcp21 kernel: 
/usr/share/linux-gpib-4.2.0/linux-gpib-kernel-4.2.0/drivers/gpib/ni_usb/ni_usb_gpib.c: 
ni_usb_hs_wait_for_ready exit retval=0


Now i receive on the first ibwrt-command an error:

returnvalue=8100  iberr=0  errno=25

Any idea?

Kind regards

Werner

Re: [Linux-gpib-general] Errors with module ni_usb_gpib on CentOS 7.6

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

On Wed, Apr 24, 2019 at 9:06 AM Werner Liffert
<wer...@ae...> wrote:
>
> Hello
>
> I use for many years  GPIB-USB-HS cards from Ni without Problems.
> Last Installation: CentOS 7.5 (kernel 3.10.0-862.11.6.el7.x86_64),
> linux-gpib-3.2.21
>
>
> With the update from CentOS 7.5 to 7.6 (kernel
> 3.10.0-957.10.1.el7.x86_64) i receive the following error messages:
>

Try SVN or a newer release, 3.2.21 is from 2014.  Do the 4.x
linux-gpib releases not compile against your kernel?

Re: [Linux-gpib-general] Cannot make linux-gpib-kernel-4.2.0

[Werner K. <wer...@on...>]

Hi Julien,

I received a mail with a hint that fixed my problem. Now I don't know if I can find that mail 
again. I was told that this looks like a particular OpenSuse problem. Here is my query first:  

*******************************************************************
Hi,
 
I followed the installation description in the linux-gpib-kernel-4.2.0 directory until the 
make-command. In the output I get
 
echo >&2;                                                       \ 
echo >&2 "  ERROR: Kernel configuration is invalid.";           \ 
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\ 
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \ 
echo >&2 ;                                                      \ 
/bin/false)

and 
 
/home/werner/GPIB/linux-gpib-4.2.0/linux-gpib-kernel-4.2.0/drivers/gpib/lpvo_usb_gpib/
lpvo_usb_gpib.c:621:13: err
or: unknown type name ‘wait_queue_t’; did you mean ‘wait_event’? 
#define WQT wait_queue_t 
            ^
 
I ran "make oldconfig && make prepare" without error, but the errors above remained. I 
looked for the type-description ‘wait_queue_t’ but didn't find anything apart a remark in a 
log-file that didn't help me  ( "include /sys/sysmacros.h for minor() definiton" )
 
My system:  OpenSuse Leap 15.0,  x86_64, 
kernel  4.12.14-lp150.12.48-default
 
Now I don't know how fix that problem. I am not a big expert in Linux.
Do you have any idea, any hint
 
Best regards
Werner
*******************************************************************
Oh yes, Julien,

now I found a note concerning that problem. I simply copy the important part of the note:

*******************************************************************
Hallo Werner,
The first message is not an error message, it is in fact
the echo of the build script commands.
The second is an error which might be specific to Suse.
To fix this please change line 620 in 
drivers/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
from 
*#if LINUX_VERSION_CODE < KERNEL_VERSION(4,13,0)*
to
*#if LINUX_VERSION_CODE < KERNEL_VERSION(4,12,14)*
mfG,
-Dave
*******************************************************************
Best regards
Werner




Am Donnerstag, 25. April 2019, 18:49:05 CEST schrieb Julien Salort:
> Hello Werner,
> 
> > */home/werner/GPIB/linux-gpib-4.2.0/linux-gpib-kernel-4.2.0/drivers/gpib/l
> > pvo_usb_gpib/ lpvo_usb_gpib.c:621:13:* *err*
> > unknown type name ‘*wait_queue_t*’; did you mean ‘*wait_event*’?
> > *w*ait_queue_t
> > *^*
> 
> [snip]
> 
> > My system:  OpenSuse Leap 15.0,  x86_64, kernel 
> > 4.12.14-lp150.12.48-default
> I had exactely the same problem on my system, also using OpenSuSE Leap 15.
> 
> I figured out that the problem is this line:
> 
> #if LINUX_VERSION_CODE < KERNEL_VERSION(4,13,0)
> 
> in drivers/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c (line 621)
> 
> Changing it to
> 
> #if LINUX_VERSION_CODE < KERNEL_VERSION(4,12,0)
> 
> fixed it for me.
> 
> I am not sure how the ticketing system works for linux-gpib to submit a
> patch if it hasn't been done yet, I came across your message when
> searching for the problem for myself.
> 
> 
> Bests,
> 
> 
> Julien

[Linux-gpib-general] Cannot make linux-gpib-kernel-4.2.0

[Julien S. <li...@sa...>]

Hello Werner,

> */home/werner/GPIB/linux-gpib-4.2.0/linux-gpib-kernel-4.2.0/drivers/gpib/lpvo_usb_gpib/
> lpvo_usb_gpib.c:621:13:* *err*
> unknown type name ‘*wait_queue_t*’; did you mean ‘*wait_event*’?
> *w*ait_queue_t
> *^*
[snip]
> My system:  OpenSuse Leap 15.0,  x86_64, kernel  4.12.14-lp150.12.48-default

I had exactely the same problem on my system, also using OpenSuSE Leap 15.

I figured out that the problem is this line:

#if LINUX_VERSION_CODE < KERNEL_VERSION(4,13,0)

in drivers/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c (line 621)

Changing it to

#if LINUX_VERSION_CODE < KERNEL_VERSION(4,12,0)

fixed it for me.

I am not sure how the ticketing system works for linux-gpib to submit a 
patch if it hasn't been done yet, I came across your message when 
searching for the problem for myself.


Bests,


Julien

[Linux-gpib-general] Errors with module ni_usb_gpib on CentOS 7.6

[Werner L. <wer...@ae...>]

Hello

I use for many years  GPIB-USB-HS cards from Ni without Problems.
Last Installation: CentOS 7.5 (kernel 3.10.0-862.11.6.el7.x86_64), 
linux-gpib-3.2.21


With the update from CentOS 7.5 to 7.6 (kernel 
3.10.0-957.10.1.el7.x86_64) i receive the following error messages:

Apr 16 11:41:09 mcp21 kernel: gpib_common: loading out-of-tree module 
taints kernel.
Apr 16 11:41:09 mcp21 kernel: gpib_common: module verification failed: 
signature and/or required key missing - tainting kernel
Apr 16 11:41:09 mcp21 kernel: Linux-GPIB 3.2.21 Driver
Apr 16 11:41:09 mcp21 kernel: ni_usb_gpib driver loading
Apr 16 11:41:09 mcp21 kernel: usbcore: registered new interface driver 
ni_usb_gpib
Apr 16 11:41:09 mcp21 kernel: gpib: registered ni_usb_b interface
...
...
...
Apr 16 11:41:09 mcp21 systemd: Starting start the gpib_conf script...
Apr 16 11:41:09 mcp21 gpib_config: failed to bring board online
Apr 16 11:41:09 mcp21 gpib_config: failed to configure board
Apr 16 11:41:09 mcp21 gpib_config: main: No such device
Apr 16 11:41:09 mcp21 kernel: ni_usb_gpib: attach
Apr 16 11:41:09 mcp21 kernel: No supported NI usb gpib adapters found, 
have you loaded its firmware?
Apr 16 11:41:09 mcp21 kernel: gpib: interface attach failed
Apr 16 11:41:09 mcp21 systemd: Started start the gpib_conf script.
...
...
...
Apr 16 13:31:50 mcp21 kernel: usb 1-1.4: new high-speed USB device 
number 4 using ehci-pci
Apr 16 13:31:50 mcp21 kernel: usb 1-1.4: New USB device found, 
idVendor=3923, idProduct=709b
Apr 16 13:31:50 mcp21 kernel: usb 1-1.4: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Apr 16 13:31:50 mcp21 kernel: usb 1-1.4: Product: GPIB-USB-HS
Apr 16 13:31:50 mcp21 kernel: usb 1-1.4: Manufacturer: National Instruments
Apr 16 13:31:50 mcp21 kernel: usb 1-1.4: SerialNumber: 013CC599
Apr 16 13:31:50 mcp21 kernel: ni_usb_gpib: probe succeeded for path: 
usb-0000:00:1a.0-1.4
Apr 16 13:31:50 mcp21 mtp-probe: checking bus 1, device 4: 
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Apr 16 13:31:50 mcp21 mtp-probe: bus: 1, device: 4 was not an MTP device
Apr 16 13:31:50 mcp21 kernel: ni_usb_gpib: attach
Apr 16 13:31:50 mcp21 kernel: #011attached to bus interface 0, address 
0xffff8dab932b9400
Apr 16 13:31:50 mcp21 kernel: #011product id=0x709b
Apr 16 13:31:50 mcp21 kernel: ------------[ cut here ]------------
Apr 16 13:31:50 mcp21 kernel: WARNING: CPU: 0 PID: 3315 at 
drivers/usb/core/hcd.c:1587 usb_hcd_map_urb_for_dma+0x51c/0x780
Apr 16 13:31:50 mcp21 kernel: transfer buffer is on stack
Apr 16 13:31:50 mcp21 kernel: Modules linked in: ni_usb_gpib(OE) 
gpib_common(OE) fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 
tun devlink rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd 
grace fscache ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT 
nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute 
bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 
ip6table_mangle ip6table_security ip6table_raw iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_security iptable_raw ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter sunrpc dm_mirror 
dm_region_hash dm_log dm_mod iTCO_wdt iTCO_vendor_support ppdev 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
intel_powerclamp coretemp
Apr 16 13:31:50 mcp21 kernel: intel_rapl kvm_intel kvm irqbypass 
crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper 
ablk_helper cryptd pcspkr sg lpc_ich i2c_i801 snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm 
parport_pc parport nuvoton_cir rc_core snd_timer snd mei_me mei 
soundcore ie31200_edac sch_fq_codel binfmt_misc ip_tables ext4 mbcache 
jbd2 sd_mod crc_t10dif crct10dif_generic i915 serio_raw crct10dif_pclmul 
crct10dif_common crc32c_intel ahci libahci libata i2c_algo_bit iosf_mbi 
drm_kms_helper video syscopyarea sysfillrect sysimgblt fb_sys_fops 
e1000e drm ptp pps_core drm_panel_orientation_quirks
Apr 16 13:31:50 mcp21 kernel: CPU: 0 PID: 3315 Comm: gpib_config Kdump: 
loaded Tainted: G           OE  ------------ 3.10.0-957.10.1.el7.x86_64 #1
Apr 16 13:31:50 mcp21 kernel: Hardware name: transtec AG  /DH77KC, BIOS 
KCH7710H.86A.0106.2012.1227.1251 12/27/2012
Apr 16 13:31:50 mcp21 kernel: Call Trace:
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf962e41>] dump_stack+0x19/0x1b
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf297688>] __warn+0xd8/0x100
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf29770f>] 
warn_slowpath_fmt+0x5f/0x80
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf5a149c>] ? map_single+0x2c/0x30
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf5a1666>] ? 
swiotlb_map_page+0x66/0x150
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf6fc58c>] 
usb_hcd_map_urb_for_dma+0x51c/0x780
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf6fd2cd>] 
usb_hcd_submit_urb+0x1fd/0xc00
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf583466>] ? sprintf+0x56/0x80
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf6fef47>] 
usb_submit_urb+0x297/0x580
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf29813a>] ? 
msg_print_text+0xea/0x1d0
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf6ff9ce>] 
usb_start_wait_urb+0x6e/0x180
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf299cb2>] ? wake_up_klogd+0x32/0x40
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf6ffbbc>] 
usb_control_msg+0xdc/0x130
Apr 16 13:31:50 mcp21 kernel: [<ffffffffc0d33dec>] 
ni_usb_receive_control_msg+0x8c/0xc0 [ni_usb_gpib]
Apr 16 13:31:50 mcp21 kernel: [<ffffffffc0d367f3>] 
ni_usb_attach+0x2e3/0xea0 [ni_usb_gpib]
Apr 16 13:31:50 mcp21 kernel: [<ffffffffc0d4a39e>] ? 
board_type_ioctl+0x1de/0x250 [gpib_common]
Apr 16 13:31:50 mcp21 kernel: [<ffffffffc0d4cf1d>] ibonline+0x4d/0x110 
[gpib_common]
Apr 16 13:31:50 mcp21 kernel: [<ffffffffc0d4a976>] ibioctl+0x266/0x1830 
[gpib_common]
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf456880>] do_vfs_ioctl+0x3a0/0x5a0
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf45312d>] ? putname+0x3d/0x60
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf456b21>] SyS_ioctl+0xa1/0xc0
Apr 16 13:31:50 mcp21 kernel: [<ffffffffaf975ddb>] 
system_call_fastpath+0x22/0x27
Apr 16 13:31:50 mcp21 kernel: ---[ end trace a634841b9f2bf70c ]---
Apr 16 13:31:50 mcp21 kernel: 
/usr/share/linux-gpib-3.2.21/drivers/gpib/ni_usb/ni_usb_gpib.c: 
usb_control_msg request 0x41 returned -11
Apr 16 13:31:50 mcp21 kernel: 
/usr/share/linux-gpib-3.2.21/drivers/gpib/ni_usb/ni_usb_gpib.c: 
usb_control_msg returned -32
Apr 16 13:31:51 mcp21 sh: abrt-dump-oops: Found oopses: 1
Apr 16 13:31:51 mcp21 sh: abrt-dump-oops: Creating problem directories
Apr 16 13:31:51 mcp21 sh: abrt-dump-oops: Not going to make dump 
directories world readable because PrivateReports is on
Apr 16 13:31:51 mcp21 kernel: ni_usb_nonblocking_receive_bulk_msg: 
killed urb due to timeout
Apr 16 13:31:51 mcp21 kernel: 
/usr/share/linux-gpib-3.2.21/drivers/gpib/ni_usb/ni_usb_gpib.c: 
ni_usb_write_registers: ni_usb_receive_bulk_msg returned -110, bytes_read=0
Apr 16 13:31:51 mcp21 kernel: ni_usb_dump_raw_block:
Apr 16 13:31:51 mcp21 kernel: 
/usr/share/linux-gpib-3.2.21/drivers/gpib/ni_usb/ni_usb_gpib.c: 
ni_usb_shutdown_hardware: register write failed, retval=-110
Apr 16 13:31:51 mcp21 kernel: gpib: interface attach failed
Apr 16 13:31:52 mcp21 abrt-server: Looking for kernel package
Apr 16 13:31:52 mcp21 abrt-dump-oops: Reported 1 kernel oopses to Abrt
Apr 16 13:31:54 mcp21 abrt-server: Kernel package 
kernel-3.10.0-957.10.1.el7.x86_64 found


Has anyone an idea? Thanks in advance

Kind regards

Werner Liffert

[Linux-gpib-general] install_mod_path was accidentally removed in 1774

[Derek K. <der...@gm...>]

Hello,

Attached is a patch to restore the INSTALL_MOD_PATH argument to
modules_install in the kernel modules Makefile. It looks like this
argument was accidentally removed during the rework in r1774. This
argument is needed to be able to build a Debian package.

Regards,
Derek

Re: [Linux-gpib-general] GPIB module and updated kernel

[Charles L. <la...@du...>]

That's why it's useful to have modules handled with
dkms; when the kernel is updated, the modules are
automatically rebuilt. 

dkms-linux-gpib-4.2.0-2.20190107svn1809.fc29.noarch 

is the Fedora 29 module that sets this up. Look for
something similar for Ubuntu. 

On Tue, 2 Apr 2019 20:19:09 -0300
Anderson Minozzo Begossi <amb...@uc...> wrote:

> Hello,
> I successfully installed the gpib linux driver in my ubuntu
> 4.15.0-46-generic kernel and it worked perfectly.
> However, recently my operating system updated and with it the kernel
> changed to 4.15.0-47-generic, and with that I can no longer use the
> driver that was installed in the old kernel.
> 
> Is there any way to solve this, without installing linux-gpib driver
> every time the kernel updates?
> 
> I appreciate any help.
> 



-- 
 Drexel University    \V               --Chuck Lane
======]---------->-----*------<--------[===========
     (215) 895-1545   / \_/*~~~~~  Particle Physics
FAX: (215) 895-1281  la...@du...

[Linux-gpib-general] GPIB module and updated kernel

[Anderson M. B. <amb...@uc...>]

Hello,
I successfully installed the gpib linux driver in my ubuntu
4.15.0-46-generic kernel and it worked perfectly.
However, recently my operating system updated and with it the kernel
changed to 4.15.0-47-generic, and with that I can no longer use the driver
that was installed in the old kernel.

Is there any way to solve this, without installing linux-gpib driver every
time the kernel updates?

I appreciate any help.

-- 
Enviado via UCSMail.

Re: [Linux-gpib-general] Broken GPIB

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

On the not working run, the udev scripts don't seem to be running
gpib_config.  We fixed some problems with the udev stuff in svn, which i
don't think has made it into a release.  So you could try that.  The old
udev scripts wouldn't work unless the kernel modules were already loaded
when they run.  I'd remove any existing linux gpib files from /etc/udev.d
then configure the userspace svn code with --sysconfdir=/etc and install
that.

On Wed, Mar 13, 2019, 13:31 Bishop, Mark (STRT) via Linux-gpib-general <
lin...@li...> wrote:

> I had this working a few weeks ago and now it isn’t.  Does this make any
> sense to anyone?
>
>
>
> I have a NI USB dongle attached to my system and this is what I am getting:
>
> (Not working)
>
> Feb 20 08:13:31 stride kernel: [2390014.354592] usb 1-4.1: new high-speed
> USB device number 64 using xhci_hcd
>
> Mar 13 12:55:19 stride kernel: [10756.520854] usb 1-2: new high-speed USB
> device number 15 using xhci_hcd
>
> Mar 13 12:55:19 stride kernel: [10756.875157] usb 1-2: New USB device
> found, idVendor=3923, idProduct=709b
>
> Mar 13 12:55:19 stride kernel: [10756.875158] usb 1-2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
>
> Mar 13 12:55:19 stride kernel: [10756.875159] usb 1-2: Product: GPIB-USB-HS
>
> Mar 13 12:55:19 stride kernel: [10756.875160] usb 1-2: Manufacturer:
> National Instruments
>
> Mar 13 12:55:19 stride kernel: [10756.875161] usb 1-2: SerialNumber:
> 01C300DD
>
> Mar 13 12:55:19 stride kernel: [10756.999293] ni_usb_gpib: probe succeeded
> for path: usb-0000:03:00.0-2
>
> Mar 13 12:55:19 stride mtp-probe: checking bus 1, device 15:
> "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-2"
>
> Mar 13 12:55:19 stride mtp-probe: bus: 1, device: 15 was not an MTP device
>
> Mar 13 12:55:34 stride kernel: [10592.110439] gpib: no gpib board
> configured on /dev/gpib0
>
>
>
> (Working)
>
> Feb 20 08:13:31 stride kernel: [2390014.354592] usb 1-4.1: new high-speed
> USB device number 64 using xhci_hcd
>
> Feb 20 08:13:31 stride kernel: [2390014.601458] usb 1-4.1: New USB device
> found, idVendor=3923, idProduct=709b
>
> Feb 20 08:13:31 stride kernel: [2390014.601460] usb 1-4.1: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
>
> Feb 20 08:13:31 stride kernel: [2390014.601461] usb 1-4.1: Product:
> GPIB-USB-HS
>
> Feb 20 08:13:31 stride kernel: [2390014.601462] usb 1-4.1: Manufacturer:
> National Instruments
>
> Feb 20 08:13:31 stride kernel: [2390014.601462] usb 1-4.1: SerialNumber:
> 012E5518
>
> Feb 20 08:13:31 stride kernel: [2390014.642890] ni_usb_gpib: probe
> succeeded for path: usb-0000:03:00.0-4.1
>
> Feb 20 08:13:35 stride mtp-probe: checking bus 1, device 64:
> "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-4/1-4.1"
>
> Feb 20 08:13:35 stride mtp-probe: checking bus 1, device 63:
> "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-2"
>
> Feb 20 08:13:35 stride mtp-probe: bus: 1, device: 64 was not an MTP device
>
> Feb 20 08:13:35 stride mtp-probe: bus: 1, device: 63 was not an MTP device
>
> Feb 20 08:13:36 stride /usr/local/etc/hotplug/usb/ni_usb_gpib: entered for
> Product: 3923/709b/101 Device: /dev/bus/usb/001/064 Serial: 012E5518
> Devpath: /devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-4/1-4.1
>
> Feb 20 08:13:36 stride kernel: [2390019.560601] gpib0: exiting autospoll
> thread
>
> Feb 20 08:13:36 stride kernel: [2390019.560734] ni_usb_gpib: attach
>
> Feb 20 08:13:36 stride kernel: [2390019.560737]         attached to bus
> interface 0, address 0xffff8d1690428000
>
> Feb 20 08:13:36 stride kernel: [2390019.650587]         product id=0x709b
>
> Feb 20 08:13:36 stride kernel: [2390019.651699] ni_usb_hs_wait_for_ready:
> board serial number is 0x12e5518
>
> Feb 20 08:13:36 stride kernel: [2390019.651905]
> /home/mark/svn_repos/linux-gpib-code/linux-gpib-kernel/drivers/gpib/ni_usb/ni_usb_gpib.c:
> ni_usb_hs_wait_for_ready exit retval=0
>
>
>
> *Mark Bishop*
>
> *Sr. Firmware/Software Engineer – Microwave Subsystems*
>
>
>
> [image: cid:image001.png@01D281ED.A45F0A90]
>
> 4726 Eisenhower Blvd.
>
> Tampa, FL 33634
>
> USA
>
>
>
> T  +1 813 901 7293
>
> *mb...@sm... <mb...@sm...>*
>
> *smithsinterconnect.com* <http://www.smithsinterconnect.com/>
>
> *TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!*
>
>
>
>
>
> This e-mail contains proprietary information some or all of which may be
> legally privileged. It is intended for the recipient only. If an addressing
> or transmission error has misdirected this e-mail, please notify the
> authority by replying to this e-mail. If you are not the intended recipient
> you must not use, disclose, distribute, copy, print, or rely on this
> e-mail. In addition, information contained in or attached to this e-mail
> may be subject to either 22 C.F.R. Parts 120?130, or 15 C.F.R. Parts
> 730-774. These regulations prohibit the release or disclosure of certain
> information contained herein to anyone who is not a U.S. citizen or
> permanent resident alien, without a license first having been issued.
> Failure to observe such requirements is a violation of U.S. law that
> carries serious penalties.   ­­
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Broken GPIB

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

Hi Mark,
It looks like you have two different adaptors, serial numbers 012E5518
(worked) and 01C300DD (failed). Perhaps try it again with the first one by
itself to see whether that makes any difference.
cheers,
/d

On Wed, Mar 13, 2019 at 6:31 PM Bishop, Mark (STRT) via Linux-gpib-general <
lin...@li...> wrote:

> I had this working a few weeks ago and now it isn’t.  Does this make any
> sense to anyone?
>
>
>
> I have a NI USB dongle attached to my system and this is what I am getting:
>
> (Not working)
>
> Feb 20 08:13:31 stride kernel: [2390014.354592] usb 1-4.1: new high-speed
> USB device number 64 using xhci_hcd
>
> Mar 13 12:55:19 stride kernel: [10756.520854] usb 1-2: new high-speed USB
> device number 15 using xhci_hcd
>
> Mar 13 12:55:19 stride kernel: [10756.875157] usb 1-2: New USB device
> found, idVendor=3923, idProduct=709b
>
> Mar 13 12:55:19 stride kernel: [10756.875158] usb 1-2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
>
> Mar 13 12:55:19 stride kernel: [10756.875159] usb 1-2: Product: GPIB-USB-HS
>
> Mar 13 12:55:19 stride kernel: [10756.875160] usb 1-2: Manufacturer:
> National Instruments
>
> Mar 13 12:55:19 stride kernel: [10756.875161] usb 1-2: SerialNumber:
> 01C300DD
>
> Mar 13 12:55:19 stride kernel: [10756.999293] ni_usb_gpib: probe succeeded
> for path: usb-0000:03:00.0-2
>
> Mar 13 12:55:19 stride mtp-probe: checking bus 1, device 15:
> "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-2"
>
> Mar 13 12:55:19 stride mtp-probe: bus: 1, device: 15 was not an MTP device
>
> Mar 13 12:55:34 stride kernel: [10592.110439] gpib: no gpib board
> configured on /dev/gpib0
>
>
>
> (Working)
>
> Feb 20 08:13:31 stride kernel: [2390014.354592] usb 1-4.1: new high-speed
> USB device number 64 using xhci_hcd
>
> Feb 20 08:13:31 stride kernel: [2390014.601458] usb 1-4.1: New USB device
> found, idVendor=3923, idProduct=709b
>
> Feb 20 08:13:31 stride kernel: [2390014.601460] usb 1-4.1: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
>
> Feb 20 08:13:31 stride kernel: [2390014.601461] usb 1-4.1: Product:
> GPIB-USB-HS
>
> Feb 20 08:13:31 stride kernel: [2390014.601462] usb 1-4.1: Manufacturer:
> National Instruments
>
> Feb 20 08:13:31 stride kernel: [2390014.601462] usb 1-4.1: SerialNumber:
> 012E5518
>
> Feb 20 08:13:31 stride kernel: [2390014.642890] ni_usb_gpib: probe
> succeeded for path: usb-0000:03:00.0-4.1
>
> Feb 20 08:13:35 stride mtp-probe: checking bus 1, device 64:
> "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-4/1-4.1"
>
> Feb 20 08:13:35 stride mtp-probe: checking bus 1, device 63:
> "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-2"
>
> Feb 20 08:13:35 stride mtp-probe: bus: 1, device: 64 was not an MTP device
>
> Feb 20 08:13:35 stride mtp-probe: bus: 1, device: 63 was not an MTP device
>
> Feb 20 08:13:36 stride /usr/local/etc/hotplug/usb/ni_usb_gpib: entered for
> Product: 3923/709b/101 Device: /dev/bus/usb/001/064 Serial: 012E5518
> Devpath: /devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-4/1-4.1
>
> Feb 20 08:13:36 stride kernel: [2390019.560601] gpib0: exiting autospoll
> thread
>
> Feb 20 08:13:36 stride kernel: [2390019.560734] ni_usb_gpib: attach
>
> Feb 20 08:13:36 stride kernel: [2390019.560737]         attached to bus
> interface 0, address 0xffff8d1690428000
>
> Feb 20 08:13:36 stride kernel: [2390019.650587]         product id=0x709b
>
> Feb 20 08:13:36 stride kernel: [2390019.651699] ni_usb_hs_wait_for_ready:
> board serial number is 0x12e5518
>
> Feb 20 08:13:36 stride kernel: [2390019.651905]
> /home/mark/svn_repos/linux-gpib-code/linux-gpib-kernel/drivers/gpib/ni_usb/ni_usb_gpib.c:
> ni_usb_hs_wait_for_ready exit retval=0
>
>
>
> *Mark Bishop*
>
> *Sr. Firmware/Software Engineer – Microwave Subsystems*
>
>
>
> [image: cid:image001.png@01D281ED.A45F0A90]
>
> 4726 Eisenhower Blvd.
>
> Tampa, FL 33634
>
> USA
>
>
>
> T  +1 813 901 7293
>
> *mb...@sm... <mb...@sm...>*
>
> *smithsinterconnect.com* <http://www.smithsinterconnect.com/>
>
> *TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!*
>
>
>
>
>
> This e-mail contains proprietary information some or all of which may be
> legally privileged. It is intended for the recipient only. If an addressing
> or transmission error has misdirected this e-mail, please notify the
> authority by replying to this e-mail. If you are not the intended recipient
> you must not use, disclose, distribute, copy, print, or rely on this
> e-mail. In addition, information contained in or attached to this e-mail
> may be subject to either 22 C.F.R. Parts 120?130, or 15 C.F.R. Parts
> 730-774. These regulations prohibit the release or disclosure of certain
> information contained herein to anyone who is not a U.S. citizen or
> permanent resident alien, without a license first having been issued.
> Failure to observe such requirements is a violation of U.S. law that
> carries serious penalties.   ­­
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] Broken GPIB

[Bishop, M. (STRT) <MB...@sm...>]

I had this working a few weeks ago and now it isn't.  Does this make any sense to anyone?

I have a NI USB dongle attached to my system and this is what I am getting:
(Not working)
Feb 20 08:13:31 stride kernel: [2390014.354592] usb 1-4.1: new high-speed USB device number 64 using xhci_hcd
Mar 13 12:55:19 stride kernel: [10756.520854] usb 1-2: new high-speed USB device number 15 using xhci_hcd
Mar 13 12:55:19 stride kernel: [10756.875157] usb 1-2: New USB device found, idVendor=3923, idProduct=709b
Mar 13 12:55:19 stride kernel: [10756.875158] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 13 12:55:19 stride kernel: [10756.875159] usb 1-2: Product: GPIB-USB-HS
Mar 13 12:55:19 stride kernel: [10756.875160] usb 1-2: Manufacturer: National Instruments
Mar 13 12:55:19 stride kernel: [10756.875161] usb 1-2: SerialNumber: 01C300DD
Mar 13 12:55:19 stride kernel: [10756.999293] ni_usb_gpib: probe succeeded for path: usb-0000:03:00.0-2
Mar 13 12:55:19 stride mtp-probe: checking bus 1, device 15: "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-2"
Mar 13 12:55:19 stride mtp-probe: bus: 1, device: 15 was not an MTP device
Mar 13 12:55:34 stride kernel: [10592.110439] gpib: no gpib board configured on /dev/gpib0

(Working)
Feb 20 08:13:31 stride kernel: [2390014.354592] usb 1-4.1: new high-speed USB device number 64 using xhci_hcd
Feb 20 08:13:31 stride kernel: [2390014.601458] usb 1-4.1: New USB device found, idVendor=3923, idProduct=709b
Feb 20 08:13:31 stride kernel: [2390014.601460] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 20 08:13:31 stride kernel: [2390014.601461] usb 1-4.1: Product: GPIB-USB-HS
Feb 20 08:13:31 stride kernel: [2390014.601462] usb 1-4.1: Manufacturer: National Instruments
Feb 20 08:13:31 stride kernel: [2390014.601462] usb 1-4.1: SerialNumber: 012E5518
Feb 20 08:13:31 stride kernel: [2390014.642890] ni_usb_gpib: probe succeeded for path: usb-0000:03:00.0-4.1
Feb 20 08:13:35 stride mtp-probe: checking bus 1, device 64: "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-4/1-4.1"
Feb 20 08:13:35 stride mtp-probe: checking bus 1, device 63: "/sys/devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-2"
Feb 20 08:13:35 stride mtp-probe: bus: 1, device: 64 was not an MTP device
Feb 20 08:13:35 stride mtp-probe: bus: 1, device: 63 was not an MTP device
Feb 20 08:13:36 stride /usr/local/etc/hotplug/usb/ni_usb_gpib: entered for Product: 3923/709b/101 Device: /dev/bus/usb/001/064 Serial: 012E5518 Devpath: /devices/pci0000:00/0000:00:15.0/0000:03:00.0/usb1/1-4/1-4.1
Feb 20 08:13:36 stride kernel: [2390019.560601] gpib0: exiting autospoll thread
Feb 20 08:13:36 stride kernel: [2390019.560734] ni_usb_gpib: attach
Feb 20 08:13:36 stride kernel: [2390019.560737]         attached to bus interface 0, address 0xffff8d1690428000
Feb 20 08:13:36 stride kernel: [2390019.650587]         product id=0x709b
Feb 20 08:13:36 stride kernel: [2390019.651699] ni_usb_hs_wait_for_ready: board serial number is 0x12e5518
Feb 20 08:13:36 stride kernel: [2390019.651905] /home/mark/svn_repos/linux-gpib-code/linux-gpib-kernel/drivers/gpib/ni_usb/ni_usb_gpib.c: ni_usb_hs_wait_for_ready exit retval=0

Mark Bishop
Sr. Firmware/Software Engineer - Microwave Subsystems

[cid:image001.png@01D281ED.A45F0A90]

4726 Eisenhower Blvd.
Tampa, FL 33634
USA


T  +1 813 901 7293

mb...@sm...<mailto:mb...@sm...>

smithsinterconnect.com<http://www.smithsinterconnect.com/>

TRAK MICROWAVE IS NOW SMITHS INTERCONNECT!

Re: [Linux-gpib-general] Python 3.7.1 import Gpib

[Tomislav I. <tom...@gm...>]

Hi Anderson,

Anaconda environments are separate from the system python installation and
do not share their libraries or packages with it. You need to install the
linux-gpib python bindings into the specific anaconda environment.

Here are the steps that I use myself.

Get the linux-gpib source tree.
In a terminal, activate your anaconda python 3.7.1 environment.
Change the active directory to linux-gpib-user/language/python directory.
Install the python bindings by running: $ python setup.py install

That should be it. Let me know if you have any questions.

Best,
Tomislav


On Wed, Mar 13, 2019 at 1:12 PM Anderson Minozzo Begossi <amb...@uc...>
wrote:

> Hello,
> I successfully installed the linux-gpib package, and when I run the import
> Gpib command on python 2.7 everything happens perfectly. But now I'm trying
> to import the package with python 3.7.1, installed with anaconda, and
> import is returning me the following error:
>
> Python 3.7.1 (default, Dec 14 2018, 19:28:38)
> [GCC 7.3.0] :: Anaconda, Inc. on linux
> Type "help", "copyright", "credits" or "license" for more information.
>
> import Gpib
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ModuleNotFoundError: No module named 'Gpib'
>
> I appreciate if someone helps me.
>
> Enviado via UCSMail.
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Perl rpm "provides"

[Colin S. <col...@gm...>]

Thanks Charles. I think that is on the rpm on my GitHub repo for rpm packaging
for linux-gpib.  I can apply this patch over there.

Thanks!
Colin

--
Colin Samples


On Wed, Mar 13, 2019 at 10:00 AM Charles Lane
<la...@du...> wrote:
>
> The default current build of perl-LinuxGpib
> gives  Provides:
> perl-LinuxGpib = 4.2.0-2.20190107svn1809.fc29
> perl-LinuxGpib(x86-64) = 4.2.0-2.20190107svn1809.fc29
>
> but standard Perl rpm provides for modules should be:
> perl(LinuxGpib)
>
> Attached (minor!) patch to linux-gpib.spec fixes this,
> by adding a BuildRequires for the perl subpackage.
> --
>  Drexel University    \V               --Chuck Lane
> ======]---------->-----*------<--------[===========
>      (215) 895-1545   / \_/*~~~~~  Particle Physics
> FAX: (215) 895-1281  la...@du...
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general

[Linux-gpib-general] Perl rpm "provides"

[Charles L. <la...@du...>]

The default current build of perl-LinuxGpib 
gives  Provides: 
perl-LinuxGpib = 4.2.0-2.20190107svn1809.fc29
perl-LinuxGpib(x86-64) = 4.2.0-2.20190107svn1809.fc29

but standard Perl rpm provides for modules should be:
perl(LinuxGpib)

Attached (minor!) patch to linux-gpib.spec fixes this,
by adding a BuildRequires for the perl subpackage. 
-- 
 Drexel University    \V               --Chuck Lane
======]---------->-----*------<--------[===========
     (215) 895-1545   / \_/*~~~~~  Particle Physics
FAX: (215) 895-1281  la...@du...

[Linux-gpib-general] Python 3.7.1 import Gpib

[Anderson M. B. <amb...@uc...>]

Hello,
I successfully installed the linux-gpib package, and when I run the import
Gpib command on python 2.7 everything happens perfectly. But now I'm trying
to import the package with python 3.7.1, installed with anaconda, and
import is returning me the following error:

Python 3.7.1 (default, Dec 14 2018, 19:28:38)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.

import Gpib
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'Gpib'

I appreciate if someone helps me.

-- 
Enviado via UCSMail.

[Linux-gpib-general] Cannot make linux-gpib-kernel-4.2.0

[Werner K. <wer...@on...>]

Hi,

I followed the installation description in the linux-gpib-kernel-4.2.0 directory until the 
make-command. In the output I get

echo >&2;                                                       \ 


*/home/werner/GPIB/linux-gpib-4.2.0/linux-gpib-kernel-4.2.0/drivers/gpib/lpvo_usb_gpib/
lpvo_usb_gpib.c:621:13:* *err*
unknown type name ‘*wait_queue_t*’; did you mean ‘*wait_event*’? 
*w*ait_queue_t 
*^*

I ran "make oldconfig && make prepare" without error, but the errors above remained. I 
looked for the type-description ‘*wait_queue_t*’ but didn't find anything apart a remark in 
a log-file that didn't help me  ( "include /sys/sysmacros.h for minor() definiton" )

My system:  OpenSuse Leap 15.0,  x86_64, kernel  4.12.14-lp150.12.48-default

Now I don't know how fix that problem. I am not a big expert in Linux.
Do you have any idea, any hint

Best regards
Werner

[Linux-gpib-general] linux-gpib Ubuntu installation help

[Anderson M. B. <amb...@uc...>]

Hello, I'm trying to install the linux-gpib-kernel-4.2.0 on my ubuntu
UBUNTU 18.04.1 LTS.
I updated the kernel to 4.19.0-041900-generic and proceeded to install the
driver.

When I run the make command, this returns me the following error

echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 "
include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";
\ echo >&2 ; \ /bin/false)

I would appreciate a more detailed step-by-step guide on how to do this
installation.

-- 
Enviado via UCSMail.

Re: [Linux-gpib-general] mystery problem

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

what happens when you run gpib_config?

On Tue, Feb 19, 2019 at 3:14 AM Hosni Limam <hos...@gm...> wrote:
>
> I encountered a problem with my gpib system and I am struggling to
>
> diagnose it. I would appreciate any suggestions you may have.
>
>  I have to communicate Agilent E3640a with raspberry pi 3 using gpib_usb_hs
>
> When I try connecting to any device using ibtest, I receive the error:
>
>
>
> libgpib: IBOPENDEV ioctl failed
>
> libgpib: error in is_cic()!
>
> ibdev error
>
>
>
> ibsta = 0x8000  < ERR >
>
> iberr= 0
>
> EDVR 0: OS error
>
>
>
> ibcntl = 19
>
> Abandon
>
>
> Thank you!
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general



-- 
Frank

[Linux-gpib-general] mystery problem

[Hosni L. <hos...@gm...>]

I encountered a problem with my gpib system and I am struggling to

diagnose it. I would appreciate any suggestions you may have.

 I have to communicate Agilent E3640a with raspberry pi 3 using gpib_usb_hs

When I try connecting to any device using ibtest, I receive the error:



libgpib: IBOPENDEV ioctl failed

libgpib: error in is_cic()!

ibdev error



ibsta = 0x8000  < ERR >

iberr= 0

EDVR 0: OS error



ibcntl = 19

Abandon


Thank you!

Re: [Linux-gpib-general] Prologic GPIB-USB adaptors

[Patrick <pa...@sp...>]

Hi John

I don't really know anything about Sigrok. Is this a free open-source 
application? You could pick out the commands from the code and send them 
over serial to your prologix device. Otherwise, I am out of ideas

Re: [Linux-gpib-general] Prologic GPIB-USB adaptors

[John <su...@qc...>]

Patrick,

Yes, that's true. On Windows you access it via a COM port, on Linux its
/dev/ttyUSBx port. However, I would like to use my Schlumberger 7150+
DMM with Sigrok on Linux. I have been advised that Sigrok support for
GPIB is via linux-gpib but since linux-gpib does not have support for
this particular adapter I am unable to use my DMM with Sigrok. What is
missing is a means for Sigrok to talk to USB GPIB devices using the
Prologix protocol. Perhaps if I had an NI card, this might have been
possible via linux-gpib.

I was perhaps hoping that linux-gpib might already provide a suitable
layer of abstraction as per NI or Matlab, but as I have been advised,
this particular adapter is not supported and support is not planned so
I guess I will have to pursue other options such as writing a suitable
native driver for Sigrok or (cringe) using something on Windows.

Regards.



On Thu, 2019-01-10 at 09:45 -0500, Patrick wrote:
> Hi John
> 
> Prologix is cross platform. Don't you just have to switch the serial 
> port name? COM1 -> /dev/ttyUSB0 etc ?
> 
-- 
John.

Re: [Linux-gpib-general] Prologic GPIB-USB adaptors

[Patrick <pa...@sp...>]

Hi John

Prologix is cross platform. Don't you just have to switch the serial 
port name? COM1 -> /dev/ttyUSB0 etc ?