Dear Wouter,

Eventually got it working, thank you so much for the kind support!!!

Best, Helge

Dear Helge,

Great! So glad to have been of help. Enjoy your imaging and please share your results in the Gallery on this forum!


Clear skies, Wouter

Sorry for the really stupid question by me,,, but if I do an apt-get upgrade, will I get the new atik drivers or should I uninstall the cloudmakers one?
I've already updated but I was previously using the cloudmaker drivers (and all working great)
Thanks,
Derek

Remove any old drivers in /usr/local, it's those there that can interfere with the driver.

I have put my observatory back online, so far the Atik is behaving normally. I will test it more once and if I get a clear night this week.
Tried 1s 5s 10s and it was ok.

tbc...

I can confirm that the Atik 314 works well. I have taken countless pictures to achieve focus, not missed a bit.
Thanks

50% success for me but I am 100% positive that it is my fault.

I purchased an Atik 314E directly from Synoptics this week. It came in an Atik box but the camera is labeled "Synoptics". (I understand Synoptics and Atik are joined at the hip but that is besides the point

The camera works perfectly using Artemis on Windows. It has TEC cooling but not set-point.

First off, I use Astroberry. Secondly, I only did a "Software Update" using the Ubuntu Mate utility. I did not launch the terminal and type "sudo apt-get update", "sudo apt-get upgrade". So keep that in mind.

The Synoptics CCD is replacing my Altair CMOS camera.

First attempt to get it working under Ekos involved simply changing "Altair" to "Atik" in the dropdown list in "My Astro Gear" configuration. When I tried to connect I got the message:
Unable to establish:
+Atik
Please ensure the device is connected and powered on.

After some thought I decided to see if I could manually start indiserver with the Atik driver from the terminal:
indiserver -v indi_atik_ccd
I was expecting it to fail but it actually worked and it was waiting for a client connection!

I torpedoed it and restarted it using:
indiserver -v indi_atik_ccd indi_simulator_telescope

Then I re-entered Ekos and created a new connection called "foo" where I told it to use a "remote" connection with devices: Atik and Telescope Simulator.

Ekos connected! I now see a tab called "Synoptics USB 2.0 EF Camera (A)". I was able to snap a 1-second exposure. It worked.

One problem I see is when I go to the Ekos "CCD" tab the "Cooler On/Off" controls are disabled.

Finally, in INDI Control Panel in the General Info tab the Driver info says:
Atik
indi_atik_ccd
Version 2.2
Interface 6

Like I said, this is probably my fault. "Software Update" probably doesn't bring in bleeding edge INDI development.

Sorry for droning on and on. Thanks for any feedback.

Hi Kamisan,

In my case - and I am sure you have done already - I got it sorted by running sudo apt-get upgrade

Best, Helge

I tested the ATIK 414EX yesterday and all worked fine.

Thanks, Helge.

I have not done that only because this is Astroberry. I am awaiting a definitive answer as to what Software Update accomplishes versus sudo apt-get upgrade. Maybe they are functionally equivalent.

My reply to you last week was on a different platform: Ubuntu 16.04 laptop + my build of INDI code from Github. There I was grasping for solutions, anything to make it work. I am taking a different approach with Astroberry. I am not a Linux expert so these nuances are not intuitively obvious to me.

Perhaps Software Update brought in the latest Atik driver and everything should work but since I've got a camera that identifies itself as Synoptics there is a problem. My fallback right now is Artemis if I need to image. I'd like to get Astroberry working but it is not critical at this point.

Thanks.

To everyone who has gotten their Atik camera to work:

How does your camera identify itself on INDI Control Panel?

Mine says "Synoptics USB 2.0 EF Camera (A)"

Thanks.

Hi kamisan,

I just had a look on the astroberry side, concerning upgrade via standard procedure you would be fine (github.com/rkaczorek/astroberry-server).

In my case, there was a conflict between new Atik driver and some outdated general libraries, which was solved with the upgrade.

Best, Helge