I would like to 2nd the request for PHDlogviewer compilation to be worked into the script. I was unable to get past compiling wxformbuilder which is required to compile phdlogviewer.
Yes. That was the point, Without PPA, what are the steps necessary to clean/rebuild Kstars from scratch.
Although I ended up just re-running the script, it seems inefficient for rebuilding only KStars. Good news is it resolved the crashing.
I'm on raspbian. Raspberry Pi 4 and relearning how to go about things without PPA.
With that in mind, could I get advice on the steps required to rebuild kstars?
I had a hard time finding instructions on the forum.
Simulators, natively within the Pi. But it also crashed with a custom profile.
AstroNerd wrote: After running your script again to install these new WiFi upgrades, I just opened Kstars and it’s broken, it opens, then when I click ekos it brings up a window that says:
“An instance of INdI server is already open, do you want to close before opening another”
and no matter if I click yes or no it just shuts Kstars completely down every time...
I have just encountered the same issue. Everything was fine at first. But now when I try to run a profile from EKos, KStars crashes.
I have been configuring various things in the meantime so I am not sure when it broke.
I am aware of the canon mounting issue that has affected some users. Although I use a canon t3i, it has never come up for me.
I noticed modemmanager was installed during the script run. This should be avoided/removed because it is known to cause issues with serial bluetooth (such as EQmod BT dongles)
Also, I'm not sure if it is related to your script or not, but I could not see my USB flash media drives mount at all.
Over all I must say the script worked very well. Thank you.
I have resolved it, see edited comment above. But so you understand. No, I do not use a PC in the field. I have a portable display and keyboard directly connected to the Pi.
At home though, when I am setting things up and messing around on the Pi I like to use VNC into the pi from my PC via an ethernet cable into one of the 2 network ports my desktop has. So it doesn't even go through my home network router, but the internet is shared through the PC.
I think my issue was that the first time I ran the script I stated Yes to making a static IP, but then wasn't sure when to enter at the time. So I continued without entering the any IP. It seemed to recognise it was invalid and moved on with the process.
It did create the 'Wired DHCP Ethernet' connection, but not the second Link Local Ethernet when I did that.
I get no IP address when I connect the Pi to my desktop. How do I set up the network manager to automatically connect to the LAN?
You should be cautious making the adjustments. If you make it too tight, it might bind. You may not even notice until it's out in the cold and things contract. Gearing also has tolerances that you may feel by hand have a different spacing at certain points in the rotation. Try to identify where in the period the gear is tightest by moving the gear with your fingers, and set your adjustments from that spot.
Ordinarily yes. But in poorly tuned cases it can have a noticeable amount of wiggle room, and that's no good. Especially if the balanced load is opposite the driving forces.
ChrisRowland wrote:Why would backlash in the Ra axis matter? The axis is always being driven in the same direction and all that guiding is doing is changing the drive rate , not the direction.
Check for and carefully adjust the backlash in the RA worm gear if you can.
It's that bad as is, but it could probably be improved. Check for and carefully adjust the backlash in the RA worm gear if you can.
I can not provide a complete answer, but as far as I can tell you are one the right path.
A udev rule with the Vendor ID, Product ID, sometimes the serial port number, and the mode is needed. Then a Symlink created.
This script, intended for creating consistent rules for a serial GPS, may offer a little insight.