EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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  <2019>  2020  2021  2022  2023  2024  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  <2019>  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: USBTMC Device can not autoConnect
From: Eric Norum via Tech-talk <[email protected]>
To: Christopher Herrmann <[email protected]>
Cc: Marty Kraimer via Tech-talk <[email protected]>
Date: Wed, 17 Jul 2019 08:46:45 -0700
Try explicitly specifying the vendor ID, product ID, and, if necessary, the serial number string.  Perhaps there’s some other device on the new machine that’s showing up before your power supply when the connect method scans fof USBTMC devices.
What does the lsusb command show? (I’m presuming that you’re using Linux)
The connect method sets the ASYN error string before returning a fault indication but I’m not sure how to get the ASYN autoconnect mechanism to print it.  Marty/Mark, would disabling autoconnect (by setting the last argument of the usbtmcConfigure command to 1) and then explicitly attempting a connect print the USBTMC connect error string?

On Jul 17, 2019, at 8:03 AM, Christopher Herrmann via Tech-talk <[email protected]> wrote:

Hello,

I am currently trying to interface with a Keithly 2230G multichannel power supply over USBTMC.

When I plug in the device it appears at "/dev/usbtmc0" and I have the permissions set that
I should be able to access it. However, when running the IOC I get the following message:

usbtmcConfigure("U0")
No device information specified.  Will connect to first USB TMC device found.
2019/07/17 10:51:18.202 U0 -1 autoConnect could not connect

I am in the process of transferring my IOC from one computer to another. This command would
just magically work on the previous device, but not on this one.

Any suggestions would be appreciated.

~ Chris

— 
Eric Norum




References:
USBTMC Device can not autoConnect Christopher Herrmann via Tech-talk
Navigate by Date:
Prev: Re: SmarAct MCS2 ASCII-based IOC Peterson, Kevin M. via Tech-talk
Next: Re: USBTMC Device can not autoConnect Eric Norum 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  <2019>  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: USBTMC Device can not autoConnect Christopher Herrmann via Tech-talk
Next: Re: USBTMC Device can not autoConnect Eric Norum 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  <2019>  2020  2021  2022  2023  2024 
ANJ, 17 Jul 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·