fix(core.Common): Use LoadConfigProcess.#1006
Conversation
|
It does seem however that the JESD lock fails repeatedly and overall it takes much longer to set all of the defaults with this process... I don't know how systematic that is, but I've observed it now on the B33 smurf and on a LAT system. |
|
@ruck314 I should do some more testing on this, but any ideas why the JESD init may be taking a lot longer / failing with this change? |
|
right now I'm observing it failing repeatedly on the JESD init: |
|
I think this will have to be re-visited once changes in the When that happens, other libraries like |
|
Another data point here: If I keep rogue exactly the same and only go back to using So it might be that the process not blocking the rogue threads or something like that is cause the inits to fail. Looks like there is PR slaclab/rogue#1259 that may be addressing this (?). |
dc0f63c to
6cfdebb
Compare
Avoids timing out on long-running command.
The default period is 1.0, which means that the update thread is not blocked while loading configuration and initialisation. This was found to cause the JESD initialisation to fail.
6cfdebb to
a10ee2b
Compare
|
This is sorted now. Pending #1011 |
Avoids timing out on long-running command.
This was often causing crashes during testing on the LAT, now that the ZMQ client will time out on long-running
Commandcalls breaking with previous behavior in rogue 4 / EPICS.Tested on the B33 smurf.