EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  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  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Linking a HIGH and LOW field to a PV
From: Bo Jakobsen <[email protected]>
To: "[email protected]" <[email protected]>
Date: Tue, 22 Nov 2016 09:24:25 +0100
Thanks for the input

I will try this,

It is still unclear to me if the problem is to get the ao record to process the value or if it is simply not possible to define the HIGH and LOW fields as CA links.

Best
    Bo

On 2016-11-21 15:12, Steiner, Mathias wrote:

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(CALC, “A”)

  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
Sent: Monday, November 21, 2016 09:01
To: [email protected]
Subject: Linking a HIGH and LOW field to a PV

 

Hi

I am trying to get "limits" to work on a "Soft Channel" record.
The challenge is that I have the limit values in another record, and want to make a link between the two records.

I would therefore like to something like this:

record(ao, "$(P):SUBCRYO_SETP_S") {
  field(DESC, "Huginn Sub-cryostat system setpoint")
  field(DTYP, "Soft Channel")
  field(VAL, "300")
  field(PREC, "3")
  field(EGU, "K")
  field(PINI, "YES")
  field(HSV, "MINOR")
  field(LSV, "MINOR")
  field(LOW, "$(P):SUBCRYO_SETP_MIN.VAL CP")
  field(HIGH, "$(P):SUBCRYO_SETP_MAX CP")
}


which, however, does not work.
It this possible, and in that case how.

Thanks in advance.
    Bo



Replies:
RE: Linking a HIGH and LOW field to a PV Arnold, Ned D.
Re: Linking a HIGH and LOW field to a PV Andrew Johnson
References:
EPICS Base Release-Candidate Double Feature! Andrew Johnson
RE: EPICS Base Release-Candidate Double Feature! freddie.akeroyd
Re: EPICS Base Release-Candidate Double Feature! Andrew Johnson
RE: EPICS Base Release-Candidate Double Feature! freddie.akeroyd
Re: EPICS Base Release-Candidate Double Feature! Johnson, Andrew N.
RE: EPICS Base Release-Candidate Double Feature! freddie.akeroyd
Re: EPICS Base Release-Candidate Double Feature! Matt Rippa
Re: EPICS Base Release-Candidate Double Feature! Andrew Johnson
Re: EPICS Base Release-Candidate Double Feature! Matt Rippa
Re: EPICS Base Release-Candidate Double Feature! Andrew Johnson
RE: Linking a HIGH and LOW field to a PV Steiner, Mathias

Navigate by Date:
Prev: Re: Control system remote access Maren Purves
Next: RE: Control system remote access Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Linking a HIGH and LOW field to a PV Steiner, Mathias
Next: RE: Linking a HIGH and LOW field to a PV Arnold, Ned D.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 22 Nov 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·