Hello, could it be due to the "DEC motor to the left/right"?
I have an heq5-pro so that DEC motor part does not apply for me. Sorry I don't have the answer to your question.
My Atik camera is on its way back, nothing wrong was found with it. In perfect working order.
The team at AtikCameras is extremely friendly and patient. A very good company.
I have tried the camera on my Windows machine (I hate Windows), same nothing coming out. I will let Atik run all the tests they can do, only them will have the final say about my camera.
My Atik 314 is with Atik at the moment, they are going to check it. From what they said, they could be looking at replacing the PCB.
I must say that Atik is a very nice company to deal with. This camera is very old and they did not seem to mind that. Top marks for Atik.
It's just a bit of fun ... , an idea...
I'd like to run a little imaging competition, just for the fun of it.
This January: 30 Second Exposures unguided
Start Date: 1st January 2020
End Date: 31st January 2020
All images must be taken using Indilib.
30 seconds unguided <-- screenshot must be provided of Ekos
data captured between the challenge start and end date
1 single submission of the image, no multiple entries
Reply to this topic with your entry, with as much information as possible.
target name, imaging train, technique used etc...
I don't have this mount, but have a look at this rather large thread over on 'Cloudy Nights'
Lots of tips and tweaks to make this mount even better.
I'm taking the camera back with me and will send it to Atik for repairs.
What is the most important in the Atik driver, is it the indi-atik or the libatik?
Do they have to work in pair or can I for example use indi-atik 1.7.9 with libatik 1.8.2 ?
I have git cloned all the tags from 1.7.6 to 1.8.2 to see which one would work (work in progress)
I see for example a slight difference in the bin file libatikcameras.bin for branch 1.7.6
root@heidenrod-obs:/Astro/indi_old_branches# for x in `find . -name libatikcameras.bin` ; do ll -la $x | grep armhf; done
-rw-r--r-- 1 root root 11989452 Dec 25 23:54 ./v1.7.9/indi/3rdparty/libatik/armhf/libatikcameras.bin
-rw-r--r-- 1 root root 11989452 Dec 25 23:45 ./v1.7.8/indi/3rdparty/libatik/armhf/libatikcameras.bin
-rw-r--r-- 1 root root 10662196 Dec 25 23:58 ./v1.7.6/indi/3rdparty/libatik/armhf/libatikcameras.bin
-rw-r--r-- 1 root root 11989452 Dec 26 00:40 ./v1.7.7/indi/3rdparty/libatik/armhf/libatikcameras.bin
-rw-r--r-- 1 root root 11989452 Dec 26 00:22 ./v1.8.0/indi/3rdparty/libatik/armhf/libatikcameras.bin
-rw-r--r-- 1 root root 11989452 Dec 25 23:42 ./v1.8.1/indi/3rdparty/libatik/armhf/libatikcameras.bin
As for atik_ccd.cpp I obviously see more changes.
root@heidenrod-obs:/Astro/indi_old_branches# for x in `find . -name atik_ccd.cpp` ; do ll -la $x; done
-rw-r--r-- 1 root root 39674 Dec 25 23:54 ./v1.7.9/indi/3rdparty/indi-atik/atik_ccd.cpp
-rw-r--r-- 1 root root 39466 Dec 25 23:45 ./v1.7.8/indi/3rdparty/indi-atik/atik_ccd.cpp
-rw-r--r-- 1 root root 39454 Dec 25 23:58 ./v1.7.6/indi/3rdparty/indi-atik/atik_ccd.cpp
-rw-r--r-- 1 root root 39466 Dec 26 00:40 ./v1.7.7/indi/3rdparty/indi-atik/atik_ccd.cpp
-rw-r--r-- 1 root root 39737 Dec 26 00:22 ./v1.8.0/indi/3rdparty/indi-atik/atik_ccd.cpp
-rw-r--r-- 1 root root 39737 Dec 25 23:42 ./v1.8.1/indi/3rdparty/indi-atik/atik_ccd.cpp
I have a clear night... but the Atik is not working... back to square one...
thanks for the info. I hope this was it...
I just have to wait for later on, I might get a break in the clouds...
locked down the drivers... lol
root@heidenrod-obs:~# dpkg -l | grep atik
ii indi-atik 2.4~201911160020~ubuntu18.04.1 armhf INDI Driver for Atik cameras and filter wheels.
ii libatik 2.2.6~201911071658~ubuntu18.04.1 armhf Library for Atik Cameras.
root@heidenrod-obs:~# apt-mark hold libatik indi-atik
libatik set on hold.
indi-atik set on hold.
root@heidenrod-obs:~# dpkg --get-selections | grep hold