| 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 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: streamDevice Exception Handler Question |
| From: | Dirk Zimoch <[email protected]> |
| To: | [email protected] |
| Date: | Mon, 19 Nov 2012 17:48:24 +0100 |
On 15.11.2012 15:33, Martin L. Smith wrote:
When using steamDevice exception handlers and in particular the replytimeout and readtimeout handlers, what would one normally do in these handlers?
Probably send something to the device to reset it. Not much that would help EPICS. I once used it to change the baud rate because the device always started with a slow baud rate after power on.
For a mismatch I simply get whatever the received data was and put that in a string record for display so that I know that something went wrong ... since the error messages are now suppressed from this error.
Are they? They should be suppressed for "I/O Intr" records only. I will check. A mismatch handler allows you to re-parse the input. But the other handlers don't.
Is it possible to set a PV to a value without using an "in" command? Or would I simply look at the STAT field of the record using the protocol to know that something happened in the case of a timeout error?
Unfortunately I have no way (so far) to set PVs to some constant value. but perhaps....: in "%#{=17}"; would probably set the value 17 independently on the input, but only if there is any input.
Dirk
Thanks, Marty