Yes it can be extremely fast. But I have found that sometimes it doesn’t solve a field that astrometry.net will solve. But that is a small price to pay for software that tends to solve much faster while requiring much less configuration. So if it doesn’t solve, just try a different exposure time or move to a new spot of sky
It is possible that Jasem might need to update INDI web. Let me check with him.
That could have something to do with the fact that you might still be using KStars 3.3.6 on your client machine, I'm not sure. In a couple of days, you should have 3.3.7 and then maybe it will be fixed.
Yep, to be fair, my advice was to get the 2GB version since that's all you should need memory-wise. However, I myself instead opted for the 4GB version, just because it was just a little more money. So you can do what I said or do what I did
I would recommend 2 GB at least. Sometimes on my raspberry Pi 3, it uses more than 1GB, so it goes in to the Zram swap. But with Zram enabled, there is no reason 2GB is not enough.
Ok sorry other way around KStars 3.3.7 on Mac with stellarmate 3.3.6
So that should not make a difference. Note that KStars doesn’t talk to another KStars. It talks to the INDI server. INDI has changed some recently since the last release but not enough to matter for this.
So yes absolutely you can test KStars 3.3.6 on Mac with a stellarmate that hasn’t been updated to 3.3.7
Thank you! Let me know of any other Mac issues.
So I found that the issue for ZWO was in the ID of two of the ZWO library binary files. I used otool to fix it. I reuploaded the dmg. Please test it again. If it works out, I will put in a pull request for the new library files for ZWO.
Birthdate19. 07. 1980
About meEven though I am relatively young, I have been an astrophotographer for about 20 years. Within the last 5 years or so, I have taken my hobby to new heights. I built my own 10 inch telescope including grinding the mirror, bought a wide field newtonian for wider fields, acquired a much better mount to put them on (separately), got an SBIG camera for cooled CCD photos, modified a Canon XSi for better DSLR photos, and got lots of accessories. I have been doing all of my astrophotography with a Mac computer. I have basically made my own portable observatory, everything is carefully organized into boxes that I can load into my car in about 20 minutes. I take these things to dark skies and do lots of imaging at star parties.
I found out about INDI in May 2016 when Pleiades Astrophoto sent me an email about including an INDI client in their software. When I investigated further, I found out about KStars and Ekos. I quickly realized that I could install everything on a Raspberry Pi, velcro that to my scope, and use VLC to configure it from my computer using wifi. I have implemented 2 modes. The first is using the Raspberry Pi as an INDI server and using my Laptop as a wireless client using either the EKOS VM (running KStars and Ekos) or PixInsight as the client software. The second is using KStars and Ekos on the Raspberry Pi and controlling everything through VNC. Both methods have allowed me to cut the cords, move to WIFI control, and make all USB connections shorter. The second method also allows me to put my computer to sleep after I have configured the PI to do all the work. All I have to do is check in once in awhile to make sure it is working properly. So far this experiment is going very well, but I did have to work out quite a few issues along the way. I have been keeping a couple of logs of everything I have done to make it work, however, which is very useful. There are still a few problems, but the system is fully functional. It is a good thing it is summer so I have time to work on this!
The remarkable part is that you can automate your astrophotography setup, make the connection wireless, simplify the software by just running one program (KStars/Ekos) that runs it all, and you can make the connection to the devices separate from that program using INDIServer. (The last item is important because if KStars/Ekos were to crash, the devices would still be running on INDIServer.) And all of this will cost you around $100 including the Pi, a case, a 32 MB microSD card, the software, and a powered USB hub. There was a bit more work involved in setting it up and figuring it all out, but it was worth it.
I am an:
Physics and Computer Science Teacher
Delaware Astronomical Society Member
Mt. Cuba Observatory Education Associate