On 06/16, Paul Nord via Tech-talk wrote:
> Strange problem.
>
> A. I create a bunch of PV's with initial values.
> B. A little later in the code another configuration file is read for values
> and put is called.
> C. IOC is started.
> D. Some of the PV's get the correct values. Some still show init value.
>
> If I call the configure routine to set the PV's "some time" later, the load
> reliability.
>
> I can add a 30 second delay, but I've lost confidence that I can
> guarantee initialization under circumstances where processor load might
> change. It looks like the "init" value is being set some random time after
> the PV is created. Possibly even overwriting later calls to put.
>
> I'm using Python Soft IOC.
>
> Thoughts?
Where is iocInit called in your A-D sequence? Are CA links involved?
Possibly related to this?
https://epics.anl.gov/tech-talk/2012/msg02082.php
Lewis
- References:
- IOC Startup - init value used sometimes instead of put Paul Nord via Tech-talk
- Navigate by Date:
- Prev:
Re: IOC Startup - init value used sometimes instead of put Mark Rivers via Tech-talk
- Next:
Re: IOC Startup - init value used sometimes instead of put Paul Nord 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: IOC Startup - init value used sometimes instead of put Mark Rivers via Tech-talk
- Next:
No PV record found when build ASYN application on Windows shenzb--- 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
|