EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024>  Index 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: pC_->doCallbacksEnum() coming too early
From: Ralph Lange via Core-talk <core-talk at aps.anl.gov>
To: EPICS Core Talk <core-talk at aps.anl.gov>
Date: Thu, 29 Feb 2024 15:50:09 +0100
On Thu, 29 Feb 2024 at 15: 10, Mark Rivers <rivers@ cars. uchicago. edu> wrote: If you only have 20 motors with 1-2 enums then I don't understand why you don't just use the current "correct" solution which does not require
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
On Thu, 29 Feb 2024 at 15:10, Mark Rivers <rivers at cars.uchicago.edu> wrote:

If you only have 20 motors with 1-2 enums then I don't understand why you don't just use the current "correct" solution which does not require a hack to do callbacks.  Just implement the readEnum method. 

What if the device is not connected at iocInit and becomes available later?

I know this is a general EPICS Base issue.
The whole approach of "initialization happens when the IOC boots" lost its appeal since the 1980s/VME. Initialization at any moment, before/during/after the IOC is up, should be the regular case. Btw. PINI is another part of that problem, which is why drivers like Stream and OPC UA have their own handling of (re)initialization.

IMHO, doing requests after connect and callbacks after the IOC is up is the "correct" solution, while implementing readEnum feels more like a hack. Which is a lot simpler and works in many cases, no doubt about that.

Cheers,
~Ralph
Replies:
Re: pC_->doCallbacksEnum() coming too early Torsten Bögershausen via Core-talk
References:
pC_->doCallbacksEnum() coming too early Torsten Bögershausen via Core-talk
Re: pC_->doCallbacksEnum() coming too early Johnson, Andrew N. via Core-talk
RE: pC_->doCallbacksEnum() coming too early Mark Rivers via Core-talk
Re: pC_->doCallbacksEnum() coming too early Ralph Lange via Core-talk
Re: pC_->doCallbacksEnum() coming too early Torsten Bögershausen via Core-talk
Re: pC_->doCallbacksEnum() coming too early Mark Rivers via Core-talk
Navigate by Date:
Prev: Re: pC_->doCallbacksEnum() coming too early Mark Rivers via Core-talk
Next: Re: pC_->doCallbacksEnum() coming too early Torsten Bögershausen via Core-talk
Index: 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: pC_->doCallbacksEnum() coming too early Mark Rivers via Core-talk
Next: Re: pC_->doCallbacksEnum() coming too early Torsten Bögershausen via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024> 
ANJ, 29 Feb 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·