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> 2025 | 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> 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: [EXTERNAL] Representing stateless device commands? |
From: | "Feister, Scott via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Hartman, Steven" <hartmansm at ornl.gov> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Sat, 6 Jan 2024 00:11:19 +0000 |
Thanks Steven and Mark, for your welcoming and helpful responses. I have the streamDevice proto files written, and am at the point where I’m wondering if there’s an easy way to capture what Steven is suggesting – forcing the PV back to zero immediately after the RS232 command “IncreaseBrightness” has
been sent, such that the state of the binary PV “MYLED:IncreaseBrightness” represents whether we are “in process” of “Increasing Brightness”? Here’s what I have in mind as far as sequence:
I have steps 1-3 under control with StreamDevice, so I’m wondering about best practices to implement Step 4. Thanks! Scott From: Hartman, Steven <hartmansm at ornl.gov> CAUTION: This email originated from outside of CSUCI. Do not click links or open attachments
unless you validate the sender and know the content is safe. Contact ITS if you have any concerns
Welcome to the forum. Yes, that sounds about right. You can use the ONAM and ZNAM fields of the BO record to name the two states which may convey that it is indeed a process variable that is either doing something (i.e., increase the brightness) or not. In EPICS, pretty much everything is
a process variable. |