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: No reply from device using asyn+streamdevice |
From: | Eric Norum <[email protected]> |
To: | [email protected] |
Cc: | EPICS <[email protected]> |
Date: | Wed, 12 Sep 2018 06:31:05 -0700 |
I’ve been following this thread while on travel the past few days. One thing that I’ve not seen is the results of enabling ASYN device I/O messages to see what the device is actually sending. What do you see if you add the following to your st.cmd file after configuring the port: asynSetTraceIOMask(“<<your port name>>”,0,0x2) asynSetTraceMask(“<<your port name>>”,0,0x9) Apologies if this has already been mentioned and I’ve just missed the message suggesting it.
--
Eric Norum [email protected] |