Yes , there were some important things that should happen in the setup steps. Sorry you had a crash that prevented the setup for completing successfully. You don't need to install GSC, but it can be very nice for using simulators to get fake stars so you can run a full Ekos session without being connected to real equipment. But the other startup steps are critical. In those steps some initial parameters get set and files get copied.
Yes you should have the boxes to the left of each of the items checked to use the internal INDI drivers, internal INDI server, internal Astrometry, and internal XPlanet. Unless you have a home-brew installation on your computer where you installed all of these things. That is not common. You don't need to type the paths if you are using the internal stuff because the paths are fixed inside the app bundle.
If you want to install GSC Later, you can go to the menu "Settings" and select "Startup Wizard"
For Astrometry, if you go to the Align module in Ekos and click "Options" at the bottom right, you can get into the settings to set them to the internal astrometry solver and internal config file just like you set the other things in preferences. Because you didn't get through the whole setup successfully, you might need to manually create the folder ~/Library/Application Support/Astrometry and you might need to edit the Astrometry.cfg file so that it uses that location.
Does this help?
The "Canon DSLR," "Nikon DSLR," etc are really all just links to the GPhoto Driver. If you just select the GPhoto driver, you should be good to go. It's nice to have it say "Fuji DSLR" but it really isn't necessary for imaging.
Python is really easy to use as long as it doesn't have syntax problems. . ..
Yeah, as I said, stupid python and its syntax issues.
Hmm, see if this works. Just remember to change the .txt to .py
File Attachment:File Name: kstars.txt
File Size: 4 KB
Do you have a text editor that shows you the hidden characters so that you can make sure it is all the same? To be honest, this is what I hate the most about python.
I think that is likely the error I was telling you about. Probably the easiest way to fix this is instead of just copying and pasting the code that I gave you, start with the file the way it was and just edit each line appropriately. Then you won't have any syntax errors. Watch those spaces and tabs, they are not the same.
Oh, I forgot to mention, you might want to set the Logging to "Default" instead of "File" before you run it via lldb so that all of the logging gets sent to the terminal window along with any crash info.
I did just test saving and loading a sequence file using simulators on my MacBook Pro. It loaded almost instantly with no beachball or delay of 10-15 seconds. That is very strange. I am using the latest version of Mojave on this computer that I just tested it on and the computer KStars version 3.0.0 was built on is running El Capitan, so it should work for any system running El Capitan and later. Please see if there is anything else that is strange or sluggish, because that is definitely odd.
Also you might want to run KStars from the command line to see if that reveals anything about the sluggish behavior or the crashing that you reported. Try this:
Then try whatever you can do to produce sluggish or crashing behavior so it all gets recorded.
Are you using KStars and INDI both on the same computer? In other words, are you connecting to a raspberry pi or other SBC from your Mac when you experience these crashes? I had some strange crashes in OS X version 3.0 right after I first build it when I was testing it, until I updated the software on the pi. Since then, I have not seen any crashes.
I can certainly make a new Mac build if there is something wrong with the current one, but first, we would need to figure out what is wrong. Is some incompatibility in the Mac build, is there a version conflict between the KStars build on the Mac and the INDI build on an SBC, or is there some other problem that is more general that affects all users on Windows, Mac, and Linux. For the last one, it could be an issue with KStars, with INDI, or with some dependency of those.
I know that PHD2 had some changes recently to how it communicates data back to the client programs and I am planning to look into how we need to update KStars soon to adapt to those changes, but I don't think that anything they did would cause crashes in KStars, nor does it seem to affect the quality of the guiding. But I will look into that one.
It would be very good if we can get a pattern or cause of any crashes, especially if they seem to be reproducible, so that we can narrow down the cause. For me, the crashes just happened randomly until I updated the software on the pi and then they did not happen anymore. I think sometimes it happened when I was trying to focus and sometimes when I was trying to run a sequence if I remember correctly.
P.S. Be careful of spaces and tabs, python is ridiculously picky about those. Python uses indenting to determine what code is inside or outside of a code block. For example, if you try to indent the same way as the code above using tabs when the code above it used spaces, it will complain that the file has syntax errors. So try to match the syntax that already exists in the python file when you change it.
This change will not be too hard to make. All the packages in craft are built using simple python scripts. In my/your craft installation, the relevant script should be in the craft root directory in etc/craft-blueprints-kde/kde/applications/kstars/kstars.py.
You should change the current code that downloads the stable version:
self.description = 'a desktop planetarium'
for ver in :
self.targets[ver] = ' download.kde.org/stable/kstars/kstars-%s.tar.xz ' % ver
self.targetInstSrc[ver] = 'kstars-%s' % ver
self.defaultTarget = '3.0.0'
self.displayName = "KStars Desktop Planetarium"
To download the current version on git:
self.description = 'a desktop planetarium'
self.svnTargets = " github.com/KDE/kstars.git "
self.targetInstSrc = ""
self.displayName = "KStars Desktop Planetarium"
self.defaultTarget = 'Latest'
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