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 "No reply from device" messages |
From: | Ralph Lange <[email protected]> |
To: | EPICS Tech-Talk <[email protected]> |
Date: | Fri, 06 Dec 2013 13:12:14 +0100 |
On 06.12.2013 12:42, [email protected] wrote:
Hello John, A database modification may be enough to achieve a quiet console: Have all the records that read the device disabled by a single control record, using the SDIS field. Then one single toggle removes many error messages on the console. I paste below an example from a lakeshore controller. Regards, Ronaldo record(bo, "$(P):DISABLE") { | field(DESC, "Disable comms") | field(PINI, "YES") | field(VAL, "0") | field(OMSL, "supervisory") | field(ZNAM, "Enabled") | field(ONAM, "Disabled") | } record(stringin, "$(P):ID") { | field(DTYP, "stream") | field(SDIS, "$(P):DISABLE") | field(INP, "@lakeshore336.proto getID $(PORT) $(ADDR)") | field(SCAN, "$(SCAN) second") | } |
I have seen people use some harmless status value of the device, scan that record every 10 seconds, and use its SEVR as the disable input for all other (faster) records polling the same device.
That way, when the device goes down the sources of error messages are automatically reduced to one record every 10 seconds, connection status is checked every 10 seconds, and the full set of fast scanning records continues automatically when the device is back.
Note that the SDIS links pull records into one lock set. You might want to set those to CA to avoid that.
~Ralph