Hi Friends,

i like to run the Atik EFW3 besides the EFW2.
Running dmesg shows me different device Ids. But text info shows EFW2 instead of EF3 for the second filterwheel.
The kstars device manager only shows up one device. On command line (-v Option) two devices where recognized.
I search through the web, but could not find any solution yet.
Is there a chance to read out the usb device id in the driver and than to identify if there is EFW3?
Or is there a chance to go beyond in the sourcecode of the libatik to handle EFW3 identification.
Where can i get the source code of the libatik library to have a closer look?
Many thanks in advance and kindest regards,
Gerrit

Add:

Found the libatik code.
Is it just to add

enum ARTEMISEFWTYPE
{
ARTEMIS_EFW1 = 1,
ARTEMIS_EFW2 = 2,
ARTEMIS_EFW3 = 3 // this one??
};


And in the INDI_atik_wheel driver:

const char *fwName = (type == ARTEMIS_EFW1) ? "EFW1": "EFW2";

turn into switch Statement?

Error found. Missing USB cable O:) But the naming of the EFW3 is EFW2_2. So may be , my idea is a solution to show the right deviceid.
Right?
Regards,
Gerrit

Last week I wrote:
Thank you, Kaczorek, for your reply.

Here is some additional info that I learned from the seller, Synoptics LTD. Synoptics and Atik are related corporate entities. The gentleman with whom I have been working says that the camera has been validated for use under Windows with their drivers but obviously they would like to know if it works under Linux. The Windows driver reports the camera as "Synoptics", not "Atik" or "Artemis".

Does anyone see any red flags here? I guess the real test is to buy it and try it, and if it doesn't work with INDI then use it with a Windows capture program

Thank you.

EDIT: A friend uses the same camera from the same seller with AstroDMX on Debian Linux with drivers from Cloudmakers. This is a good sign. I am moving forward with the purchase.

Hi,

just tried connecting to new ATIK Horizon, but INDI driver keeps crashing when starting up. I have done all the updates, also run "sudo apt-get install indi-atik" as well as libatik. Not sure if that was necessary. The log file says something about a "child process died".

Can anyone help?

Many thanks, Helge

Hi Helge,

Sorry I can't fix your problem but I can relay my similar experience with Altair cams. In my case the indiserver build was looking for a library named 'libaltaircam' in a directory named '/usr/local/lib/'. There was no such library there. It was located in '/usr/lib/x86_64_linux_gnu/'. indiserver failed in the exact sequence shown in your attached log file. I am sure the guys and gals at INDI will get to the bottom of it!

Hi kamisan,

Thanks a lot for sharing your experience - did you find a kind of workaround, like symlink - not sure how to write out correctly (maybe something like „ln -s /usr/lib/x86_64_linux_gnu /usr/local/lib“)

Best, Helge

Just had a look - also in my case the libatik libs are at the mentioned location (x86_64_linux_gnu-folder). Maybe it has to do with the fact that I am having the indiserver on a miniPC, and not a Raspberry Pi, thus the location differs?

Does it work if you create a symbolic link from the driver in /usr/lib/x86_64_linux_gnu to the /usr/local/lib directory? It can be created with

sudo ln -s /usr/lib/x86_64_linux_gnu/libaltaircam.so /usr/local/lib


HTH, Wouter

Hi Wouter,

Unfortunately, no success (yet): I tried the "symlink", slightly modified, as there are quite a few atik-libs (see also attached screenshot. So I put in as follows:

sudo ln -s /usr/lib/x86_64_linux_gnu/libatik*.* /usr/local/lib

hope that modification did not make things worse. There are also some libs that sound similar, so I repeated the symlink for them as well: sudo ln -s /usr/lib/x86_64_linux_gnu/libatk*.* /usr/local/lib .

Best, Helge

Hi Helge,

Sorry, I should have given you some more background info on those drivers and on how symlinks work on linux. When you issue this ls statement then you can see that all but one atik drivers are in fact symlinks to this one driver file:

$> ls -al /usr/lib/x86_64-linux-gnu/libatik*
lrwxrwxrwx 1 root root 19 Mar 9 14:46 /usr/lib/x86_64-linux-gnu/libatikcameras.so -> libatikcameras.so.2
lrwxrwxrwx 1 root root 23 Mar 9 14:46 /usr/lib/x86_64-linux-gnu/libatikcameras.so.2 -> libatikcameras.so.2.2.5
-rw-r--r-- 1 root root 4247608 Mar 9 14:46 /usr/lib/x86_64-linux-gnu/libatikcameras.so.2.2.5
lrwxrwxrwx 1 root root 12 Mar 9 14:46 /usr/lib/x86_64-linux-gnu/libatik.so -> libatik.so.2

The arrows, denoted by "->" mean it is a symlink. So in fact the only symlink needed is to the /usr/lib/x86_64-linux-gnu/libatikcameras.so.2.2.5 file. HOWEVER the filename will change with future updates of the driver and that is why the other symlinks exist.

I executed your symlink command and this is the result:

$> sudo ln -s /usr/lib/x86_64_linux_gnu/libatik*.* /usr/local/lib
$> ls -al /usr/local/lib/libatik\*.\*
lrwxrwxrwx 1 root root 36 Apr 5 18:21 '/usr/local/lib/libatik*.*' -> '/usr/lib/x86_64_linux_gnu/libatik*.*'

So you in fact created a symlink to a non-existent file and that is why it still doesn't work.

In short, please execute the symlink command as I stated before:

sudo ln -s /usr/lib/x86_64_linux_gnu/libaltaircam.so /usr/local/lib

and it should work. Actually you'll need to delete the old symlink with

sudo rm /usr/local/lib/libatik\*.\*

Note the two back slashes which are ESSENTIAL to make the command work!!!!

Please also note that with every update of the atik driver you will need to check if the symlink still points to an existing file. If it doesn't and you don't check, you will notice because you return to the same problems

The atik driver maintainer (is that Atik themselves?) should adhere t the INDI standard that the drivers should be in /usr/local/lib OR should add a command to automatically create the symlink when installing the package and actually remove the old one when upgrading the package. fortunately the way apt and dpkg work on Debian based Linux distributions, of which Ubuntu is one, makes this very well possible and actually easy to implement.

Let me know please if it works once you have done all of this


CS, Wouter

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