This is what is strange, because last night mine was successful again.
Ever since I made sure the "solve and slew" button was set, and that I turned off "Subframe" in the guider, my success rate went way up.

Peter

I never take mine off "solve and slew" and I turned off sub-framing. Perhaps it's because I'm running Kstars on a Windows machine instead of from the RPI.

I'm becoming so frustrated with the constant issues. I know the software is free but really it should be able to handle something as simple as move the telescope, take a picture and compare it to a file, then rinse and repeat until successful. Might be time to consider another software package like SGP or Voyager.

Rene

I’m in a similar frustration boat, in that every new update breaks something else that worked before.

But I hate using MS Windows and while I put up with it at work, won’t have it in my house. The Mac OSX version works better than the Linux version so once I finish my observatory I will bypass the Linux machine I use as a bridge and direct connect a Mac to my equipment. My new mount (CEM120 EC2) will make that easy with its built in USB ports right at the dovetail plate.

Ah the Mac vs Windows battle. As old as time itself.

I find the Linux version slow even on a RPI4 and it's a poor user experience as I have to terminal in and have less real-estate. At the moment I have 2 screens I can spread out on. I'm having a good think about what I'll be using going forward. KStars/Ekos has a lot of potential to it but we need this thing to bullet proof. I'm not staying up all night to monitor the software. It should be stable enough that I can set and forget.

No Mac vs Windows fight. I use both.
I just don't use Windows on my own time in my house.

Yes, I recommed that you try SGP. It's a well supported, mature, product and I think you will find that the software and support will suit you. You will find plenty of kindred spirits in their forum.

I think I'm going to have to. I'm wasting so much time fighting with this software. Tonight is no better.

So far I'm having aligning issue where the alignment module won't plate solve. It get's close to my limit but then fails. Now I'm having issues with the guiding module where the calibration fails. Other people may be having better luck than me but I'm fed up wasting my time.

I just checked the logs and the solver just can't get a solution after the meridian flip it keep trying and trying over with multiple timeouts. Did you happen to see the images post the meridian? were they normal? no clouds or some motion knocked the camera to different area in the sky or something like that? At any rate, capture module was trying too many times, and I just adjusted it to also fail in case of solver time out (vs solver failure).

Hi Jasim,

Unfortunately I was asleep when it did the meridian flip so I don’t know what the images looked like.

Las night though when I was having similar issues with the solver timing out the images looked like the always did. Slightly grainy but clear enough to solve from. The behaviour last night was very weird. It would skew to a target but be way off. The solver would start and the mount would get closer to the target. It would keep solving until it go close to the limit (30 arcsec), then back off where it would solve, get close but never reach the limit I set.

The other issue was that guiding was constantly failing. Calibration start, R.A. would calibrate but Dec would fail.

The suddenness of these issues makes me think it’s my mount. I have had issues in the past where the Dec would fail on guiding calibration but if I tried again it would work. Then my Total RMS would never below 1.5 - 2.

Rene

I had a similar issue with the mount not moving to the target. The solution was to select nearest point instead of N-star in my mount's alignment tab.

I'm almost certain it is set to 'Nearest point' but I'll double check.

Cheers

Yesterday I had a close look on the guide module working, when slewing from one variable star to the next. I think the issue is that guiding is not searching for a guide star when it resumes its work.
When the first picture of the new area is coming in, the green square stays where it was, when guiding the variable star before. In most cases there is no star in the green square then. But in order to serach for a new guide star the module stays there and guides on whatever I don't know. After a while the guiding module reports: "Delta RMS threshold value exceeded. Searching for guide star." Within some millis the green square is locked on a suitable guide star and everything works fine ........ until the next variable. Would be nice if this could be fixed.
I hope my English is good enough to understand what I mean.
Greetings, Jörg!