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: | Representing stateless device commands? |
From: | "Feister, Scott via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Fri, 5 Jan 2024 18:47:33 +0000 |
Hi EPICS community, I searched the tech-talk forums and documentation for this answer for a long time, because I am confident it’s in there somewhere if I could just search the correct words. However, after a long search, I decided I would stop and ask the
forum. How can I represent a command to a device (using StreamDevice) for a command that does not involve a process variable? For example, let’s say I have a device that has a single LED. It may accept two commands over RS232 such as: DecreaseBrightness IncreaseBrightness ToggleOnOff Since these commands operate on internal states to the device rather than states we as the user can access, we don’t actually have a PV state accessible directly to put into an EPICS PV. We just want to call those methods remotely from
EPICS. How can I basically send the above commands like I would in a Serial Terminal, but with EPICS? My approach right now is to call them binary outputs (bo) records, e.g. a bo record named “MYLED:IncreaseBrightness” and then just ignore the PV value itself. Then I do “caput MYLED:IncreaseBrightness 1” every time I want to increase brightness.
Is that a reasonable approach? Thanks! Scott |