Last night after a successful meridian flip, autoguiding was not resumed automatically. I think it should, right ?
On Kstars 3.6.0.
Logs attached here.
Any ideas ?
Any updates on this ? My platesolving also suddenly started failing.. At least on my primary scope.. on my guide scope it still works for some reason.
Strangely it just fails in the middle of my session. It _was_ working... totally clueless why it suddenly stopped working.
No, I didn't as I am currently enjoying my holidays. Great to hear about this update.
Is there any idea when astroberry repo will contain kstars 3.6.0 ?
The repo from the upstream maintainers does not support astroberry
After indilib.org/forum/general/12048-target-l...dian-flip.html#84853, I took the advice, and I _slewed_ to the target.
However, it seems the meridian flip fails on "Meridian flip failed, pier side not changed" for many times. Eventually it seems to work out: ""Meridian flip completed OK.", but capturing is not resumed for some reason...
Attaching the full log here. KStars 3.5.9
Not sure if I understand your explanation. If I only use the Capture module and set 'slew to target' in Alignment tab, will it be okay or not according to you ?
Yes, I am attaching the full log here.
IMHO the software should _always_ slew to the target after a MF.
Indeed, it is set to sync.
However, I only this tab to do initial plate solving. I had no idea this tab was also relevant for meridian flip. Did I miss any documentation ?
The other day I was shooting a target (Deer Lick Group).
After a meridian flip, capturing resumed but it was off by several degrees in declination,
In the attached log you can see before the meridian flip, the telescope was pointing at RA= "22h 38m 08s" DEC= " 34° 31' 49\"".
After the flip there is a plate solving which results in Solution coordinates: RA (22h 37m 39s) DEC ( 37° 24' 54\") Telescope Coordinates: RA (22h 35m 02s) DEC ( 35° 50' 31\")".
Finally we find a "Syncing to RA (22h 37m 39s) DEC ( 37° 24' 54\")".
I do not understand why Ekos does not try to slew back to the original coordinates but just syncs and continues capturing from the wrong coordinates.
Logs in attachment (Kstars 3.5.9)
Thanks in advance,
Hi,I have always been an enthusiast user of kstars.
However, last night, things failed horribly.I wanted to use my new ZWO EAF and I started the imaging session with a refocus of every 60 minutes.When I checked my setup in the morning I saw my camera was stuck on one of the tripod legs, even though I had configured kstars to return to home position on the right time.
However, kstars had crashed so the mount kept on going. I am still not clear if there is any damage but I am very concerned
Moreover, even though I think the refocus worked (looking at the logs), no more pictures were taken after the first refocus.I am attaching the logs here and also pointing to the core dump .
This is on astroberry with kstars 3.5.8 stable and indi Code v220.127.116.11-6-gfd391d51b. Protocol 1.7.
Last night my imaging session failed after ~165 images. I have attached the logs.
It's my impression this problem has gotten worse since a recent upgrade.
running this on astroberry with:
INDI Library: 1.9.5
Code v18.104.22.168-6-gfd391d51b. Protocol 1.7.
The problem was gone after I restarted Indi in the morning.
Any ideas ?
Just wanted to share I found the cause. The skyguider pro was not entirely stable when doing PAA. I fixed this and now the results are much better. however, still some minor variation between consecutive runs.
The latest version of kstars there is just 3.5.4. Which is also available in the normal repositories. Wanted to try out some 3.5.5 nightly builds.