Experimental Physics and
Industrial Control System

Dirk Zimoch <[email protected]> · Tue, 22 Nov 2011 09:24:08 +0100

Zhang, Dehong wrote:

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

If a protocol has only ACK as a reply, you can work with maxinput=1 and

no interminator. Interminator and maxinput can both be set on a per

protocol base.

If I understand correctly, none of the replies has a terminator, all

start with ACK (if successful) and probably those which return a value

have a fixed number of characters. Is that correct?

inTerminator="";

simpleCommand {
  maxInput=1;
  out "command";
  in ACK;
}

readValue {
  maxInput=5; # assume 5 char reply: ACK + 4 char int
  out "value?";
  in ACK "%d";
}

Dirk

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System