Argonne National Laboratory

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  <20132014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: RE: StreamDevice "No reply from device" messages
From: Mark Rivers <rivers@cars.uchicago.edu>
To: Eric Norum <eric@norum.ca>, John Dobbins <john.dobbins@cornell.edu>
Cc: EPICS Tech Talk <tech-talk@aps.anl.gov>
Date: Thu, 5 Dec 2013 19:45:08 +0000
Nope, that won't work, because streamDevice does not currently use the asynTrace facility to print error messages.  I've suggested that Dirk change StreamDevice to do this, but it is non-trivial because most of StreamDevice is not aware of asyn, and does not necessarily have access to the required asynUser structure when it needs it.



Mark



________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Eric Norum [eric@norum.ca]
Sent: Thursday, December 05, 2013 1:41 PM
To: John Dobbins
Cc: EPICS Tech Talk
Subject: Re: StreamDevice "No reply from device" messages

Set the asyn trace flags to 0 for the port in question -- in particular the least-significant-bit which controls error-level messages.
 From the IOC shell
asynSetTraceMask("<port>",-1, 0)
or use an asynRecord and a client of your choice.


On Dec 5, 2013, at 11:33 AM, John Dobbins <john.dobbins@cornell.edu<mailto:john.dobbins@cornell.edu>> wrote:

All,

I frequently encounter this situation and am wondering how to best address it:

An IOC will have a device connected via StreamDevice. In my case it is typically a serial device connected though a serial-to-ethernet server. For some reason the serial device is not responding and the IOC console will have frequent "No reply from device" messages making it difficult to use the IOC console.

These messages come from StreamCore which calls error() - defined in StreamError to print to stderr.

I don't see any built in way to redirect these messages. I can imagine various changes but I am wondering what approach others may have taken or might suggest.

Regards,

John Dobbins
Cornell University

epics base R3.14.2
stream 2.5.1
asyn 4.19
linux-x86_64

--
Eric Norum
eric@norum.ca<mailto:eric@norum.ca>






Replies:
Re: StreamDevice "No reply from device" messages Andrew Johnson
References:
StreamDevice "No reply from device" messages John Dobbins
Re: StreamDevice "No reply from device" messages Eric Norum

Navigate by Date:
Prev: Re: StreamDevice "No reply from device" messages Eric Norum
Next: Re: StreamDevice "No reply from device" messages Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: StreamDevice "No reply from device" messages Eric Norum
Next: Re: StreamDevice "No reply from device" messages Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·