I use yesterday for the first time this new driver. It is very good to have a free driver for atik.
I schedule poses of 300s.
The images stops after 30 exposures (But it was time to sleep).
I don't now why, I will look at the logs.
Anyway, it is a good news to have a free atik driver.
There is a fundamental and very important difference between free and open source software. Contributing new features or fixes directly is not possible in close source case, so it's all pending on the sole author, all you can do is report issues and wishes and hope for the best. When the author stops supporting the driver, it works as long as the environment happens to be similar and so on. Before this I used Peter's driver for a couple of years and it mostly worked (and I reported the issues I had) but had issues with old libraries being required and so on, which would have been trivial to fix had it been open sourced, but couldn't in a fixed binary release that would need to work on multiple OS versions.
There was a similar situation with Peter's USB_FocusV3 driver which for some reason wasn't open sourced unlike many of his other drivers (for example SX driver I also use), and never worked correctly in Raspberry Pi due to compiler issues so I wrote my own (by coincidence there was another driver written for it around the same time which was more polished so that one is included in INDI and I dropped my own version and improved that one instead, another good thing about open source).
One technical improvement is that this new driver uses Atik's own SDK (as does Peter's new open source INDIGO driver, but his old INDI driver did not) which should make it easier to support new camera models and benefits from fixes and features Atik makes for their Windows drivers and so on.
So while I'm very grateful for Peter's work I'm also very happy about this open source driver.
I of course understand these differences... and fully understand your points (& in general agree)... Although not a C++ programmer, I managed to write a focuser driver and decided to pass it onto here as a contribution.
But surely some of the issues and/or difficulties being experienced now might have been avoided if a collaboration was attempted at the start?
As far as I know Jasem did talk with Peter multiple times about this but there was some IPR issue with the camera SDK used. But this is just my recollection from discussions with Jasem, so it would be better if either of them commented directly.
As far as these current difficulties are concerned, at least the ones I fixed (temperature reading while downloading image and abort flushing) had more to do with the Atik SDK which the old driver doesn't use so while it would have obviously been good to have more collaboration, it might not have made much difference. All in all I was actually very pleasantly surprised how well the driver worked already in its initial version and have been using it ever since, but it could also just be that working as a programmer I'm probably more pessimistic about software in general than usual
So I have installed this new driver (removed the other one).
root@heidenrod-obs:~# dpkg -l | grep indi-atik
ii indi-atik 2.0~201811230011~ubuntu18.04.1 armhf INDI Driver for Atik cameras and filter wheels.
ii indi-atik-dbg 2.0~201811230011~ubuntu18.04.1 armhf INDI Driver for Atik cameras and filter wheels.
one thing that I'm missing is the atik-test tool. Is it there somewhere or has it been removed/not implemented?
Kstars Mac osx
Odroid C1 running indiserver (kept up-to-date with apt-get update/upgrade)
HEQ5 pro / QHY5L-II-M (OAG) / Atik 314L+ / Gerd Neumann drawer
Weird, unfortunately I don't have that camera, only 383L and I run on x64 so would need logs to say anything useful... One thing to check is to make sure the driver reports API version 110, which is the current SDK, then it should be up to date otherwise too.