EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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>  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> 
<== Date ==> <== Thread ==>
Subject: RE: Changing runtime limits with Channel Access
From: Alessandra Palazzo via Tech-talk <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 21 May 2024 13:34:25 +0000

Thanks all for your replies.

Ralph: using DRVH/DRVL instead of HOPR/LOPR indeed solves my issue. Thanks!

Ulrik: please find attached a screenshot of the records I’m now using (I was previously using HOPR/LOPR as you suggested) and one of the Phoebus configuration file. Even though the issue is now solved by using DRVH/DRVL, I would still appreciate if you could tell me if there’s something else that could be improved in the logic I’m using.

Thanks,

 

Alessandra

 

Present: Mon - Tue - Wed - Thu - Fri

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Ralph Lange via Tech-talk
Sent: maandag 20 mei 2024 14:08
To: EPICS Tech Talk <tech-talk at aps.anl.gov>
Subject: Re: Changing runtime limits with Channel Access

 

Also keep in mind that the ao record has two sets of range/limits fields.

 

HOPR/LOPR - "Operating Range" - hints for clients (like Phoebus) how to display things.

DRVH/DRVL - "Drive Limits" - these limits are clipping the output value that the record will write.

 

Depending on your specific use case and application, you might want to set both to the same value, or both to different values, or only one, or only the other one. (Or none, for completeness.)

 

Cheers,
~Ralph

 

Attachment: PhoebusSettings.png
Description: PhoebusSettings.png

Attachment: EpicsDB.png
Description: EpicsDB.png

References:
Changing runtime limits with Channel Access Alessandra Palazzo via Tech-talk
Re: Changing runtime limits with Channel Access Ulrik Pedersen via Tech-talk
Re: Changing runtime limits with Channel Access Ralph Lange via Tech-talk
Navigate by Date:
Prev: Re: JavaFX Phoebus warning at run time Kasemir, Kay via Tech-talk
Next: CryoTel GT Cooler: different startup and shutdown StreamDevice protocols boj via Tech-talk
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> 
Navigate by Thread:
Prev: Re: Changing runtime limits with Channel Access Ralph Lange via Tech-talk
Next: JavaFX Phoebus warning at run time William F Badgett Jr via Tech-talk
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> 
ANJ, 23 May 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·