I’m glad you got it fixed Hy.
Some other folks have given me some ideas of how to make the script even better recently. I hope I will have some time soon to make some of those improvements, but I have had a lot of grading to do recently. My students have to come first. But I will get back to this soon.
Cool, I’m glad the star profile works on the pi. I never would have dreamed of trying it before the pi 4 came out, but it is much more powerful. I didn’t expect it to work great on the pi 4 even then, but if it’s working ok, then awesome! I guess with the pi 4 the resources limited mode is unnecessary too?
So one thing that is probably relevant is that about 8 days ago, I accepted a pull request from Radek to add the optional dependencies libkf5notifyconfig-dev libqt5datavisualization5-dev and qt5keychain-dev. I would say all three of those are desirable packages. A raspberry pi may or may not have an audio device, but being able to configure it is useful. And the visualizations package will enable the user to make use of the 3D Star profile viewer that I made last year. And the qt keychain dependency will support logins for Ekos Live. So they are useful. So if you built since the change was made, you should be able to use the 3D Star Profile, you should be able to use the notification configuration and probably also use Ekos Live with the qt keychain. But if you built It before then, you probably don't have those features.
I would recommend turning off Audio Notifications in KStars. You can find Notifications in one of the menus. You can just turn off each of the "Play a sound" ones. That should prevent it from trying to use Audio. Based on what you said, I suspect you don't have an audio device that VLC likes.
Hmm, I guess it is possible there could be some sort of recent change to the code in either INDI or KStars that is causing an error. I haven't rebuilt KStars in a few days myself.
But you might take a look at my Raspbian build script and see if there is something that I did in my script that might be different on your system.
I think you are probably missing a dependency. Qt quick maybe?
Ah, I was looking at the screenshot at the top left for the last successful solve and the solution parameters. I assume it must have solved at some point or that would be blank.
KStars will tell astrometry do a partly blind solve to start. The first time it runs, the scale is set to zero, so that makes it ignore the scale. After that, it should use the previous solve to refine the scale so it takes less time to solve subsequent images. So yes, if it had a good solve, that updated those boxes, and I do think those solves were accurate based on the comparison you showed.. That should have also update the settings in the astrometry options. Yes I believe they are calculated from the pixel size, focal length etc. I'm pretty sure that the astrometry solution factors into that calculation, but it could also be largely based on other entries in KStars as well. That might be worth investigating if those aren't right. If you want to, you can uncheck the boxes, and take the scale out of the parameters it uses to solve, then see if it solves. Also I saw you were using bpp for the units, I don't have experience with that setting. I usually use aw, or arc second width. Did you try that? Astrometry.net takes a little bit to configure but it is incredibly powerful and once you get it configured well, it works like a charm. There are reasons for why it is used as the engine behind a wide range of plate solving front ends. It works well and works on many systems.
I believe that Platesolve2 is a closed-source windows-only program, correct? That might be kind of an issue for KStars which is an open-source Linux program that has been ported/adapted so that it will run on Windows and MacOS. I wouldn't be against adding support for other programs, but the program won't even run on my computer unless I use wine, which isn't really the best plan for this purpose I don't think. Personally I really like Astrometry.net, it does a great job for my system, solves in about 1-2 seconds most of the time and its accurate enough to get it going really quick.
Based on your screenshot, I don't think that the astrometry.net solution is that far off from the other one you posted. One says the pixel scale is 1.09 and the other says 1.11, one says that the field of view is 101' x 67'. and the other says 101' x 67.7'.
The solver options in the KStars options box for the scale that you posted say 1.99 to 2.44. Those numbers should be coming from the astrometry solution, but they aren't directly reported by astrometry.net, they are calculated by KStars based on the information it has, which includes the astrometric solution. So if they are incorrect, that is some KStars code that we will need to look at. But that isn't straight from astrometry.net.
In your video I don't see any information printing to the Ekos Guide Log. I would need to see if it has printed the messages saying whether or not KStars recognized that it has the same Camera that PHD2 has reported it is using, or if it found it was not found in Ekos. Also I don't know if this camera is setup in your profile in KStars. Can you send more information please.
Is this behavior observed in KStars 3.3.6 or in the latest version on GIT or latest nightly? I spent about a week working on a whole bunch of PHD2 related issues, including something like this. But that was about a week ago, and so it wasn't in KStars 3.3.6.
Was this crash before or after my latest PHD2 changes? Another words, are you running the latest version from GIT or the KStars 3.3.6 version?
It probably doesn't matter because I think that I didn't change anything related to dithering.
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