Problem
The sequence is executed by a synchronous function of the AcquisitionControl which return the AcquisitionData.
At the moment, the execution cannot be aborted by the user in a controlled way.
The only option is to cancel the program.
However, it has been observed that the card continues to replay the sequence.
This is due to the sequence data which remains in the card memory.
Idea
The idea is to implement an abort function which guarantees a controlled stop of a running sequence execution.
This could be achieved by asynchronous execution.
The sequence could be started in a thread such that the user has the option to cancel the execution.
Problem
The sequence is executed by a synchronous function of the
AcquisitionControlwhich return theAcquisitionData.At the moment, the execution cannot be aborted by the user in a controlled way.
The only option is to cancel the program.
However, it has been observed that the card continues to replay the sequence.
This is due to the sequence data which remains in the card memory.
Idea
The idea is to implement an abort function which guarantees a controlled stop of a running sequence execution.
This could be achieved by asynchronous execution.
The sequence could be started in a thread such that the user has the option to cancel the execution.