using the 'full field' option just under 'Auto Select Star' could help.
It chooses stars in a donuts excluding, if requested, the core.

thank you Jasem, i will test and report here.

Read More...

I changed my camera from ASI071 to ASI1600, the indi_asi_ccd driver crashes both on stable and nightly build.
Could it be something related to a different configuration file used by the new camera (_ZN4INDI13DefaultDevice11purgeConfigEv) ? Which config file should I cancel?

Attached the full log, here's the relevant part of the log:

[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "FIFO: start indi_asi_ccd"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "FIFO: Starting driver indi_asi_ccd"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Driver indi_asi_ccd: pid=8510 rfd=5 wfd=10 efd=11"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Client 9: new arrival from 127.0.0.1:56816 - welcome!"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Driver indi_asi_ccd: indi_asi_ccd: symbol lookup error: indi_asi_ccd: undefined symbol: _ZN4INDI13DefaultDevice11purgeConfigEv"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Driver indi_asi_ccd: stderr EOF"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "Child process 8510 died"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Driver indi_asi_ccd: restart #1"
[2019-07-24T14:14:21.805 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Driver indi_asi_ccd: pid=8513 rfd=5 wfd=12 efd=15"
[2019-07-24T14:14:21.806 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Driver indi_asi_ccd: indi_asi_ccd: symbol lookup error: indi_asi_ccd: undefined symbol: _ZN4INDI13DefaultDevice11purgeConfigEv"
[2019-07-24T14:14:21.806 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2019-07-24T12:14:21: Driver indi_asi_ccd: stderr EOF"
[2019-07-24T14:14:21.806 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "Child process 8513 died"
[2019-07-24T14:14:21.806 CEST CRIT ][           org.kde.kstars.indi] - INDI driver  "indi_asi_ccd"  crashed

there's an option in the Guide tab -> options... -> guide named 'non guide dither pulse (ms)'.
I only have used it once with my mount (10micron hps 1000) but doesn't seems to send pulses to the mount.

Read More...

hi Rene,

the ideal exposure time depends on many factors that are not known by INDI/Ekos. Mainly SQM and some feature of the camera like QE, dark current, read noise, FW depth have impact on the optimal length of the exposure.

I would rather use simulators that available online or as excel file.
I even tried to write one for myself but my personal experience is that, despite the theoretical model being perfect, the uncertainty on some inputs is affecting the results so much that an empirical approach based on trial and error is more valuable.

Ferrante

Read More...

hi Wolfgang,
to me it makes sense.
I'm thinking of a use case where the weather gets bad (warning) and the sequence is stopped and the shutter is closed but the cooler still on and mount not parked. If the weather gets worse (Alert / danger/*) mount is parked, camera warmed up and INDI stopped.

Are you thinking to place the logic (the steps) for suspend / resume and shutdown / start up in the Observatory on in the Scheduler? as you know i'm in favor of the Observatory because it could be used even if one is not using the Scheduler. For example if a standalone Capture is running.

* somewhere else in INDI / Ekos it has been used 'Danger' or other words instead of 'Alert' (e.g. in Weather interface). I think any word is fine but it should be kept the same all over the place.

ferrante

Read More...

hi Wolfgang,
I was wondering if the observatory status is useful also as a command to activate the whole observatory.
For RoR, it is redundant, they already have unpark to get the same result.
For domes, it could be dangerous to issue two commands (open shutter and unpark) at the same time. Actually would be more dangerous to do the opposite: close shutter and park.

I would leave the observatory status issuing no action, just showing the status. Any action should be managed by a more complete procedure that is customizable. Like: first unpark dome, wait 10sec, open shutter.
Again, this approach would make more sense in case of a shutdown than wake up.

Ferrante

Read More...

hi Wolfgang,
Using Weather Watcher. But I can't recreate the status icon issue anymore. I will let you know if I understand the condition for this to happen.
Ferrante

PS: sent you a personal message on a related topic.

Read More...