Closed jilavsky closed 3 years ago
@jilavsky : Was the blackfly_optical
camera IOC just started? This looks like the usual report from ophyd when trying to trigger an area detector IOC when the plugin has not already received at least one image with the current configuration. (The so-called plugin warmup).
Can you report the value of blackfly_optical.jpeg1.stage_sigs
? (It's a dictionary.)
Or, the stage_sigs are specifying a configuration that the Capture value cannot accept. One way to diagnose is (from the command-line), stage the detector and then inspect the configuration with the GUI screens. Once satisfied that configuration correct, press Acquire
to take an image. Don't forget to unstage when done.
blackfly_optical.stage()
# 1. check the GUI screens for correct values
# 2. press Acquire in the GUI
# 3. check for image on disk
blackfly_optical.unstage()
I collected some data using spec and there it worked. Now it works in BS also. Looks like initialization from epics (without enabling jpg writer) is not good enough, spec enabled jpg writer, wrote image and disabled it. After this seems BS is working fine also. This initialization is nightmare. I have used the epics interface to find focus of the camera, it was collecting hundreds of images before I settled on focus and exposure. Yet, even after this, BS has initialization problem. This needs better solution on BS side, it cannot be this picky. This is not usable for standard APS staff... I suggest to play with this on this camera after next Monday and finding solution for all AD BS code.
What you request is that BS do the same initialization steps as done by SPEC. The problem is with area detector and how picky it is.
As requested,
Can you report the value of
blackfly_optical.jpeg1.stage_sigs
? (It's a dictionary.)
works now. Not sure why, but OK.
Nothing happens when trying. this is error message
It is working manually from epics screen. I had to enable jpeg plugin and set to autosave, after which it saved image as expected.