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:
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:
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.
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.
I was so hopeful that the official release that came through at 3am my time would surely fix the problem with not recognizing my Atik/Synoptics camera. No such luck. Rumor has it that someone has this same camera working on AstroDMx. I'll contact them to hopefully duplicate their success. In the meantime under Windows, Artemis Capture works as well as SharpCap using the camera's ASCOM driver.
One last ditch effort to get this camera working under INDI:
I uninstalled indi_atik and libatik on my Astroberry and then installed Cloudmakers' driver for ARMHF (V6+) Debian Linux or Raspbian (atikccd-1.30-armhf.deb). Installation was successful.
In Ekos I tried both local and remote. 'local' gave me the same old negative response. Then I tried 'remote' by starting indiserver from the command line. It was successful but only to the extent that INDI control panel says the camera is an "Atik 314E" but it stays disconnected. I tried clicking the "connect" button but it immediately disconnects.
A friend has this same camera that he purchased from Synoptics six months ago. Cloudmakers driver works for him using AstroDMx. I bought this camera last week. The best I can figure, Synoptics reflashed the firmware to only allow access by *authorized* applications like Artemis Capture.
Caveat emptor. If they can do this to someone like me who wants to try out a new technology without dropping $2000 into a new model then what prevents them from deactivating your camera after say 2 years, now that they control the SDK?
Have all the issues connecting Atik cameras and filter wheels been solved? Not for me, and was hoping to get some on what's going on with my setup.
I have the Atik EFW 2.2 that Ekos won't recognize no matter what I do (throws the generic "No Atik filter wheels connected, power on?" message). Here's my setup:
- RPI 4 running latest StellarMate version & latest stable Indi library
- Remote connection to RPI 4 using Mac OS Mojave
- Main CCD is Atik 383l+
- Pegasus focus Cube
- Losmandy G11 gemini 2 mount
- QHY guiding camera with Orion mini 50 scope
- All hardware is powered & connected through UPBv2
Everything is working flawlessly except for the dam Filter wheel. I've tried connecting it directly to RPI4, tried connecting locally by remoting into RPI4 and controlling ekos from there (tried just connecting the filter wheel by itself). I tried every usb port on the UPBv2 and RPI 4, tried different cables and a different power source. Also tried connecting it through Atik's software on a windows laptop and it worked just fine. So frustrating since tonight is a perfectly clear sky and I'm scrambling to get it set up, but will have to just control the filter wheel directly/without StellarMate. So much for automation :-/
Can anyone please help?!! Thanks.
Indi library 1.8.6