it seems that the twilight is according to a sun dip of 18°. I found in the setting to set dusk and dawn offsets. Is it possible to set the sun dip to lets say 15°? For me that would be a nice feature in the summer where we have times with no twilight in EKOS. I always start my session at a sun dip of 15°...
I just tried using simulators. I installed GSC and can get a picture with stars when using the capture tab. Also the guiding / guiding calibration works. So I tried the alignment tab (all settings are default). Picture was taken, but when starting plate solving Kstars suddenly crashes. I started with ekosdebugger, I attach the log.
I'm using Opensuse 15.5 with latest updates.
Thanks for helping.
When I used Phd2 for guiding long time ago I stumbled also over this behaviour. If I remember correctly you first have to start PHD2 then Kstars (or maybe the other way round). And you have to look in the "guiding" tab that guiding is "connected", sometimes you have to klick on the "connect" button.
Now I use the build-in guider and I'm happy with it.
Thank you for your quick reply. I made my horizon roughly 1° bigger than it actually is. So for long focus length no problem. But I use focal length down to 180mm (sometime 50mm, but thats rare), so I have with my QHY268C 7.5° x 5° FOV. So I would have to cut off nearly 4°, for 1500mm FL I would need only 0.5° (+ offset due to disturbed air and so on near the "horizon")
It would be on the wish list to have this feature: start of capturing depending on focal length
But doesnt matter you guys do all a very good job
as I wrote before I'm testing the scheduler. In principle it workes but I encountered another question:
I had created an artificial horizon for my balcony observatory. Today I tried with simulators to see, if the full FOV of the camera is up the horizon when starting the sequence. The picture shows the situation for the first light. As one can see, part of the picture is still below the artificial horizon. Target was the star Mirach.
thanks for your reply. It makes the scheduler clearer to me. As I wrote I just starting scheduler and stumble over things I never thought about . Normally I think forcing the temperature will be only a problem, if I set T to lets say -20°C and take pictures in the summer at 25°C. And I do it like you, I watch the first few lights to be save.
And if I understood it right, then I can set the temperature manually despite setting the "force T" option.
If I understood correctly the intension of "forcing T" was that the first capture should start AFTER reaching the intended temperature. I never used it, because often the first captures are not the best due to GPG learning.
What I'm wondering is, why the temperature was not set (still a 0 in the temperature field) and the cooler was not even turned from OFF to ON...
What will happen, if for some reason the temperature will not be reached and you dont recognize it? Then one can forget the whole session, because the cooler is OFF and sensor temperature is probably 20°C or more...
The question is, is it a feature or a "bug"?
Seems that it was my fault, I changed the force T button without reloading the sequence... Now the sequence is ok. I will test next time.
thank you for your reply. I just tried that and I became the same esq file... There is a line
and the "force='false' was set no matter if I click the button or not. I also tried to push the button "Cooler ON" and save the esq but same outcome.
When I started my sequence yesterday, as I wrote everything worked fine, but the cooler stayed in OFF position. Also the -10°C was not set. So I had to set both -10°C and Cooler ON manually.
I attach the esq files.
BTW it would be nice to have .esq and .esl in the list of allowed files
Thank you for your reply and clarification, Hy. I always reuse calibration if possible but I change my rig depending on the target, so I have to recalibrate sometimes. But now its clear to do that before starting the scheduler.
I'm testing the scheduler for the first time. Startup was quite good, focusing, alignment and guiding are ok. But the camera temperature was planned to set to -10°C but I have to do it manually. The first light was taken with 0°C. What went wrong? I attache the log (starting the session was 20:00), esq and esl file. Thanks for helping.
I'm currently working on testing the scheduler. Up to now I just just the capture tab, tonight will be the first scheduler session with one target.
I've stumbled over the following question: guiding calibration should be done (at least to my knowledge) at roughly 0° DEC around meridian. So what should I do if I have a target with high declination and have to calibrate? This is not optimal for guiding calibration. So how to proceed here? Of course I could calibrate befor starting the scheduler, but that should be the way?
Thanks for clarification