×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Problem getting images from Atik 383L+ mono

  • Posts: 94
  • Thank you received: 8
Hi,

I'm new to Ekos and trying to understand operations. Yesterday, I set up my RPi as a server, and was controlling everything from my laptop. System is set up in my living room for basic testing. I was able to get some images from the camera indicating it was working - uncap the telescope, take an image, get weird bright out of focus picture.

Today, it seems like the camera shutter doesn't want to open. I can set the exposure to 5 seconds, which should produce a completely white image, but instead I get what looks like a bias image. Listening carefully near the camera, I can't hear any shutter action.

Just in case it's a hardware issue, I tried the camera from my Windows installation and it works just fine. Switching back to Ekos... it doesn't work.

I'm kind of wondering if I have everything set up right. In the INDI control panel for the camera, there are "Shutter - Manual open / Manual close" buttons. I don't want manual anything here. What do these buttons do?

Software details: Raspberry Pi running Raspbian - libindi updates downloaded yesterday. Ekos VM 1.6 downloaded a month ago ; all updates applied.

Thanks for your help,

Charles
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
6 years 9 months ago #17259

Please Log in or Create an account to join the conversation.

  • Posts: 94
  • Thank you received: 8
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.
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
6 years 9 months ago #17260

Please Log in or Create an account to join the conversation.

  • Posts: 472
  • Thank you received: 165
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.
6 years 9 months ago #17265

Please Log in or Create an account to join the conversation.

  • Posts: 94
  • Thank you received: 8
Thanks. I'll give that a try next time I have time to get this running.
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
6 years 9 months ago #17274

Please Log in or Create an account to join the conversation.

  • Posts: 94
  • Thank you received: 8
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
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
6 years 9 months ago #17337

Please Log in or Create an account to join the conversation.

  • Posts: 456
  • Thank you received: 76
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
6 years 9 months ago #17338

Please Log in or Create an account to join the conversation.

  • Posts: 472
  • Thank you received: 165
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 :)
6 years 9 months ago #17343

Please Log in or Create an account to join the conversation.

  • Posts: 64
  • Thank you received: 2
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
6 years 7 months ago #18434

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174
Sorry, I missed this thread, I'll check what's wrong. Peter
6 years 7 months ago #18821

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174
Pls. can you try version 1.24? Peter

www.cloudmakers.eu/atikdrivers/
The following user(s) said Thank You: Jasem Mutlaq, Thomas Seckler
6 years 7 months ago #18827

Please Log in or Create an account to join the conversation.

  • Posts: 64
  • Thank you received: 2
After the upgrade, the issue is gone. Thanks!
Question: how come that the indilib package does not ship the latest driver version?

Regards,
Florian
6 years 7 months ago #18831

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174
Probably because ATIK driver is not opensource. Peter
6 years 7 months ago #18835

Please Log in or Create an account to join the conversation.

Time to create page: 0.726 seconds