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

Subject: DRVL, DRVH, HOPR, LOPR
From: Abadie Lana <[email protected]>
To: "[email protected]" <[email protected]>
Date: Wed, 1 Feb 2012 14:25:18 +0100
Hi all
I have a question regarding the process of DRVL, DRVH, HOPR and LOPR.
By default, there are all equals to 0.

In the EPICS record reference manual, it is written that some checks are performed if these limits are defined.

DRVH  Drive High            If these values are defined then VAL will forced to be in       
                            the range:                                                      
                              DRVL<=VAL<=DRVH                                         
DRVL  Drive Low                                                                             
HOPR  High Operating        These fields determine the upper and lower display limits       
      Range                 for graphics displays and the upper and lower control           
                            limits for control displays. The fields are used by record      
                            support to honor calls to get_graphic_double or                 
                            get_control_double.  If these values are defined,               
                            they must be in the range:                                      
                              DRVL<=LOPR<=HOPR<=DRVH.                              
LOPR  Low Operating                                                                         
      Range     

Questions: 
1. how does one (especially the client) know that the limits are really set? And not default values.
2. if it performs a check that HOPR!=LOPR then what if one defines an upper limit (but does not need a low one) and vice-versa.

Thanks
Lana




Replies:
Re: DRVL, DRVH, HOPR, LOPR Kasemir, Kay
RE: DRVL, DRVH, HOPR, LOPR Dalesio, Leo
References:
mvme6100 HW issues? Vesna Samardzic-Boban

Navigate by Date:
Prev: Re: mvme6100 HW issues? chris.colborne
Next: Re: std_R3_1 Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022 
Navigate by Thread:
Prev: mvme6100 HW issues? Vesna Samardzic-Boban
Next: Re: DRVL, DRVH, HOPR, LOPR Kasemir, Kay
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·