You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we noticed that when motion setpoints was running alongside autoparamhandler, autoparamhandler was snatching all asyn callbacks but not checking whether or not it should be acting on them.
We added ISISComputingGroup/autoparamDriver@115c065 as a workaround, but there are still issues with this approach ie this will not work if there are 2 or more autoparamhandler instances as they'll act upon each others callbacks as the driver check will still pass.
This is an unlikely scenario, but as we have had some success with adsDriver/AutoParamHandler we should fix it.
The text was updated successfully, but these errors were encountered:
https://github.com/Cosylab/autoparamDriver/tree/stfc-integration the changes which check instance do fix this issue I believe. ONly issue is our version of epics base does not have makeAPIHeader.pl for the api header generation, so needs to be able to be backwards compatible with versions before epics v7.0.4
the above is to revert the patch we made, then apply the latest updates from the vendor which fix the issue permanently.
To review and test, checkout NDXSANDALS for example as it has motion setpoints loaded in by TC_01 (which is what was crashing the ioc before our patch), cd to C:\Instrument\Apps\EPICS\ioc\master\TC\iocBoot\iocTC-IOC-01 and run runIOC.bat and just check that you get to an IOC terminal. No need to actually connect to a real PLC here as the motion setpoints asyn callbacks should still happen and crash if this change does not work.
we noticed that when motion setpoints was running alongside autoparamhandler, autoparamhandler was snatching all asyn callbacks but not checking whether or not it should be acting on them.
We added ISISComputingGroup/autoparamDriver@115c065 as a workaround, but there are still issues with this approach ie this will not work if there are 2 or more autoparamhandler instances as they'll act upon each others callbacks as the driver check will still pass.
This is an unlikely scenario, but as we have had some success with adsDriver/AutoParamHandler we should fix it.
The text was updated successfully, but these errors were encountered: