Hi,
I tried bracketing my read of 'ACK' with 'MaxInput=1' and
'MaxInput=0',
but it didn't help - still nothing in my PV.
At them moment, you cannot change variables at run-time. The protocol
starts and runs with the last setting. Thus this:
Well, that explains it.
In cases you have no terminator string but constant length input, using
MaxInput saves you from using readTimeout as the line terminator. Thus
you have no delay at the end of the input and no danger that two lines
join to one in case readTimeout is too long.
OK, that's useful to know - this particular controller seems to have
fixed lengths for each response type.
Thanks,
Richard
- References:
- Parsing problem with stream Lucock, Richard M
- Re: Parsing problem with stream Dirk Zimoch
- Re: Parsing problem with stream Lucock, Richard M
- Re: Parsing problem with stream Dirk Zimoch
- Navigate by Date:
- Prev:
Re: Parsing problem with stream Dirk Zimoch
- Next:
Stringin - asynOctedRead type how to set string length Pilar Gil Jaldo
- 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: Parsing problem with stream Dirk Zimoch
- Next:
Re: Parsing problem with stream Florian Feldbauer
- 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
|