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: "Dudley, David" <[email protected]>
To: "[email protected]" <[email protected]>
Date: Mon, 21 Nov 2016 16:30:04 +0000

Wouldn’t a SEQuencer record be more appropriate for moving a bunch of values from one place  to another?

 

Later-

 

David Dudley

Controls Engineer III

Facility for Rare Isotope Beams

Michigan State University

640 South Shaw Lane

East Lansing, MI 48824-1321, USA

Tel. 517-908-7133

Email: dudleyd@frib.msu.edu

 

 

cid:image002.jpg@01D07041.57B6D750

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Steiner, Mathias
Sent: Monday, November 21, 2016 9:13 AM
To: Bo Jakobsen <[email protected]>; [email protected]
Subject: RE: Linking a HIGH and LOW field to a PV

 

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 Hu, Yong
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

Navigate by Date:
Prev: RE: Linking a HIGH and LOW field to a PV Steiner, Mathias
Next: Re: Linking a HIGH and LOW field to a PV Hu, Yong
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 Bo Jakobsen
Next: Re: Linking a HIGH and LOW field to a PV Hu, Yong
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, 23 Nov 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·