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>
Cc: Christopher Herrmann <ch852@cornell.edu>, Marty Kraimer via Tech-talk <tech-talk@aps.anl.gov>
Date: Wed, 17 Jul 2019 22:05:45 +0000
I don’t see why it’s not printing the error message returned from the driver.

Mark


Sent from my iPhone

On Jul 17, 2019, at 1:28 PM, Eric Norum <wenorum@lbl.gov<mailto:wenorum@lbl.gov>> wrote:

I  checked that autoConnect code and it does print the error message supplied by the driver:

    if (!pdpCommon->connected) {
        epicsMutexMustLock(pport->synchronousLock);
        status = pasynCommon->connect(drvPvt,pasynUser);
        epicsMutexUnlock(pport->synchronousLock);
    }
    if(status!=asynSuccess) {
        asynPrint(pasynUser,ASYN_TRACE_ERROR,
            "%s %s %d autoConnect could not connect\n",
            pasynUser->errorMessage,pport->portName,addr);
    }

So the fact that there’s nothing printed between the time and the port name implies that the USBTMC connect method is returning a value other than asynSuccess but is not filling in an error message.
I had a look through drvAsynUSBTMC.c and can see no place that its connect method returns asynError without filling a value into pasynUser->errorMessage.
What version of ASYN are you using?
Mark, any idea what’s going on here?

On Jul 17, 2019, at 9:55 AM, Christopher Herrmann <ch852@cornell.edu<mailto:ch852@cornell.edu>> wrote:

I tried the command you suggested. Here is the output when running the IOC.

usbtmcConfigure("U0", 0x05E6, 0x2230, "", 0, 0)
Will connect to first USB TMC device found with vendor ID 0x05e6 and product ID 0x2230.
2019/07/17 12:53:34.209 U0 -1 autoConnect could not connect



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

Navigate by Date:
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 
Navigate by Thread:
Prev: Re: USBTMC Device can not autoConnect Eric Norum via Tech-talk
Next: RE: USBTMC Device can not autoConnect Mark Rivers 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