2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 | Index | 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: Possible Access Rights improvement? |
From: | "Kasemir, Kay" <[email protected]> |
To: | EPICS Core Talk <[email protected]> |
Date: | Thu, 24 Aug 2017 20:40:52 +0000 |
Your calc record example is good.
Assume record(calc, "ramp") { field(INPA, "ramp") field(CALC, "A+1") field(SCAN, "1 second") }
In this case you _can_ display the record in a TextEntry field. Most of the time, the record counts up on its own. But you can also enter "0" or "1000" to reset the ramp, or move it ahead.
Somewhat tricky to decide inside the IOC if the VAL field should allow write access or not.
It's really up to the person who creates this database to decide: Do I add access security to make it read-only? Or do I allow writing, but only to those in-the-know, because on the displays I present it with a Text Update? Or do I intent for this to be written by mere mortals, so I use a Text Entry on the display?
-Kay |