I can add that if I capture a 300 second exposure, it looks like a dark frame. In other words, the camera is actually exposing for the right time (I assume) but not opening the shutter.

I've had similar problems for a while as well that the camera doesn't always open the shutter then taking light frames. The workaround that has worked pretty well is to take one dark frame at the beginning of the session and it usually works fine after that. Ie. set frame type to dark, take 1 second exposure, switch back to light frame type. Not ideal especially with Ekos scheduler, but better than nothing.

Thanks. I'll give that a try next time I have time to get this running.

Well I tried it and I can get the shutter to open. It seems the workaround does work. However, it would be nice to be able to control the shutter, or at least to have it work sensibly for other images.

For instance, a bias image is generally taken with the shutter closed. But Ekos doesn't do that when you select "Bias" as the type. Workaround is to set the type to Dark and change the filename accordingly, then move the images out of the "Dark" folder into the Bias folder.

This would be nice to get working. Another option would be to have a shutter control button that is another parameter in the sequencer job.

Thanks,

Charles

This is strange, I have an Atik 383L+ mono and have never experienced this with INDI/EKOS.
What version of the driver from cloudmakers are you using? I'n using 1.22

I've used pretty much every version from 1.12 to 1.23 so far, the difference might be that we are using ARM driver on Raspberry Pi and you seem to use Intel. I had similar issues with Cloudmaker's USB Focus V3 driver, which didn't work on ARM but worked fine on Intel and it looked like uninitialized variables or something as the settings were full of garbage. Could be that the frame type isn't always properly initialized on ARM so it doesn't quite work until set to a different value and back. Just a guess though

Hello,

I am experiencing the problem too.
Using ATIK 383L+ mono / Kstars+Ekos on xubuntu / INDI on Raspberry Pi.

The workaround works (taking a small dark after connecting to the device).
Should we enter some bug tracking record somewhere?

Thanks
Regards,
Florian

Sorry, I missed this thread, I'll check what's wrong. Peter

Pls. can you try version 1.24? Peter

www.cloudmakers.eu/atikdrivers/

After the upgrade, the issue is gone. Thanks!
Question: how come that the indilib package does not ship the latest driver version?

Regards,
Florian

Probably because ATIK driver is not opensource. Peter

You mean the Raspbian package? It will have the updated version tomorrow.