×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

New INDI Atik driver - Feedback requested

  • Posts: 210
  • Thank you received: 104
Good you can restore the previous version.

I tested my 314 with the current git version on a Rpi2 and it work without problem. So it is just a matter to update the ppa with this version.
5 years 4 months ago #32710

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

  • Posts: 2255
  • Thank you received: 223
I will test this new driver at some point, but right now I cannot really mess about and waste some time. I have to re-align the mount before I leave back home.. and using the mini guider for it isn't too great so I need my Atik 314+ to work perfectly.
5 years 4 months ago #32711

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

  • Posts: 2255
  • Thank you received: 223
Here's a 60 sec taken with the Atik 314 in case someone wants to take a look at it.
This is not a jpeg, it is a fits file, had to change the extension to be able to upload it here.

File Attachment:

File Name: 314_60s.jpeg
File Size:2,829 KB
5 years 3 months ago #32779
Attachments:

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

  • Posts: 2255
  • Thank you received: 223
Attempting to compile this driver from source too. Am I missing the obvious? Do I need more coffee?

# git describe --tags
v1.7.5-174-g9d9f0478

# cd build/
# cmake -DCMAKE_INSTALL_PREFIX=/usr ..
-- The CXX compiler identification is GNU 7.3.0
-- The C compiler identification is GNU 7.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found CFITSIO 3.43: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found INDI: /usr/lib/arm-linux-gnueabihf/libindidriver.so;/usr/lib/arm-linux-gnueabihf/libindiAlignmentDriver.so (found version "1.7.6")
-- Found ZLIB: /usr/lib/arm-linux-gnueabihf/libz.so (found version "1.2.11")
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Found USB1: /usr/lib/arm-linux-gnueabihf/libusb-1.0.so (found version "1.0.21")
-- Performing Test USB1_HAS_LIBUSB_ERROR_NAME
-- Performing Test USB1_HAS_LIBUSB_ERROR_NAME - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found Atik Library: /usr/lib/arm-linux-gnueabihf/libatikcameras.so
-- Performing Test COMPATIBLE_FORTIFY_SOURCE
-- Performing Test COMPATIBLE_FORTIFY_SOURCE - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/build
#

# make
Scanning dependencies of target indi_atik_wheel
[ 25%] Building CXX object CMakeFiles/indi_atik_wheel.dir/atik_wheel.cpp.o
[ 50%] Linking CXX executable indi_atik_wheel
[ 50%] Built target indi_atik_wheel
Scanning dependencies of target indi_atik_ccd
[ 75%] Building CXX object CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o
/home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.cpp: In member function ‘virtual void ATIKCCD::debugTriggered(bool)’:
/home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.cpp:1240:9: error: ‘ArtemisSetDebugCallbackContext’ was not declared in this scope
ArtemisSetDebugCallbackContext(this, &ATIKCCD::debugCallbackHelper);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.cpp:1240:9: note: suggested alternative: ‘ArtemisSetDebugCallback’
ArtemisSetDebugCallbackContext(this, &ATIKCCD::debugCallbackHelper);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ArtemisSetDebugCallback
/home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.cpp:1242:9: error: ‘ArtemisSetDebugCallbackContext’ was not declared in this scope
ArtemisSetDebugCallbackContext(nullptr, nullptr);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.cpp:1242:9: note: suggested alternative: ‘ArtemisSetDebugCallback’
ArtemisSetDebugCallbackContext(nullptr, nullptr);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ArtemisSetDebugCallback
CMakeFiles/indi_atik_ccd.dir/build.make:62: recipe for target 'CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o' failed
make[2]: *** [CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o] Error 1
CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/indi_atik_ccd.dir/all' failed
make[1]: *** [CMakeFiles/indi_atik_ccd.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2
#
5 years 3 months ago #32806

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

  • Posts: 474
  • Thank you received: 168
You need to build and install libatik directory first, you currently have older version which doesn't yet have those debug callbacks.
The following user(s) said Thank You: Gonzothegreat
5 years 3 months ago #32807

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

  • Posts: 2255
  • Thank you received: 223
thanks


# make
[ 50%] Built target indi_atik_wheel
[ 75%] Building CXX object CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o
In file included from /usr/include/c++/7/vector:69:0,
from /usr/include/libindi/indifilterinterface.h:24,
from /home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.h:26,
from /home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.cpp:22:
/usr/include/c++/7/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const double&}; _Tp = double; _Alloc = std::allocator<double>]’:
/usr/include/c++/7/bits/vector.tcc:394:7: note: parameter passing for argument of type ‘std::vector<double>::iterator {aka __gnu_cxx::__normal_iterator<double*, std::vector<double> >}’ changed in GCC 7.1
vector<_Tp, _Alloc>::
^~~~~~~~~~~~~~~~~~~
In file included from /usr/include/c++/7/vector:64:0,
from /usr/include/libindi/indifilterinterface.h:24,
from /home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.h:26,
from /home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/atik_ccd.cpp:22:
/usr/include/c++/7/bits/stl_vector.h: In member function ‘virtual bool ATIKCCD::ISNewNumber(const char*, const char*, double*, char**, int)’:
/usr/include/c++/7/bits/stl_vector.h:948:21: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<double*, std::vector<double> >’ changed in GCC 7.1
_M_realloc_insert(end(), __x);
~~~~~~~~~~~~~~~~~^~~~~~~~~~~~
[100%] Linking CXX executable indi_atik_ccd
[100%] Built target indi_atik_ccd
root@heidenrod-obs:/home/heidenrod/indi-drivers/indi/3rdparty/indi-atik/build# make install
[ 50%] Built target indi_atik_wheel
[100%] Built target indi_atik_ccd
Install the project...
-- Install configuration: ""
-- Installing: /usr/bin/indi_atik_ccd
-- Installing: /usr/bin/indi_atik_wheel
-- Installing: /usr/share/indi/indi_atik.xml
5 years 3 months ago #32810

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

  • Posts: 2255
  • Thank you received: 223
