Experimental Physics and Industrial Control System
On 09/12/2017 11:19 AM, Iain Marcuson wrote:
>>
>> Is this a situation where those PVs can be updated from either the GUI or the
>> back-end hardware? There are techniques people have developed to handle
>> this correctly if it is.
>
> The PVs are divided into the "Getters" and "Setters". The backend-variables
> can be set in hardware independently of EPICS. The Getters have their OUT
> fields pointed at the Setters.
Great, adding a PP flag to the Getters' OUT fields would cause them to
process the setter records whenever they write a new value, which will
trigger a CA event automatically so you won't need the GUI Refresh. From
the earlier description of your fourth (trigger) PV that should be safe
to do and wouldn't cause a processing loop.
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- References:
- Automatic refresh of OPI Iain Marcuson
- Re: Automatic refresh of OPI Kasemir, Kay
- RE: Automatic refresh of OPI Iain Marcuson
- Re: Automatic refresh of OPI Andrew Johnson
- RE: Automatic refresh of OPI Iain Marcuson
- Navigate by Date:
- Prev:
RE: Automatic refresh of OPI Iain Marcuson
- Next:
MEDM display of string records not updating from PCASpy/PyEpics keith.thorne
- 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
- Navigate by Thread:
- Prev:
RE: Automatic refresh of OPI Iain Marcuson
- Next:
Cannot communicate with S7-400 Antal, Szabolcs
- 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