musst: prepare once, start once
TODO:
- take into account
prepare_once
- take into account
start_once
-
wait_ready
problem ; naive approach: ifstart_once
returnsTrue
- would be better to find a more suitable solution to the problem
-
Idea: emit a trigger
channel with trigger number, it could have a parameter to tell how many values are stored per trigger ; in combination with start_once=True
, it would define the "wait_trigger_id" (similar to "wait_frame_id" for Lima) - maybe a "sentinel" AcquisitionDevice
can be added to help with this, to make something more generic ; it could even be used for progress display or watchdog to detect blocked scans.
Edited by Matias Guijarro