g+
g+ Communities
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  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
<== Date ==> <== Thread ==>

Subject: Re: DRVL, DRVH, HOPR, LOPR
From: "Kasemir, Kay" <kasemirk@ornl.gov>
To: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Wed, 1 Feb 2012 08:43:34 -0500
Hi:

On 2/1/12 08:25 , "Abadie Lana" <Lana.Abadie@iter.org> wrote:
>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.
There might not be a way to find out.

For alarm limits, you get NaN for those that are not defined.
In a future release of EPICS, that might be a way to communicate
undefined control ranges. At the same time, that might break
many existing clients.

-Kay



References:
DRVL, DRVH, HOPR, LOPR Abadie Lana

Navigate by Date:
Prev: Re: std_R3_1 Benjamin Franksen
Next: RE: DRVL, DRVH, HOPR, LOPR Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
Navigate by Thread:
Prev: DRVL, DRVH, HOPR, LOPR Abadie Lana
Next: RE: DRVL, DRVH, HOPR, LOPR Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·