https://code.launchpad.net/~bhill/epics-base/+git/epics-base/+merge/341081
might be relevant. In summary, use of the TPRO field as a log level or bitmask
is not uncommon.
More broadly, better control of logging is generally seen as desirable.
On 2/5/20 7:02 AM, Torsten Bögershausen via Core-talk wrote:
> Hej asyn & motor & record experts:
>
> While debugging this and that, I find more and more that
> asynPrint() is a very useful feature.
>
> Timestamps can be printed, file/line and/or the thread, all
> is configurable in runtime.
>
> Now to my question:
> Is it a good idea to use it during record processing ?
>
> Since the motorRecord does not have access to asyn directly,
> all prints are fiddled through device support, which has
> asyn.
>
> In other words, this nice print works only for asynMotors
> (But that restriction is OK).
>
> I have done a prototype here:
> <https://github.com/tboegi/motor/commit/9aebabdf551a24bd138d483808130af57888a9e0>
>
> Any feedback or better ideas are welcome.
>
> Thanks
> /Torsten
- References:
- Using asynPrint() from motorRecord ? Torsten Bögershausen via Core-talk
- Navigate by Date:
- Prev:
Using asynPrint() from motorRecord ? Torsten Bögershausen via Core-talk
- Next:
Re: Using asynPrint() from motorRecord ? Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Using asynPrint() from motorRecord ? Torsten Bögershausen via Core-talk
- Next:
Re: Using asynPrint() from motorRecord ? Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|