our (CloudMakers) INDI driver definitely worked with Atik One (I have one) and to some extent worked with Atik GP (I have one as well). If it is detected but can't be connected, maybe USB rules script failed for some reason. Check permissions for device created for the camera in /dev/bus/usb/something... You can use lsusb command to find which one is it.
Atik GP is actually PointGrey Chameleon camera and only basic IIDC modes are supported by INDI driver, what limits e.g. available resolutions or framerates. If you want full support, you need to use INDIGO IIDC driver, but it will not work for you out of the box because of design flaw in Ekos. Camera reports itself correctly as PointGrey Chameleon and not as CCD IIDC as supposed by Ekos. But it should work, if you will run Atik and IIDC drivers in separate INDIGO server instead of built in INDI server. It will be also faster, because you will save one interprocess boundary.
"Atik" is the newer INDI driver built on Atik SDK. Regarding the Atik filter wheel, I just tested it and it works just fine, including saving filter names. . Which driver are you selecting for that? Make sure it's "Atik EFW".
thanks for the quick reply. First I wasn't using any driver for the filter wheel, since it is included in the Atik One. However, when I select "Atik EFW" as filter wheel I get a message from Indi Server saying "No Atik filter wheels detected. Power on?". Any idea what I am doing wrong? Also any clue why the Atik GP guider camera doesn't even show up in the INDI Control Panel?
Ah built it FW. Okay, I can't test that but I think I fixed the issue from the description of your bug report. The change will be in tomorrow's nightly build (check
for how to enable nightly PPA).
Regarding Atik GP, I just emailed Atik to see what they have to say about that. But As Peter said above, you might need a different driver for it. At any rate, let's wait for Atik official response on this.
Thanks for the effort. I will check the nightly build tomorrow and see how it works. I also tried using the indigo server. All connected devices (CCD, built in FW and Guider) show up in the Web Interface. But how do I get Ekos to use the indigo instead of the INDI drivers?
I‘m looking forward to hear what Atik‘s official reply is.
Or you could try just manually writing the name of the indigo driver into the corresponding ekos profile box, and it will find them as they are located in same folder as INdI drivers, that may work..
Stellarmate OS on Raspberry pi4b
Skywatcher EQ8 pro, on steel pier
Takahashi FSQ85, FS60cb & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar x2 Guide Camera
Pegasus Ultimate Hub V2 for all USB & Power
Pegasus focus motors on all scopes
Thanks to Peter and AstroNerd for the help. I managed to start Ekos using the INDIGO drivers for the Atik One CCD and Atik GP. Both cameras work and the filter wheel is behaving correctly. However, I am still running into problems:
1) The guiding section of Ekos doesn't show up. Is the GP not recognised as a guiding camera (using indigo_ccd_iidc driver)? Do I need another driver?
2) The Align section (I used the INDIGO Telescope Simulator for now) won't work. I would like to use the EqMod telescope driver with a synscan mount but there doesn't seem to be (a stable) one in INDIGO. Can you run INDI EqMod and INDIGO CCD drivers side by side? If so, how?
Jasem, I tested the INDI Atik driver in the nightly build. The 2nd filter wheel position is not skipped anymore. However, now KStars crashes when I try to change the filter wheel position from position 5. The filter names still cannot be changed. I get [ERROR] Error updating names of filters. after hitting Set in the INDI Control Panel.
INIDGO, unlike INDI, creates different devices for different purposes. You will probably find "Atik GP" device for camera itself and "Atik GP (guider)" for its guiding port, you can use them independently. You need to select first one as camera and second one as guider in Ekos. The same apply for "Atik One" and "Atik One (wheel)", there are two independent logical device too for a single physical unit.
SynScan driver (and also alignment model) made a huge progress during last couple of weeks, but binary package is not created yet. You can either checkout INDIGO from GitHub and compile from source (github.com/indigo-astronomy/indigo) or you can run INDI EqMod driver (or any other INDI driver), just prefix it with -i switch on a command line. This instruct indigo_server to load executable instead of dynamic library and to use legacy INDI protocol. I can't recommend this approach for e.g. CCD drivers as far as legacy INDI protocol is really a disaster from performance point of view, but it doesn't matter too much for mount driver.