Unfortunately I can't help you, but I do feel your frustrations. Have had the same kind of problem with my qhy2pro. Now I got a custom driver from qhy that works, but I dare not update indi until I get another RPI set up since there is no turning back to an old version with apt. I think it should be prioritized to allow install of all old versions of Indi, not just the latest, since updates sometimes break stuff.

Rant over, I do love Indi so thanks a lot for all the hard work

I agree "I think it should be prioritized to allow install of all old versions of Indi, not just the latest, since updates sometimes break stuff."
Right now, I need to wait 2 months until I come back here to re-align the mount. I was supposed to do it this time, but the weather hasn't been great, so when I saw a gap in the clouds... I jumped to the occasion.
If I had been able to download the previous drivers, I could have sorted out my polar alignment.

Telescope cover on? Not saying I've done that... but, yeah I've done that!!! Ok, I know nothing about your camera (I have the ZWO1600).

Want to see frustration? Check out Dylan's video:

I do not have a telescope cover, I am 100% sure the Atik issue is with the latest driver. I need to try to compile the previous ones and see how it goes.

I've just checked and I have the same atik camera files as you describe, including the red symlink. Same dates, same names.
And my ATIK 383L+ works fine.

The fact that INDI can connect, recognise the camera, and get an image indicates that the connection to the camera is working at least well enough that INDI believes it has downloaded an image and all is well.
I don't see any evidence that there is any problem with the software.
I wonder if the probem is internal to the camera.
Does the image data have noise in it?
Maybe it's a problem with the connection between the CCD and the controller in the camera.

It could be time to contact Atik or more heroic measures such as opening the camera and looking for obvious problems such as loose connections or socketed ICs with bad connections.

Happy Christmas!
Chris

I have opened up the camera to check for obvious issues, burned component, or loose wires. None.

Chris could you please let me now which firmware/API version you are running? You can get that from the "General Info" tab in the Atik tab. thanks

Appart from removing a few cobwebs and a dead insect, I've reinstalled the indi-atik and libatik packages.
I had recompiled the drivers for it, from 1.7.7 to 1.8.1 to see what works or not.

And no, I've been through a sequence of 21 images with different exposure lengths, and they all worked.
I am puzzled.

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
indi-atik hold
libatik hold
root@heidenrod-obs:~#

Driver Version 2.4, Interface 6

API version 118, firmware version 3.19
I would expect different firmware because the 383 uses a Kodak CCD while your camera uses a Sony CCD.

One thing you did was disconnect and reconnect the CCD - the white ribbon cable - and that could easily have remade a bad connection. That's exactly the sort of thing that your information suggested was the problem.

Cable and connector issues happen more often than people expect.

Chris

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...

I have a clear night... but the Atik is not working... back to square one...