Hi Denis,

First, congratulation to your great software! Really good!

I developed the indi_pylibcamera driver. It is a new project and certainly not free of bugs. I still try to improve it. When reading this discussion I got some questions:

1. What is POLLING_PERIOD used for? I saw this in the indi_simulator_ccd driver but I could not find out what it does. When searching internet I found something related to a focuser. But most of the cameras do not have a focuser. Is POLLING_PERIOD an importent attribute for a camera?

2. In the comment above you wrote, your program expects "len" instead of "size" in oneBLOB. I have all my half knowledge from github.com/indilib/docs and from analyzing network traffic. As far as I know github.com/indilib/docs/blob/master/protocol/INDI.pdf specifies "size". Is that outdated and should I change it to "len"?

Regards,
Ronald

Hi Ronald,
I'm not familiar with INDI protocol ) I simply analyzed the traffic and saw that both `size` and `len` attributes are presented:I don't know why but I decided to use `len` attribute. I will change code to use `size` or `len`.

I use POLLING_PERIOD (change from default 1000 ms to 500 ms) to make visualization of progress of current exposure more smoother. Smaller value of POLLING_PERIOD makes CCD_EXPOSURE property to change more frequent during taking shot

so happy Rust is making into astrophotography, got some projects myself using Rust so I thanks for your work! I read somebody asked with armv7 builds, I worked on building artifacts for multiple platforms using github actions and releases, basically whenever you cut a release on github pushing tags the machinery starts and upload under the release itself the artifacts. I could add those to your repo Denis if you think it may be helpful! Lemme know and gratz again!

Hi, Mattia
Thanks for the offer of help! It would be great if releases are created automatically using github actions and releases.
But these are plans for the future. And it will be possible to think about releases later, when the program will work stably

New alpha version 0.0.34: drive.google.com/drive/folders/17d49C9Xg...XcdNsCtb9d15nM-WBjGZ
Not tested on real sky due to clouds ((
* Rewritten code for reading XML packets
* Fix in dithering code
* Some UI improvements

@Denis: I'm very glad to confirm, that taking pictures with indi_pylibcamera now work as expected. Great work!
I'm really exiting to try your program in real situation, under real sky to see how live stacking performs!

Simon, don't expect too much from my program now. Contrast of preview image is too low. Look at screenshot for example and compare it with autosaved live stacking image processed in Siril and RawTherapee
I plan to make improved view settings a bit later.

The AstraLite is looking quite interesting and promising also! Well done!

I hope that all of you guys will have the time one day to improve Ekos with your ideas and programming skills. For example I am looking your GUI and I wish I could have the ability to have my Ekos like this. Or floating windows. Or even the ability for live stacking.

Keep up!

New alpha version 0.0.45. Not tested on real sky. Main features:
* "Full screen" button to hide control panels and show only image
* Watchdog to restart photo capture if it is stuck in "download" stage. Very useful for new touptek camera driver

Thank you for your wonderful app.

I tried it immediately.

About driver connection

Connect to the server by specifying the IP address of the server → xml file is sent from the server. -> Display in the driver list -> I think that the flow of connection will be the correct rule.

Please check how to connect CCDCiel.
(The Ekos style combined booting and connecting to the server driver, which was confusing.)

Thanks for the comments! I simply forgot to disable widgets for device selection if user select "Connect remote" checkbox. Will be fixed in next alpha version.

Thanks for the great app.

I tried the Windows version and the Linux version.

Both are working with the simulation driver.

Since this app is used by connecting to the driver, the red frame part of the attached image is unnecessary. (The part framed in red is required when starting the server driver, but it is not required when connecting.)
The live stacking image was in TIFF, is there a save option?