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: CryoTel GT Cooler: different startup and shutdown StreamDevice protocols |
From: | Žiga Oven via Tech-talk <tech-talk at aps.anl.gov> |
To: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
Date: | Fri, 24 May 2024 08:03:29 +0000 |
Regarding protocol executing twice with the bo record, I would just like to add that you can send different strings for VAL=0 or VAL=1 (look at the StreamDevice documented
Example Protocol File [1], specifically setSwitch protocol). Best regards, Žiga [1]
https://paulscherrerinstitute.github.io/StreamDevice/protocol.html From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Ralph Lange via Tech-talk On Fri, 24 May 2024 at 07:38, boj <lister at f77.dk> wrote:
Yes, correct. No decent way to avoid that. Then, just don't set the HIGH field. Whatever value is being written to the record, the protocol will be executed.
As Dirk was asking: Do you need the response? Can't you just ignore it?
Switch or buttons is a design choice. Buttons always need a status, else you never know the current device state. A switch position needs to be readable from the device or persisted (autoSaveRestore), else it might end up in the wrong position after an IOC reboot. Discussing with colleagues, I found some very strong, almost religious, opinions in the underlying "trigger by state or by pulse" question. The EPICS database allows to implement one using the other. Flexibility is nice! Cheers, ~Ralph ps. Having a record named after you is pretty cool. |