Closed bisogni closed 4 years ago
This is a communication issue with the camera and/or an issue with the camera not an issue with the software.
TimeoutError: Attempted to set EpicsSignalWithRBV(read_pv='XF:02IDC-BI{Mir:3-Cam:13_U_1}HDF1:Capture_RBV', name='m3_diag_cam_hdf5_capture', parent='m3_diag_cam_hdf5', value=0, timestamp=1579033452.660428, pv_kw={}, auto_monitor=False, string=False, write_pv='XF:02IDC-BI{Mir:3-Cam:13_U_1}HDF1:Capture', limits=False, put_complete=False) to value 1 and timed out after 60 seconds. Current value is 0.
If the camera has not started to acquire after a minute there is not much we can do on the software side.
Hi Tom,
Thanks for the message. As far as I can see the camera works well, and I can correctly operate it in CSS. I of course tried to reboot it, but I still get the same error in Bluesky. I will reach out to John Sinsheimer, and let you know if he doesn’t find anything wrong from the camera/communication side. Unfortunately, I need to have this camera functional as soon as possible.
Thanks.
Valentina
From: Thomas A Caswell notifications@github.com Reply-To: NSLS-II/Bug-Reports reply@reply.github.com Date: Tuesday, January 14, 2020 at 7:30 PM To: NSLS-II/Bug-Reports Bug-Reports@noreply.github.com Cc: "Bisogni, Valentina" bisogni@bnl.gov, Author author@noreply.github.com Subject: Re: [NSLS-II/Bug-Reports] Bluesky fails to operate Prosilica Camera (#202)
This is a communication issue with the camera and/or an issue with the camera not an issue with the software.
TimeoutError: Attempted to set EpicsSignalWithRBV(read_pv='XF:02IDC-BI{Mir:3-Cam:13_U_1}HDF1:Capture_RBV', name='m3_diag_cam_hdf5_capture', parent='m3_diag_cam_hdf5', value=0, timestamp=1579033452.660428, pv_kw={}, auto_monitor=False, string=False, write_pv='XF:02IDC-BI{Mir:3-Cam:13_U_1}HDF1:Capture', limits=False, put_complete=False) to value 1 and timed out after 60 seconds. Current value is 0.
If the camera has not started to acquire after a minute there is not much we can do on the software side.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/NSLS-II/Bug-Reports/issues/202?email_source=notifications&email_token=AF2TZRX2YJK3BR5K4WT2FV3Q5ZKKRA5CNFSM4KGZCW4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6UAQY#issuecomment-574439491, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF2TZRS5LD4VWCAYVABDQCDQ5ZKKRANCNFSM4KGZCW4A.
The underlying issue is that the directories were missing and the timeout was a red herring. Closing this as we already know the AD code needs an overhaul.
Our "m3_diag_cam" has been so far enabled to be 'acquired' in Bluesky using 'count', for example. At the restart of operation as of yesterday, this command doesn't work anymore. We see the camera being staged and going into "Multiple" Image Mode, however then the timeout error comes out (see below). This camera is needed to perform standard beamline alignment, so it would be helpful to have a quick feedback on this issue, if possible.
'''' In [1]: RE(count([m3_diag_cam],num=1))
TimeoutError Traceback (most recent call last)