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
Me and @VroniPfann were having issues setting up Photometrics Kinetix for bulb mode. We would set_trigger(TriggerType.HIGH, TriggerMode.BULB) but it would still behave as TriggerMode.ONCE. It appears that we only support the legacy PVCam trigger modes which should not be used in the sCMOS cameras
In PVCam, exposure modes are a bunch of enums. Previously, it could be one of:
TIMED_MODE
TRIGGER_FIRST_MODE
STROBED_MODE
BULB_MODE
VARIABLE_TIMED_MODE
These are now considered legacy. Since PVCam 3.0.1 there are extended exposure modes. Instead of one of those exposure mode, PVCam now has other exposure modes that need to ORed with the new exposure out modes. The legacy modes still appear to work but just not the way we expect. I'm not sure why we see the behaviour we see but the following change fixe the issue for us:
We never check what exposure modes are actually supported by the camera. It seems we should be checking that dynamically (PVCam lets us do that) and adjust what modes we use based on that.
The text was updated successfully, but these errors were encountered:
Sounds like a sensible solution. I guess the only worry is that updates break working systems. The ones that come to mind are the Oxford systems based around older photometrics cameras like the Evolve Delta's, or even the exi Blue and green (are those the right names?) that we occasionally used in Oxford. There is also the Prime BSI that was on the AO system in engineering.
@juliomateoslangerak you mentioned you use bulb mode on a photometrics kinetix. What pvcam version are you using? And are you changing it for bulb mode?
Me and @VroniPfann were having issues setting up Photometrics Kinetix for bulb mode. We would
set_trigger(TriggerType.HIGH, TriggerMode.BULB)
but it would still behave asTriggerMode.ONCE
. It appears that we only support the legacy PVCam trigger modes which should not be used in the sCMOS camerasIn PVCam, exposure modes are a bunch of enums. Previously, it could be one of:
TIMED_MODE
TRIGGER_FIRST_MODE
STROBED_MODE
BULB_MODE
VARIABLE_TIMED_MODE
These are now considered legacy. Since PVCam 3.0.1 there are extended exposure modes. Instead of one of those exposure mode, PVCam now has other exposure modes that need to
OR
ed with the new exposure out modes. The legacy modes still appear to work but just not the way we expect. I'm not sure why we see the behaviour we see but the following change fixe the issue for us:We never check what exposure modes are actually supported by the camera. It seems we should be checking that dynamically (PVCam lets us do that) and adjust what modes we use based on that.
The text was updated successfully, but these errors were encountered: