We have a 53210A frequency counter that adds "\r\n53210A> " at the end of its responses. So we specified that as the InTerminator. That worked fine until we got a 53220A. We'd like to use both of them with as little redundant code as possible. The only difference in the protocol is that 1 vs. 2 in the response. Is there a way to accommodate that small difference?
Selected lines from the protocol file:
#
InTerminator = "\r\n53210A>";
OutTerminator = CR LF;
GET_FREQ { out "READ?"; in "READ?\r\n%E";}
Messages from asyn related to this:
2017/03/15 16:34:21.577672 agilFC2 FCNT:AS01:1:FREQ_RBCK_RAW: Timeout after reading 39 bytes "...54132E+008<0d><0a>53220A> "
2017/03/15 16:34:22.239 diag-as01-ls02:5024 write 7
READ?\r\n
2017/03/15 16:34:22.240 diag-as01-ls02:5024 read 7
READ?\r\n
2017/03/15 16:34:22.581 diag-as01-ls02:5024 read 32
+1.18999946460060E+008\r\n53220A>
2017/03/15 16:34:27.585987 agilFC2 FCNT:AS01:1:FREQ_RBCK_RAW: Timeout after reading 39 bytes "...60060E+008<0d><0a>53220A> "
Garth
- Replies:
- Re: Streamdevice: wild card in InTerminator? Yongliang Yang
- Re: Streamdevice: wild card in InTerminator? Eric Norum
- Re: Streamdevice: wild card in InTerminator? Pearson, Matthew R.
- Navigate by Date:
- Prev:
Re: EPICS make problem Ben Franksen
- Next:
Re: Streamdevice: wild card in InTerminator? Yongliang Yang
- 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:
Thermocube EPICS Support Martin.Gaughran
- Next:
Re: Streamdevice: wild card in InTerminator? Yongliang Yang
- 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
|