ASI1600: API calls fail on USB3

brownbear

I'm using latest ASI windows SDK for snap mode capture with my ASI1600:

setroiformat(..) => startexposure(..) => stopexposure(..) when exposure_status != "working" => GetImageData(..)

and it works perfect as long as camera is connected to USB2 port

As soon as I plug it into USB3 code seems to work fine (errc is 0 on all API calls) until last step, where i get either ASI_ERROR_TIMEOUT from GetImageData(..) or ASI_EXP_FAILED from ASIGetExpStatus(..) if I choose to check it first.

Changed PCs, changed cameras, changed cables.

Tried all possible camera settings, explicitly defining every single parameter that might be remotely relevant with ASISetControlValue.

Still getting same picture: works fine on USB2 and ASI_EXP_FAILED on USB3

Any tips how to overcome this? I need my devices working in snap mode on USB3 ports.

chad

There seems to be a problem with your calling order。

Note that Stop should be called after the data is obtained. When you set the exposure time, and start the snap, you should wait for the data. Only when you want to exit, you should call the stop.

Please refer to our demo.

the SnapThr() function.

Thanks

Chad

brownbear

Thanks for your reply!

Saldy, removing StopExposure makes no difference for the case.

checked SnapThr() and found it matching my logic perfectly, which using python wrapper looks like this:


self._APIcall(self._ASISetROIFormat, (camProps.CameraID, currentWidth, currentHeight, cfg_bining, cfg_imgType.value)) 
self._APIcall(self._ASISetControlValue, (camProps.CameraID, ASI_CONTROL_TYPE.ASI_EXPOSURE.value, cfg_exposure)) 
while self._ASIGetExpStatus(camID).value == ASI_EXPOSURE_STATUS.ASI_EXP_WORKING.value: 
    pass
if self._ASIGetExpStatus(camID).value == ASI_EXPOSURE_STATUS.ASI_EXP_SUCCESS.value: 
    errc, imgByteArray = self._ASIGetImageData(camID, imgByteArraySize)

still always get ASI_EXPOSURE_STATUS = 3 on USB3 and ASI_EXPOSURE_STATUS = 0 on USB2 after looping though ASI_EXPOSURE_STATUS==working check for configured exposure duration

Thinking of workaround with Start/StopVideoCapture , which is kinda silly for single long exposure shot.

chad

Hi,

Please try to adjust the USB Bandwidth Overload.

Beside, you can try to use the demo first. In this way, you can avoid the problem caused by settings.

Thanks

Chad

brownbear

BANDWIDTHOVERLOAD did the trick, thanks!

Don't know how I missed this setting in a first place; should've been first thing to try.

chad

It's my pleasure～

Thanks

Chad