INDI Library: 1.2.0
Code $Rev$. Protocol 1.7.
Daily packages from download pages for Raspberry Pi, latest packages from Jasem's PPA for Desktop, Atik drivers from cloudmakers.eu

kstars-bleeding 5:16.04+r5978.2606~ubuntu16.04.1 amd64 from Jasem's PPA

Kernel: 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

In the latest version of kstars-bleeding, Ekos seems to fail to download images from the Atik 314L. When taking a preview exposure, Ekos shows

2016-08-31T09:54:21 Capturing image...
2016-08-31T09:54:21 Restarting capture attempt #1
2016-08-31T09:54:21 Capture failed.
2016-08-31T09:54:15 Capturing image...

in the CCD tab and doesn't show an image.
In the Focus tab, it shows

2016-08-31T09:55:11 FITS image failed to load, aborting...
2016-08-31T09:55:06 Capturing image...
2016-08-31T09:54:12 Idle.

Everything works fine with other capture applications like ccdciel and atik_ccd_test passes with an OK. The issue occurs when connecting to the 1.1 atik driver on a Raspberry Pi but also when connecting locally to the 1.4 driver on a desktop pc. The same issue occurs on two different machines (32-bit notebook and 64-bit desktop) with kstars-bleeding 5:16.04+r5978.2606~ubuntu16.04.1.

Attached you find the verbose Kstars-log and the output of atik_ccd_test.

From the log it appears the Atik is not producing a valid FITS file, will check with Peter

Adam, do you have enough space on filesystem where /tmp is located?
Can you try it one more time and check, if temporary file is malformed or doesn't exists at all? I mean file mentioned in messages like this:

2016-08-31T09:43:03.376 - DEBG - "Could not open file /tmp/fitswZ7228. Error second keyword not BITPIX"

Peter

Yes, there is definitely enough space. The fits file is there but indeed seems to be corrupt, I can not open it with any astroimaging application. I am now getting the same error with all my cameras and also the ccd simulator when running them on the Raspberry Pi. When running the drivers locally, only the Atik produces corrupt fits files.

Can you share one of these corrupted files?

The main difference between Atik and other drivers is, that as far as it is closed source, it is linked statically with some particular version of INDI, but both versions 1.1 and 1.4 are available for a long time, used by lot of people and this kind of issues was never reported, so it is definitely some local or OS related problem. Now we have to find out what's wrong

Peter

Yes, here is a Google Drive link:
drive.google.com/open?id=0B9Zkw3NH6y1AZXVrSU9vcGZma1U

That's really strange as the Atik worked perfectly with the Pi until some days ago. Yesterday, I tried to install the 1.4 atik driver on my desktop and had to follow this:
www.indilib.org/forum/ccds-dslrs/1270-in...shared-lib.html#8353
to make it work somehow. I don't understand however, how that affects the Pi, as I didn't make any changes there.

I confirm this issue with Atik 460EX. Ihave not updated atik driver but have just updated KStars and INDI to the latest version.
As the result I get:

The file looks like FITS image with header partially overwritten by some random binary data.

Driver shouldn't be sensitive to INDI version, it is statically linked. I suspect it may be related to some unsuccessful attempt to plate-solve the image. I don't know Ekos, is it possible? Peter

It is not atik driver version specific but is somehow related to atik driver because images captured by ZWO driver work just fine.
You will not get proper fits from Atik neither from Ekos nor INDI driver control panel itself. It is a critical bug which renders focusing, ccd imaging or any other functionality related to capturing image impossible.

Something in new INDI or Ekos breaks driver dependencies. I tried it just now and it still does work on my linux images (with control panel). It is statically linked to INDI, but not to libcfitsio. Is it possible, that it was updated as a side effect of Ekos update?

This is list of driver dependencies:

polakovic@wheezy64:~/indi-atik$ ldd indi_atik_ccd
linux-vdso.so.1 => (0x00007fffe67ff000)
libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007f1b2ffbe000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f1b2fda7000)
libcfitsio.so.3 => /usr/lib/x86_64-linux-gnu/libcfitsio.so.3 (0x00007f1b2f9e1000)
libnova-0.14.so.0 => /usr/lib/x86_64-linux-gnu/libnova-0.14.so.0 (0x00007f1b2f45e000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1b2f157000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1b2eed4000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1b2ecbe000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1b2eaa2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1b2e717000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f1b2e50f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f1b301d7000)

I just set up my Raspberry Pi and my Desktop OS from scratch. That solved the problem concerning other cameras and the ccd simulator, the Atik camera however still produces the same error.

Wait a minute, I'll build atik driver against recent INDI for RPi...