I suspect you didn't download it correctly, I tried it just now on ubuntu and this is how it looks:

notroot@ubuntu:~$ sudo dpkg -i ./atikccd-0.5-i386.deb
[sudo] password for notroot:
Selecting previously unselected package atikccd.
(Reading database ... 88179 files and directories currently installed.)
Unpacking atikccd (from ./atikccd-0.5-i386.deb) ...
Setting up atikccd (0.5) ...
notroot@ubuntu:~$

It is statically linked to INDI but it still needs all INDI prerequisites to be installed:

notroot@ubuntu:/usr/bin$ ldd indi_atik_ccd
linux-gate.so.1 => (0xb77db000)
libusb-1.0.so.0 => /lib/i386-linux-gnu/libusb-1.0.so.0 (0xb77b4000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb779b000)
libcfitsio.so.3 => /usr/lib/i386-linux-gnu/libcfitsio.so.3 (0xb75bc000)
libnova-0.14.so.0 => /usr/lib/i386-linux-gnu/libnova-0.14.so.0 (0xb7260000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb7177000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb7134000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb7117000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb6f63000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb6f48000)
librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb6f3f000)
/lib/ld-linux.so.2 (0xb77dc000)

in order to remove All OS/VM dependance, I've installed a Kubuntu. Then I've installed Jasem ppa, install indi, kstars etc.

Then I've downloaded your .deb.

-> doesn't work atik_ccd_test failed.

I've change cables. I've change USB ports -> I don't know what doing more.

I can give you a ssh access to my lapto if you want.
Mail me -> ashashiwa @ the big big brother google.

Peter,

I found a big problem with Linux ATIK CCD driver. I had big "amp-glow" on the images taken with Linux driver. I thought it was due to some problem with stretch in Ekos. But it appears the problem appears in the raw data itself. I compared the picture taken with the same camera on Windows and Linux. Please see the comparison made with PixInsight (auto stretch).



The pictures are take with the same setup, both 10s long (guiding fails for me at the moment). The area covered should be close to each other:
* Linux picture solved: nova.astrometry.net/user_images/182841#annotated
* Windows picture solved: nova.astrometry.net/user_images/182839#annotated

I would assume similar images taken on both Windows and Linux. Any idea why the difference is so huge? My camera is Atik 314L (without plus)

Cheers,
milosz

Milosz, than you for your report. Driver should turn amplifier off for exposures longer than 2.5s but it seems that doesn't work for you for some reason. I will look at it. Peter

Yes. I introduced a bug when I rewrote the entire drivers for the OSX drivers from the very original windows drivers. If peter has inspected that code to produce his code base, it will have the exact same bug, although it should have been a simple case to top&tail the two classes required to port my C++ driver. The latest R1.05 has that fixed.

Peter - I can't say where it is in your code but in the original OSX drivers, it's located in ArtemisCameraIC24.cpp within the performSnapshot method, search for "EnableAmplifier(!m_cameraAmplifierActive);" and this will help you locate the problem.

Hi Nick, I'm not using original Windows driver codebase for INDI, but it is probably the same issue

No worries - I rewrote the *entire* code base into C++.. so it sounds like that C++ code base you've seen. The current C++ rewrite has been tested with all the camera in the range - including the Titan and 4000/11000 so you could use that as a basis to expand the cameras supported by INDI.

Hi Milosz, I reproduced the problem on my 383L and it is hopefully fixed. Can you download version 0.6 of the driver from INDI Resources to try it?

Peter

Hi Peter,

Thanks for so quick fix! I will check tomorrow. I guess it should be OK to try with lens cap put on during the day. I just came back home and I have to watch the beautiful clear skies with no imaging, while the forecast for tomorrow is rain

milosz

Hi Milosz, sure, you should see it on dark frames. Peter

Hi Peter,

It seems your fix works. I had 100% of cloud coverage today so I was only able to take some frames with lens cap on. There is no amp glow on the 10s dark frames. I also checked 2.4s and there is nothing noticeable. Thanks for the fix!

milosz