RE: Changing runtime limits with Channel Access

[Alessandra Palazzo via Tech-talk <tech-talk at aps.anl.gov>]

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