slsDetectorPackage/slsDetectorSoftware
Erik Fröjdh df40665c5e
Using a loop to stop (#585)
* loop for stop, 10 retries
  For example, if module A got a "stop" during an acquisition, it stops to an 'Idle' state. If module B gets a "stop" before an acquisition, it will return it is in 'Idle' state and continue to start the next acquisition, but module B then waits for "ready  for trigger" synchronization from module A, which it will never get. Since module B missed the asynchronous stop command, the workaround in the client is to send another "stop" command (upto 10 retries) till it returns Idle.
2022-11-25 09:55:51 +01:00
..
2021-11-22 15:08:58 +01:00
2022-11-25 09:55:51 +01:00
2021-11-25 12:26:48 +01:00