×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

New INDI Atik driver - Feedback requested

  • Posts: 17
  • Thank you received: 0
Mine is 383L+ too.
I've notice the same behavior with sub-framing not allowed while testing auto-focus.
I believe that donwload time get slower too, but maybe it's only a "felling", I don't have numbers to compare.
5 years 4 months ago #31950

Please Log in or Create an account to join the conversation.

  • Posts: 210
  • Thank you received: 104
Subframe work with the 314L.

I compare the time need to take a bias with a previous session log and it is not slower. From old log 4.6 s, from new log 4.5 s. This is total time from start of exposure until the file is saved by the client.
5 years 4 months ago #31951

Please Log in or Create an account to join the conversation.

Ok so subframing issue is confirmed. There is "preview" mode which I didn't enable. At any rate, if the camera supports preview mode, then it would be faster, but Ekos has no idea about this and it must be set from INDI control panel before you start focusing..etc.
5 years 4 months ago #31952

Please Log in or Create an account to join the conversation.

  • Posts: 210
  • Thank you received: 104
I tested the last change with the mutex. It work fine, no problem with my camera.
The following user(s) said Thank You: Jarno Paananen
5 years 4 months ago #31955

Please Log in or Create an account to join the conversation.

  • Posts: 472
  • Thank you received: 165
Good, I noticed the issue when taking new calibration frames, around every 8-10th frame would time out downloading. 383L+ has larger frames so it takes longer and the window for race condition is thus much larger. But with the fix I got the calibration frames all taken and imaged a couple of nights without problems.
5 years 4 months ago #31961

Please Log in or Create an account to join the conversation.

  • Posts: 17
  • Thank you received: 0
Some inteface tests.

When first open focuser tab with Atik, the subframe is disabled "but" with a check-mark (I think this check is disconsidered when disabled, but I don't know). Then I selected the guider camera, that enable the box. It comes "selected", I unselect and switch back to Atik. Then Atik show the box disabled but unselected.



I didn't find the "preview" mode that need to be set in INDI Control Panel. It should be there?



The last picture is from Ekos, nothing to set there too.



I think that you are talking about an "internal" set that need to be checked on driver, not on visual interface (maybe I misunderstood).
I saw people talking about "mutex", is it something that I can "configure" ou it's a code change?
And the last thing, Jpaana says that 383L+ shows frame size as 3362x2537, in my case, same camera, 3354x2529 (firmware 801).

Thanks
Mastria.
5 years 4 months ago #31971
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 472
  • Thank you received: 165
Subframing is enabled now with the update merged today, also the mutex is there, both are code changes and nothing to configure as such. My camera is using firmware 795 so the resolution seems to change between versions.
The following user(s) said Thank You: Marco Mastria
5 years 4 months ago #31973

Please Log in or Create an account to join the conversation.

  • Posts: 30
  • Thank you received: 0
On my Atik 460 subframing does not work.

indi_setprop "Atik 460ex.CCD_FRAME.WIDTH=600" does not change Atik 460ex.CCD_FRAME.WIDTH
Same with Atik 460ex.CCD_FRAME.X

Frames became smaller, one Pixel is missing in each direction. What is this good for?

Cherno
5 years 3 months ago #32073

Please Log in or Create an account to join the conversation.

  • Posts: 210
  • Thank you received: 104
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
5 years 3 months ago #32082

Please Log in or Create an account to join the conversation.

  • Posts: 30
  • Thank you received: 0

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

Thank You!

Cherno
5 years 3 months ago #32091

Please Log in or Create an account to join the conversation.

  • Posts: 1029
  • Thank you received: 301
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
5 years 3 months ago #32344

Please Log in or Create an account to join the conversation.

  • Posts: 472
  • Thank you received: 165
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.
5 years 3 months ago #32464

Please Log in or Create an account to join the conversation.

Time to create page: 1.309 seconds