wvreeven wrote: As it happens I ordered an XU4 recently and it is due to arrive next Monday. I'll inform you about it as soon as I have it working which probably will be Monday night (CEST)
rlancaste wrote: The odroid is very nice, my 64 bit script works well with that. I can't use it really with my camera due to the issue of SBIG not releasing a 64 bit arm version of their driver, but other than that the odroid c2 works great. I have had way more problems with trying the Rock64. But despite having them, i am still imaging with the raspberry pi.
I do bet there are some things you can delete to answer the question, and when i first started in 2016, I did try to delete as many as I could, but I found that it was a lot of extra effort to do so, so now I just ignore the extra stuff.
I had already deleted libreoffice and thunderbird before posting this. And I think I saw some of the effects from it. I started getting errors out of nowhere, and sometimes trying to connect via VNC just didn't work right. So....back to square one with a fresh install. Now I know
El Corazon wrote:
Here's a link to a recent post ( www.indilib.org/forum/embedded-indi/3185...t-connect.html#24517 )where I summed up some of my experience with the Pi3. An additional piece of info, not covered here, is the importance of the read and write speed of the SD card. Not all Class10 cards are the same. I use the 128GB Samsung EvoSelect microSDXC UHS-I card ($40). That works very well in the Pi3. I have used another Class10 SD card with similar read and write speed (supposedly!) that slows my Pi3 down to snail sprinting speed (you don't want to go there). The card IS important. Also, I put a Swap file on an external USB 2.5" HD, which I also use for storing captured video. But the most important thing is the I/O on the SD card. You have to use the fastest one you can get. A speedy wireless connection is also important.
Lets say I only want to use the RPI for my AP needs, utilizing Rlancaste's awesome Setup Script. After that, is there a list of things I can get rid of to free up storage space? Libreoffice and Thunderbird are 2 very obvious ones that come to mind. Just wondering what else lurks in the install that is just bloat when it comes to what we're using these RPI's for.
I ordered a serial to usb cable from Amazon and made my own shoestring-style USB2EQ5 cable. I still have my Lubuntu OS running on the Raspberry Pi. Everything connected just fine. No issues I could see (Other than my lack of knowledge in actually operating Kstars/Ekos).
Telescope control was as expected, I could slew the scope around with Kstars or manually with the scope control window. I could lock back on the Sun (I'm indoors, was just making sure it all worked) and sync and track it.
Some day I'd love to figure out why the bluetooth dongle can't connect on the RPI, that will probably drive me insane. Seriously.
But for now, I'll deal with one additional cable on the mount and consider this a win. Now to learn how to actually use Kstars to do my imaging
Thanks to everyone who helped, if anyone ever comes up with additional info or suggestions on getting the BT2EQ5 working I'd love to hear it. I'm off to Kstars school in the meantime!
I've tried a few different flavors of linux on my laptop and all can pair and connect and run Ekos/Kstars with very little trouble. Mint, Ubuntu Mate, Lubuntu and even Peppermint all do just fine, just like my windows machine. At least I have that going for me, I can always leave that laptop outside and VNC into it with my windows machine.
Raspberry Pi is a whole different story. I've tried Ubuntu Mate and Lubuntu on 2 different Raspberry Pi 3's, and nothing will allow me to connect. Bluetooth pairing works, binding rfcomm works via command line, and /etc/rc.local, but I get the same error I've documented previously in this thread. Every single time, no matter what steps I take to detect, pair and assign a serial port, all goes well up to the actual point where Indi tries to connect to the Shoestring dongle.
I'm going to try and find another RPI OS that may work, and in the meantime I'm just going to take my linux laptop back to Mint, it was my favorite flavor and I ran it for years. As for the raspberry pi 3 issues, it's beyond me. Doesn't make a lick of sense, and the same issue cropping up on 2 different machines and 2 different operating systems is mind boggling, especially with people claiming they get the exact same hardware to work on their machines.
Ihoujin wrote: I got this tip from the INDI Support FAQ
You have read and write permissions to the port. In some Linux distros, this is not the default setting. Under Ubuntu, you need to add your user to the dialout group:Then you must restart your PC for this to take effect and try again.sudo adduser $USER dialout
rlancaste wrote: I am not an expert on conky by any means. I found a tutorial on how to set it up and configure it online and I then incorporated it into the script because I liked it. Currently I'm not having problems with it, but maybe it just happened recently. I do know that there is a new format for the configuration file, but the older format was working for me still. If you have any suggestions on how I should update it let me know.
I've used the script about a million times with Ubuntu Mate on my Raspberry Pi3 while trying to track down why my bluetooth dongle doesn't work correctly. The script is great, I can't say enough good things about it!
I used it again last night on the RPI3 but this time with Lubuntu. It seems that conky is not starting on it's own. When starting manually, conky give syntax errors but it does start. Apparently there is a new conky config file format. I've found a script that converts the config file to the new format but haven't tried it yet. Are there any other suggestions?