Do you try to set the other values of CCD_FRAME all at a time?

With my Atik314 if I do :
indi_setprop "Atik 314L.CCD_FRAME.WIDTH=600"
I get a message: [ERROR] Invalid frame requested (-1,-1) (600 x -1)

But if I do
indi_setprop "Atik 314L.CCD_FRAME.X=100;Y=100;WIDTH=600;HEIGHT=400"
this work as expected

What an idea! Yes this really works.
So I only have to adjust my script.

Thank You!

Cherno

Just want to mention user @kookoo_gr encounters issues with (probably) the new Atik driver in this thread : indilib.org/forum/ekos/3670-plate-solver-fails-to-solve.html

-Eric

Tried to debug an issue I've noticed earlier which is that if I abort a long exposure, say 300s, and start a short exposure for focus/alignment what not, the remaining exposure time from ArtemisExposureTimeRemaining doesn't start from the short exposure length but continues from where the 300s exposure would be causing all subsequent exposures to fail until the original long exposure ends. I added some debug prints and it seems ArtemisStopExposure returns 1 instead of 0 which indicates invalid parameter, which is odd considering it only takes the camera handle as input. I also tried changing that to ArtemisAbortExposure but it behaved the same way.

I informed Atik about this, we'll see their feedback.

Ok can you please contact Atik directly at This email address is being protected from spambots. You need JavaScript enabled to view it. ?

Ok, I'll take some log and send it there.

at a recent test with my atik 383l+ i noticed that i have bin options that go over 20x20

Abort issue should now be fixed in master, it was a case of not waiting for camera to go idle after abort, which causes the sensor to be flushed in a similar way as regular image download would and also takes the same amount of time and starting a new exposure during this time caused this issue.

Also noticed the large bin options, but they seem to work fine, though something like 32x32 binning isn't very useful

Hello,
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.
Jean-Jacques

I'm a little confused & dismayed over all this....

There has been a free & fully functioning INDI Atik driver for quite some time from Peter @ Cloudmakers (which I have been using very successfully with my Atik 16200 & Atik EFW )

Why the need to duplicate effort and go through all the laborious testing & fixing when one is already around?

At the very least, a collaboration between Jasem & Peter (who is a member & contributor here) would have cut down on all this testing?

As now, any re-compile I have to do will require that I specifically disable the GIT Atik branch in order to retain what I know already does what I need!

Phil

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.