EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
<== Date ==> <== Thread ==>

Subject: RE: USBTMC Device can not autoConnect
From: Mark Rivers via Tech-talk <tech-talk@aps.anl.gov>
To: 'Eric Norum' <wenorum@lbl.gov>, Christopher Herrmann <ch852@cornell.edu>
Cc: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Thu, 18 Jul 2019 15:55:16 +0000

On Centos7 the only packages available that contain libusb-1.0.so are the libusbx ones:

 

 

corvette:local/epics-devel/base-7.0.2>sudo yum provides '*/libusb-1.0.so*'

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

* base: ftp.usf.edu

* epel: d2lzkl7pfhq30w.cloudfront.net

* extras: mirror.cs.vt.edu

* updates: ftp.ussg.iu.edu

libusbx-1.0.21-1.el7.i686 : Library for accessing USB devices

Repo        : base

Matched from:

Filename    : /usr/lib/libusb-1.0.so.0.1.0

Filename    : /usr/lib/libusb-1.0.so.0

 

libusbx-1.0.21-1.el7.x86_64 : Library for accessing USB devices

Repo        : base

Matched from:

Filename    : /usr/lib64/libusb-1.0.so.0.1.0

Filename    : /usr/lib64/libusb-1.0.so.0

 

libusbx-devel-1.0.21-1.el7.i686 : Development files for libusbx

Repo        : base

Matched from:

Filename    : /usr/lib/libusb-1.0.so

 

libusbx-devel-1.0.21-1.el7.x86_64 : Development files for libusbx

Repo        : base

Matched from:

Filename    : /usr/lib64/libusb-1.0.so

 

libusbx-1.0.21-1.el7.i686 : Library for accessing USB devices

Repo        : @base

Matched from:

Filename    : /usr/lib/libusb-1.0.so.0.1.0

Filename    : /usr/lib/libusb-1.0.so.0

 

libusbx-1.0.21-1.el7.x86_64 : Library for accessing USB devices

Repo        : @base

Matched from:

Filename    : /usr/lib64/libusb-1.0.so.0.1.0

Filename    : /usr/lib64/libusb-1.0.so.0

 

libusbx-devel-1.0.21-1.el7.i686 : Development files for libusbx

Repo        : @base

Matched from:

Filename    : /usr/lib/libusb-1.0.so

 

libusbx-devel-1.0.21-1.el7.x86_64 : Development files for libusbx

Repo        : @base

Matched from:

Filename    : /usr/lib64/libusb-1.0.so

 

Those are installed on my system.  But I don’t have any USBTMC devices to test.

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> On Behalf Of Eric Norum via Tech-talk
Sent: Wednesday, July 17, 2019 1:15 PM
To: Christopher Herrmann <ch852@cornell.edu>
Cc: Marty Kraimer via Tech-talk <tech-talk@aps.anl.gov>
Subject: Re: USBTMC Device can not autoConnect

 

On Jul 17, 2019, at 11:00 AM, Christopher Herrmann <ch852@cornell.edu> wrote:

 

Both systems have the same version of EPICS retrieved from github. I also believe that both systems have the same version of ASYN.

Is the version number listed somewhere in the module so that I can double check?

Check your application configure/RELEASE file.

Here for example are the salient lines from a test IOC here:

ASYN       = /eda/epics/R3.15.5/modules/soft/asyn/asyn4-31

AUTOSAVE   = /eda/epics/R3.15.5/modules/soft/autosave/autosave-5-1

IOCEXIT    = /eda/epics/R3.15.5/modules/soft/iocExit/iocExit-2-0

EPICS_BASE = /eda/epics/R3.15.5/base

I can't remember if I got them from the module github

page or if I pulled them out of synApps and compiled them. Is there a preferred method?

 

The libusb question gets a bit interesting. The first system was debian based and so I installed libusb-1.0 via apt. 

Running dpkg --get-selections | grep libusb gives me this output on the debian system.

 

libhidapi-libusb0:amd64 install
libusb-0.1-4:amd64 install
libusb-1.0-0:amd64 install
libusb-1.0-0:i386 install
libusb-1.0-0-dev:amd64 install
libusb-1.0-doc install
libusb-dev install
libusbmuxd4:amd64 install

 

When I was compiling asyn for the Scientific Linux system it kept complaining that <libusb/libusb-1.0.h> was not found.

I had someone install what I thought was the correct package, but still got the same error when compiling.

Someone else then mentioned something about libusb vs libusbx. Here is the output from running rpm -qa | grep libusb

on the Scientific Linux system:

 

libusbx-devel-1.0.21-1.el7.x86_64
libusbmuxd-1.0.10-5.el7.x86_64
libusb-0.1.4-3.el7.x86_64
libusb-devel-0.1.4-3.el7.x86_64
libusbx-1.0.21-1.el7.x86_64

 

Could that have something to do with it?

 

I’ve not used libusbx and it sounds like it really isn’t the right package to use.

From the libusb wiki:

 

libusb.org was the original home for libusb project. Now it still exists but the information and code are quite outdated.

 

libusb.info is the current home page for libusb project.

 

libusbx was a fork of libusb and libusbx.org is its website. As of 2014.01.26, libusbx project has been fully merged back into libusb and is being discontinued. libusbx.org is no longer related to libusb project.

 

 

-- 

Eric Norum
wenorum@lbl.gov



 


References:
USBTMC Device can not autoConnect Christopher Herrmann via Tech-talk
Re: USBTMC Device can not autoConnect Eric Norum via Tech-talk
Re: USBTMC Device can not autoConnect Eric Norum via Tech-talk
Re: USBTMC Device can not autoConnect Eric Norum via Tech-talk
Re: USBTMC Device can not autoConnect Eric Norum via Tech-talk

Navigate by Date:
Prev: Re: pasynOctetSyncIO flushing with drvAsynIPPortConfigure Hinko Kocevar via Tech-talk
Next: RE: SmarAct MCS2 ASCII-based IOC Stubbs Scott Allen (PSI) via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
Navigate by Thread:
Prev: Re: USBTMC Device can not autoConnect Eric Norum via Tech-talk
Next: Add widgets to Phoebus Hasbroucq Dorian via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020