one nice feature for that could be using the streamdevice debug output
. It takes a while sorting it out because it will print out everything
but it helps often.
Try logging it to a file or if you use procserv just take the logfile.
Nice starting point is "grep uffer logfile.txt"
that shows the "input Buffer" as well as the "output buffer"
on the epics console just enter
"streamDebug=1" to enable it.
how the output ends up in the input is rather strange.
- References:
- StreamDevice communication problems Tito Körner
- Navigate by Date:
- Prev:
RE: StreamDevice communication problems Mark Rivers
- Next:
Re: ICALEPCS Agenda - Andrew Johnson
- 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
- Navigate by Thread:
- Prev:
RE: StreamDevice communication problems Mark Rivers
- Next:
Re: StreamDevice communication problems Dirk Zimoch
- 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
|