Open jilavsky opened 2 years ago
Weird. HDF5 plugin changes between capture and single mode while it is collecting images. But works when it is set in epics to capture, even though during exposure BS changes that to single mode. This is confusing. SAXS stays in single mode all the time.
The change we did yesterday in ordering that dictionary made WAXS detector fail today with "This is not allowed in Capture mode" message. I restarted BS to reset dictionary to old order to make sure things work when we change between spec and BS. The code needs to be more robust on what form it finds AD in and not fault when mode is something it does not expect. More development needed here... Spec requires both SAXS and WAXS detectors to be in single mode.
Note, restarted BS and now SAXS is not collected
E Tue-08:24:42 - Exception TimeoutError during attempt 1 of 1 of command '('saxsExp', ['25.2', '35.7', '1', 'AgBehenateLaB6'], 23, ' saxsExp 25.2 35.7 1 "AgBehenateLaB6"')''
subject: TimeoutError during attempt 1 of 1 of command '('saxsExp', ['25.2', '35.7', '1', 'AgBehenateLaB6'], 23, ' saxsExp 25.2 35.7 1 "AgBehenateLaB6"')''
date: 2022-04-19 08:24:42.421781
command file: /share1/USAXS_data/2022-04/usaxs.mac
line number: 23
command: ('saxsExp', ['25.2', '35.7', '1', 'AgBehenateLaB6'], 23, ' saxsExp 25.2 35.7 1 "AgBehenateLaB6"')
raw command: saxsExp 25.2 35.7 1 "AgBehenateLaB6"
attempt: 1 of 1
exception: Attempted to set EpicsSignalWithRBV(read_pv='usaxs_pilatus1:HDF1:Capture_RBV', name='saxs_det_hdf1_capture', parent='saxs_det_hdf1', value=0, timestamp=1650374672.2548933, auto_monitor=True, string=False, write_pv='usaxs_pilatus1:HDF1:Capture', limits=False, put_complete=False) to value 1 and timed out after 10 seconds. Current value is 0.
Stopping further processing of this command list.
Out[3]: :24:42 - memory report: pmem(rss=351531008, vms=4854427648, shared=66240512, text=2560000, lib=0, data=4224798720, dirty=0)
('de9f84a9-6e85-490e-b8d7-eecaccc573fb',
'5b496826-84aa-47c9-be4a-2dab67587972',
'f2a23ba5-15fa-4d7c-a162-2a6e92cc150b',
'4f017db4-35a6-42f0-acd5-9403f89a4548')
This is same issue as with WAXS detector we had. SAXS detector is set for spec in Single mode and I get now write error: capture not supported in single mode and that fails to collect data. This worked until I restarted BS. Switching back to spec, I cannot fight this many wars at the same time...
Show me the waxsdet.hdf1.stage_sigs value
On Tue, Apr 12, 2022, 9:02 AM Jan Ilavsky @.***> wrote:
Weird. HDF5 plugin changes between capture and single mode while it is collecting images. But works when it is set in epics to capture, even though during exposure BS changes that to single mode. This is confusing. SAXS stays in single mode all the time.
— Reply to this email directly, view it on GitHub https://github.com/APS-USAXS/ipython-usaxs/issues/557#issuecomment-1096771256, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARMUMDZT4JAA442O34BXCLVEV66BANCNFSM5THLGCRA . You are receiving this because you were assigned.Message ID: @.***>
Has to wait until we get the detectors up and running. I asked Nino to address move issues, current configuration is sector specific. I need them to clone old 9ID configuration to 20ID one now. Hopefully tomorrow I can start the detectors and then you can get what you need.
WAXS detector is running. When we can start BS, you can do development.
We have seen this. WAXS image not collected for some reason. Run fine in spec. Optical camera is working from epics adn save spec images. SAXS image was collected and used, but
NOTE: WAXS AD shows red: ERROR CAPTURE NOT SUPPORTED IN SINGLE MODE. we changed to single mode when WAXS could not save data in spec when it was in capture mode. When I changed to Capture model BS seems to be saving images. But now spec will not be working... SAXS detector is in single mode. Why is WAXS detector in capture mode???