ASI Linux SDK 0914 beta

Sam@ZWO

here is the latest version of linux SDK

fixed 16bit output problem

included an arm version library

welcome test

http://www.zwoptical.com/software/asicamera%20linux%20sdk%200914.zip

jamesf

My capture application uses milliseconds for the exposure time, whereas I believe the exposure control uses microseconds. I multiple my values by 1000 when I call setValue().

With my ASI120MM in 16-bit mode, if I use an exposure of 36ms (so 36000 microseconds) everything works fine. But if I set an exposure time fo 35ms (35000 us) then the getImage call is very slow and returns 0 all the time.

In 8-bit mode this works fine.

Is there any obvious reason for this?

James

jamesf

I've just noticed that this problem happens at 640x480, but not at 1280x960.

James

Sam@ZWO

Hi James

there is a break to check something else when transfer in the hardware.

and the hardware is not fast enough.

so if the data size just meet the break then this will happen.

adjust the "USB Traffic" can fix it but it may move to 36 or 37ms

so there is such "dead area"

jamesf

Thank you for the explanation, Sam.

James

jamesf

Actually, there's another little oddity with this version and the previous one. It's not a big issue because it's easy to correct in my initialisation code, but I thought I'd mention it since I've noticed it.

When my ASI120MM starts, it appears to have the image vertically flipped by default. That is, the image is returned as if I had called SetMisc(0,1).

This means that if I start the camera and the my application does, say, SetMisc(1,0) and then later on SetMisc(0,0) the image doesn't return to the original orientation.

It's easily fixed just by calling SetMisc(0,0) when I first configure the camera, but it confused me for a while :)

James

Sam@ZWO

thanks James

maybe we should add it to the init procedure