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]>, Mark Rivers <[email protected]> |
Cc: | Marty Kraimer via Tech-talk <[email protected]> |
Date: | Wed, 17 Jul 2019 10:28:10 -0700 |
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?
|