Experimental Physics and
Industrial Control System

Paul,


>  A little later in the code another configuration file is read for values and put is called.


What do you mean by "put is called"?  Is the effectively a Channel Access put?  If so, and if you were not using the Python soft IOC the answer to this would be easy.  Channel Access puts can only be done after iocInit is complete.


I am not familiar with the Python soft IOC, and I am not sure what you mean by "put", so I am not sure about the timing in that case.


Mark



________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Paul Nord via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, June 16, 2020 12:52 PM
To: EPICS tech-talk
Subject: IOC Startup - init value used sometimes instead of put

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?

Paul