It seems like the right way to fix this is to have your protocol file change the input EOS to ACK or NAK for those commands.
Of course I agree that asyn should be timing out. What happens when you do asynSetTraceTraceMask=255 on the underlying port driver? Do you see the read request, and not see it timeout?
Mark
________________________________
From: [email protected] on behalf of Zhang, Dehong
Sent: Mon 11/21/2011 4:41 PM
To: [email protected]
Subject: streamdevice problem with 1 byte reply
Hi,
For some commands, my device replies with only an "ACK" or "NAK",
no EOS. Streamdevice gets the byte ok, then gets stuck waiting for
more input, but there is no more.
We are "still" using base 3.14.9, asyn 4.10 and streamdevice 2.4.
The replytimeout is set to 900, readtimeout is 100, maxinput is 0.
The problem seems to be asyn not timing out. Could you guys advise
on what I may have missed? Is there a quick fix, instead of upgrading
the whole complex to new versions?
Thanks much and best regards,
Dehong
- Replies:
- RE: streamdevice problem with 1 byte reply Zhang, Dehong
- References:
- streamdevice problem with 1 byte reply Zhang, Dehong
- Navigate by Date:
- Prev:
streamdevice problem with 1 byte reply Zhang, Dehong
- Next:
RE: streamdevice problem with 1 byte reply Zhang, Dehong
- 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:
streamdevice problem with 1 byte reply Zhang, Dehong
- Next:
RE: streamdevice problem with 1 byte reply Zhang, Dehong
- 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
|