EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  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  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: ASYN & ioclog/CMLOG
From: "Mark Rivers" <[email protected]>
To: "Heinrich du Toit" <[email protected]>, "TechTalk EPICS" <[email protected]>
Date: Wed, 5 Sep 2007 13:43:44 -0500
Heinrich,

> or what is the errlog facility?

The asynTrace utility either outputs to the EPICS errlog facility or
directly to a file specified with the asynSetTraceFile command.  The
EPICS errlog facility allows logging both to the console and to disk
files.  The EPICS errlog facility is documented in Chapter 10 of the
Application Developers Guide.

> An operator sitting with a MEDM interface might be completely unaware
of errors on the IOC.

One way to make an operator aware of errors on the IOC is through the
EPICS alarm system.  If an asyn driver is detecting a problem then the
associated records should go into alarm, which can then be displayed
with medm.

I know of no way to display the error messages with channel access, but
other clients can certainly be used to display the log files. 

Mark


> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Heinrich du Toit
> Sent: Monday, August 27, 2007 4:31 AM
> To: TechTalk EPICS
> Subject: ASYN & ioclog/CMLOG
> 
> Hi
> 
> General question
> 
> When I develop and ASYN driver. I use the ASYN-trace facility 
> interface
> to output debugging/error stuff.
> 
> Now when the driver is done. And it is used. I figured it might make
> sense that that the error (and maybe the flow output also?) 
> be output to
> ioclog or CMLOG?
> 
> What would be the best way to enable this? 
> Is there some PV or something that can be hooked up to the trace
> interface? 
> I see asynRecord does connect to asynTrace. But it hardly gives any
> exstra ability? or what is the errlog facility?
> 
> I also noted that it is good that ASYN now outputs the ERROR messages
> using trace.
> But this data doesn't go any further. An operator sitting with a MEDM
> interface might be completely unaware of errors on the IOC.
> 
> I'm sure people have already noticed this :) So your 
> solutions would be
> interesting (remember I'm new to EPICS)
> 
> -Heinrich
> 
> 
> 


References:
ASYN & ioclog/CMLOG Heinrich du Toit

Navigate by Date:
Prev: Re: channelwatcher vs BURT Carl Lionberger
Next: EPICS Extensions Szalata, Zenon M.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: ASYN & ioclog/CMLOG Heinrich du Toit
Next: Soft IOC for A GPIB Instrument Szalata, Zenon M.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·