Adds idle status notification to data thread #45
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've had issues with Andor detectors getting stuck during multiple acquisition scans (no issue observed with older versions of the driver R2-4 ~2018).
This problem happens randomly, i.e not always for the same acquisition count, but on error it always displays the 'Acquire' flag ON with the detector status 'Idle'.
Investigating the problem in the driver with extra logs, I noticed a synchronization issue between the status thread and the data thread, where a new acquisition could be triggered by the scan-generating client before the detector status had been reset to idle.
To overcome this problem, I've tried to prevent the acquisition to complete before the detector status had been updated.
Would you please be able to have a look at it please and let me know your thoughts?
Many Thanks.