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: Linking a HIGH and LOW field to a PV |
From: | "Hu, Yong" <[email protected]> |
To: | "Dudley, David" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Mon, 21 Nov 2016 20:25:14 +0000 |
The magic word "CP" does magic thing (automatically getting updated value) only when it is used in a field whose type is INLINK (DBF_INLINK, input link), i.e. the field DOL of ao, INP of ai, etc.
See "5.12 Channel Access Links" at
http://www.aps.anl.gov/epics/base/R3-14/12-docs/AppDevGuide/node6.html
The field type of LOW/HIGH of ao is DOUBLE. See https://wiki-ext.aps.anl.gov/epics/index.php/RRM_3-14_Analog_Output
And what is more: you should see error message during iocInit if you load your .db file just like you wrote below (... field(LOW, "$(P):SUBCRYO_SETP_MIN.VAL CP") ... ).
Yong HU
NSLS-II Controls Group
From: <[email protected]> on behalf of "Dudley, David" <[email protected]>
Date: Monday, November 21, 2016 at 11:30 AM To: "[email protected]" <[email protected]> Subject: RE: Linking a HIGH and LOW field to a PV Wouldn’t a SEQuencer record be more appropriate for moving a bunch of values from one place to another? Later-
From:
[email protected] [mailto:[email protected]]
On Behalf Of Steiner, Mathias The brute force approach would be to use a calcout... record(calcout, "$(P):SUBCRYO_SET_LOW") { field(INPA, "$(P):SUBCRYO_SETP_MIN.VAL CP") field(OUT , "$(P):SUBCRYO_SETP_S.LOW PP") ..and similar for .HIGH. It’s the opposite of elegant but it’ll work. cheers -mathias From:[email protected]
[mailto:[email protected]]
On Behalf Of Bo Jakobsen Hi |