Re: StreamDevice protocol file question

["Zimoch Dirk \(PSI\) via Tech-talk" <tech-talk at aps.anl.gov>]

Use in „OK“. Then the record is in no alarm state when the device responds OK and in INVALID alarm state when the device responds BAD.

You can redirect the response to another record if you like. To a bi for example:

in „%(otherrecord){OK|BAD}“

In that other record you may want to set an alarm on the one state.

You should get an error with in „“ except if you have extrainput=ignore.

Dirk

Am 30.07.2021 um 16:22 schrieb Wang, Andrew via Tech-talk <tech-talk at aps.anl.gov>:



All,

Quick question about the protocol file in StreamDevice. Suppose I have an instrument where after I send a command to change one of its attributes, it responds back with a status of either  OK or BAD. Furthermore, I have an analog output record, whose value is used by a protocol file. 

If I want to properly flush the status response, what is the preferred method of doing so, especially since the status response is a string, not a scaler value.

What I’m currently doing in the protocol is this:

setProp

{

       out “set %f”;

       in “”;

}

What is weird is that I am not getting a mismatch error, and it does seem like I am properly flushing the input with that method.

After looking at other code, Is it better to do this?

setProp

{

       out “set %f”;

       in “%*s”; # or this “%*f”;

}

Thanks!

Andy

Get Outlook for iOS