Slow loopscan with Eiger2 and hw trigger
Seen on ID10.
The overhead of the scan with the Eiger2 is unacceptable. The Eiger detector is configured to use the TRIGGER
sync mode and thus the fast_synchro
and ready_for_next_trigger
provided by Lima, but it is not when start_once == True
(e.g. EXTERNAL_TRIGGER_NULTI
).