You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the Sardana follow-up meeting 2021/09/23 @hardion, @HEnquist and @johanfforsberg warned that there is a possible issue between the controller and the device server. At MAXIV they experienced that the device server may have some memory problems which are not correctly notified by the device state change (it stays STANDBY). As a consequence, the controller is not able to recognize this faulty condition and tries to proceed with the measurement, causing the scan to hang.
@jairomoldes, @rhomspuron I ping you here cause at ALBA BL29 and BL22 we use this controller and we may be also affected.
In order to fix this issue, we would also need more information on how to reproduce it e.g. macro parameters? Logs from the MacroServer and Pool?
The text was updated successfully, but these errors were encountered:
On the Sardana follow-up meeting 2021/09/23 @hardion, @HEnquist and @johanfforsberg warned that there is a possible issue between the controller and the device server. At MAXIV they experienced that the device server may have some memory problems which are not correctly notified by the device state change (it stays STANDBY). As a consequence, the controller is not able to recognize this faulty condition and tries to proceed with the measurement, causing the scan to hang.
@jairomoldes, @rhomspuron I ping you here cause at ALBA BL29 and BL22 we use this controller and we may be also affected.
In order to fix this issue, we would also need more information on how to reproduce it e.g. macro parameters? Logs from the MacroServer and Pool?
The text was updated successfully, but these errors were encountered: