Thanks for taking a look at it. Nice to know it can be done at least manually. I’m personally not comfortable editing the SQL database, so don’t think I’ll try it. But the horizon looks good other than what you mentioned at the North Pole, it doesn’t look like it closes the last polygon.
I’ve found the most reliable way is to not run KStars/EKOS on the StellarMate, but to instead launch the desktop application (on the Pi) and start the server. You would have to have the StellarMate on the same server as your iMac to do this.
Alternatively, you can use VNC to log into the StellarMate and run KStars/EKOS on the device itself, and only use VNC on your iMac. The iMac has VNC built in. You only have to open a finder window, look in the left sidebar for Network. You will see the StellarMate listed (if connected on your local network). Double click it, press screen share. Put in the StellarMate password “smate” and the VNC window will open so you can control the device from your iMac desktop.
An update to my wishlist feature here. After talking to the developer of Observer Pro, the text file it outputs lists the coordinates in sequential number. The first number in the text file is 0, then 1, 2, 3, etc. The coordinates are ordered altitude first, azimuth second. Using the example numbers below the first number would be 42° Altitude, 0° azimuth, and so on down the line.:
These are just the first 5 points in the text file linked above. There are 300 points! A lot to input manually. It would be fantastic if KStars could import the text file or allow me to upload in some way that doesn't require me manually entering 300 data points.
on the iPhone to generate horizons using the iPhone camera. It has an export feature that exports the coordinates to a text file. I've used it to generate a JPG to bring that horizon into SkySafari (detailed in my linked blog post), but would like to see if there were a way to add functionality to import it into the horizon manager within KStars. Here's the file it generates for reference.
File Attachment:File Name: horizon.txt
File Size: 3 KB
carkinzo wrote: Okay, so it's not a Beta anymore,
but an official version?
But I didn't understand where the download is from.
You can get it https://edu.kde.org/kstars/here , or from the download menu.
wvreeven wrote: Andrew, one way of ensuring that actual stars are picked is by doing full frame focusing. And please try SEP as I suggested before because it is MUCH better at detecting stars.
Yep, I will try that for sure. I was using full frame for some time as it did help with lots of focus failures. But switched back to single star as I thought it did a better job of getting better focus. Maybe it was all in my imagination.
Thanks to everyone offering help.
Unfortunately I didn't save a log. But I did manage to cut and paste the windows from both focus and alignment to text files. It's obvious from the screen shot that the focus system got out of focus by looking at some noise and not an actual star. This was half way through the evening (I had been imaging about 6 hours with refocus set every 45 minutes due to temperature variation). There must be some kind of threshold that could be set so that the focus algorithm doesn't pick up on noise, and insures there's a star. The star, when there, is obvious visually as it's a point source multiple pixels wide. The noise is clearly not a white point source. And this camera the ASI2600 is extremely low noise.
Additionally, thanks for the input Hy, you probably understand the system way better than I do.
File Attachment:File Name: logmessages.zip
File Size: 586 KB
What does tolerance actually do? I've tried full frame focus, but find that the overall FWHM is larger (maybe that's because it's averaging it across the frame). I do single star, auto selection, subframe. I will definitely set average. And a smaller initial step size. Though since focus varies as much as 200 on my Edge scope due to temperature drops, I don't think I want to make it too small. I'm thinking max step size and max travel are probably wrong and I still need to set them. I believe either or both have something to do with how far focus is allowed to travel before resetting. And since they are large, it allows my scope to get far out of focus without resetting. I just don't know which I should adjust and what they specifically have an effect on.
I've been imaging successfully with EKOS for a few years. I continue to occasionally come across an issue where the focus module picks up on some stray element, and gets way out of focus unable to recover. Unfortunately, it thinks it's in focus as it has no way of actually knowing. Last night, imaging M106, it did exactly this. After a dozen or so successful focus attempts, on one focusing run, it got out of focus and stayed there. Then the scheduler tried to check alignment, and the scheduler tried to solve the unfocused image 196 times. It seems at some point, the system should recheck focus with so many failed attempts. Looking at the focus parameters I noticed Max Travel, and Max Step size. Which of these would I want to set to stop this from happening? Usually focus seems to float within a few hundred (0-250) or so. I have a Moonlite focuser, so no backlash, and I've been using Polynomial process.
What should my parameters be for both the process and mechanics tab. Thanks for any help. I've lived with this issue far too long, and probably could have avoided it had I looked closely at these settings.
Saw the final 3.4.0 release was out, but I ran the beta overnight under the stars, all worked well. Scheduler, PHD2, focus, sequences, and alignment.
Here's the image I shot. Short integration...poor seeing, but I like the practice.
Thank you kind sir!
Will try it out live tomorrow night when the clouds clear up.
The new camera drivers are imbedded in the latest version 3.3.9. However, there have been reports that the 6200 doesn’t work. My 2600 does work. So, it’s possible the 533 is also not working. Jasem is working with ZWO addressing issues with the new ZWO drivers.
Glad to hear it’s working for others. I’ll check once I get home from work this evening.
I'm getting an error trying to download the file. There's a typo in the link, but even trying with that fixed I get an error.