I have a question about setting up a FOV indicator based on the IOptron iPolar. The reason I want o do this is, I'm thinking of buying one to help with polar alignment but I have trees obstructing my view of the pole. Now before I do buy one I want to know whether the 13 degree FOV will capture enough stars. SO I wanted to set up the FOV indicator to give me a sense of this.
Has anyone set this up in KStars?
I’ve been reading a bit about mo7n t modelling and how it can improve go to performance and alignment. My questions relates to where in the imaging workflow this would sit. Pre or post polar alignment or somewhere else.
I'm almost certain it is set to 'Nearest point' but I'll double check.
knro wrote: 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).
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.
ChrisRowland wrote:Yes, I recommend 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.
RugbyRene wrote: 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.
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.
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.
PK wrote: 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.
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.
Ok here's the log file (attached)
I've had a quick read of it and you should start looking from the following timestamp:
[2020-04-25T02:28:56.092 AUS Eastern Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Telescope completed the meridian flip."
From this point the alignment module kicks in and tries to solve. It attempts to re-align for the rest of the night with no luck. The last "Solver Failed" mesage I can find is at timestamp:
[2020-04-25T02:41:41.729 AUS Eastern Standard Time INFO ][ org.kde.kstars.indi] - Astrometry : "[INFO] Solver failed. "
Then the mount/Ekos sits in a never ending loop of aligning until I killed it at 5:00am this morning.
So the meridian flip failed again last night. This time during alignment. From what I could see the solver failed and just gave up. Surely it should be able to reset itself and try again. There’s far too much manual intervention and monitoring required.
I saw your Facebook post and was the one who asked the questions. Some good tips there. I'll try tonight.
From what you and others have said, the guide module isn't fool-proof after a meridian flip. Perhaps the devs need to look at it for the next release. It needs to be more robust when it fails to find a guide star. Not just give up.
So I managed to repoeat the issue last night while imaging Cent A. Meridian flip completed, post flip alignment was fine, but it failed on auto-guiding. Looks like it couldn't find a guide star and just gave up. I was using the internal guider. The relevant part of the log file is below and I've attached the full file. There's also a screenshot of the guiding module which is complaining about mount back-lash. Never seen this error before so figure it's just a generic "it failed and I can't be bothered recovering gracefully" error.
[2020-04-22T23:29:00.787 AUS Eastern Standard Time DEBG ][ org.kde.kstars.ekos.guide] - Iteration # 21 : STAR 131.712 , 90.1625
[2020-04-22T23:29:00.793 AUS Eastern Standard Time DEBG ][ org.kde.kstars.ekos.guide] - Iteration 21 Direction: RA_DEC_DIR Duration: 2000 ms.
[2020-04-22T23:29:00.799 AUS Eastern Standard Time DEBG ][ org.kde.kstars.ekos.guide] - Star x pos is 29.7237 from original point.
[2020-04-22T23:29:00.804 AUS Eastern Standard Time DEBG ][ org.kde.kstars.ekos.capture] - Guiding state changed from "Calibrating" to "Calibration error"
[2020-04-22T23:29:00.810 AUS Eastern Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Post meridian flip calibration error. Aborting..."
[2020-04-22T23:29:00.816 AUS Eastern Standard Time INFO ][ org.kde.kstars.ekos.capture] - "CCD capture aborted"
[2020-04-22T23:29:00.823 AUS Eastern Standard Time DEBG ][ org.kde.kstars.ekos.capture] - setMeridianFlipStage: 2
[2020-04-22T23:29:00.829 AUS Eastern Standard Time INFO ][ org.kde.kstars.ekos.guide] - "GUIDE_RA: Scope cannot reach the start point after 21 iterations. Possible mount or backlash problems..."
[2020-04-22T23:29:00.837 AUS Eastern Standard Time DEBG ][ org.kde.kstars.indi] - ZWO CCD ASI120MM Mini : "[DEBUG] Uploading file. Ext: fits, Size: 72000, sendImage? Yes, saveImage? No "
[2020-04-22T23:29:00.842 AUS Eastern Standard Time DEBG ][ org.kde.kstars.indi] - ZWO CCD ASI120MM Mini : "[DEBUG] BLOB transfer took 0.00132023 seconds "
[2020-04-22T23:29:00.848 AUS Eastern Standard Time DEBG ][ org.kde.kstars.indi] - ZWO CCD ASI120MM Mini : "[DEBUG] Upload complete "
[2020-04-22T23:29:01.252 AUS Eastern Standard Time DEBG ][ org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] Aborting camera exposure...
I'm running Kstars on Windows 10 with INDI on my RPI4. Was wondering how I set up Sextractor with this config. I've tried ticking the check box in the Astrometry settings but solving fails and I have to revert back to the old way.
Hah, ha yes! Cool the camera of course. Thanks for the info.
So what function do the startup/shutdown scripts serve?
I'm currently setting up a schedule for the a few nights imaging and I would like to use a start-up/shutdown script. from what I understand, they have to be written in python, which I don't know all that well. So I was wondering if someone had a script I could use. I realise it will be specific to their system but if I could use it as a starting point I could modify it to suit my set-up.
I'm running KStars from Windows with INDI on a RPI4 attached to my rig.
Here's what I'd like the script to do:
1. UnPark Mount
2. Warm camera to a specified temp
At this point the schedule should kick in and run my imaging
1. Warm camera
2. Park mount
Thanks in advance