I am trying to understand something, as the newly compiled version is available over PPA, I have installed it and noticed something interesting.

let's remove it first:
# apt-get remove libatik indi-atik indi-full
# cd /usr/lib/arm-linux-gnueabihf/
# ll libatik*
ls: cannot access 'libatik*': No such file or directory

let's install it:
# apt-get install indi-atik libatik indi-full
# ll libatik*
lrwxrwxrwx 1 root root 12 Dec 20 11:59 libatik.so -> libatik.so.2
lrwxrwxrwx 1 root root 16 Dec 20 11:59 libatik.so.2 -> libatik.so.2.1.0
lrwxrwxrwx 1 root root 19 Dec 20 11:59 libatikcameras.so -> libatikcameras.so.2
lrwxrwxrwx 1 root root 23 Dec 20 11:59 libatikcameras.so.2 -> libatikcameras.so.2.1.0
-rw-r--r-- 1 root root 2928940 Dec 20 11:59 libatikcameras.so.2.1.0


Why do I have two broken symlinks???
5 years 3 months ago #32847

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

You probably had the previous driver from Cloudmakers install. Purge everything atik* or libatik* and reinstall again.
5 years 3 months ago #32878

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

  • Posts: 2255
  • Thank you received: 223
I do not have the CloudMaker one installed, I did purge it the other day.

root@heidenrod-obs:~# dpkg -l | grep atik
ii indi-atik 2.0~201811230011~ubuntu18.04.1 armhf INDI Driver for Atik cameras and filter wheels.
ii libatik 2.1.0~201812201059~ubuntu18.04.1 armhf Library for Atik Cameras.
root@heidenrod-obs:~#
The following user(s) said Thank You: Jasem Mutlaq
5 years 3 months ago #32887

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

  • Posts: 31
  • Thank you received: 1
Hi,

I'm a physics teacher and I'm setting up an observatory at my school. We have an Atik One 6.0 CCD camera with an Atik GP guider camera. I would like to run all of it with Ekos under Ubuntu 18.04. I am using KStars 3.00 and the new ATIK drivers (Version 2.1).

I have run into the following problems trying to run the camera and the guider:

1) Atik One 6.0 connects but the following problems occur:
- I can't set the filter names permanently
- changing from filter position 1 to 2 does not move the filter wheel / a subsequent change from filter position 2 to 3 (in Ekos) moves the filter number 2 in front of the sensor and so on ... I can never reach filter position 5
2) Atik GP guider camera doesn't even show up in the INDI Control Panel
3) I can choose between "Atik" and "ATIK CCD" in the Profile Editor and don't know the difference (if there is any)

Using the cloudmaker Atik driver changes the filter problem but the guider shows up in the INDI control panel but never connects.

I'm grateful for any help on this since I would like to start observing with my students soon and have to switch to Artemis Software under Windows, if I don't get this to run under Ekos. And who would want that? ;)

Cheers,
Simon
5 years 3 months ago #33490

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

  • Posts: 712
  • Thank you received: 174
Hi Simon,

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.

Peter
The following user(s) said Thank You: Simon
5 years 3 months ago #33493

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

Hello Simon,

"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".
5 years 3 months ago #33494

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

Time to create page: 0.578 seconds