×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Remote choices

  • Posts: 4
  • Thank you received: 0
I've recently retired and one of my big retirement projects is to get my astronomy equipment back into service and taking data. I'm almost exclusively interested in photometry of eclipsing binaries and exoplanet transits. In the past I have done sessions entirely manually and I am quite excited to take advantage of all the planning/execution features in KStars/Ekos. I have a Raspberry pi that I plan to use as the main controller, but I have a question: what are the considerations in choosing to use the pi as a Indi server and running KStars on the laptop vs running everything on the pi and using the laptop as a remote display? I had assumed that the less the pi has to do the better, but does that actually hold true?

I have a GPS dongle and want to set the time and location from it. If you are running Indi server on the pi and KStars on the laptop which computer should the dongle be on?

Thanks for any help,
DanZ
5 years 1 month ago #34917

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375

Replied by Radek Kaczorek on topic Remote choices

There are many pros and cons to both approaches, however in my opinion there's a major pro in favor of all-on-rpi approach - any problem with network connection between PC running KStars and RPi running INDI server will terminate the session (which is managed on KStars side).
GPS dongle should be connected to a device running INDI server i.e. Raspberry Pi
The following user(s) said Thank You: Daniel Zaharevitz
5 years 1 month ago #34922

Please Log in or Create an account to join the conversation.

  • Posts: 1957
  • Thank you received: 420

Replied by Wouter van Reeven on topic Remote choices

I second Radek's recommendation. Please note that particularly plate solving can be quite slow on a Raspberry Pi mostly due to only 1 Gb of memory. If this is a limitation then you may want to consider buying a mini pc or other small computer with at least 4 Gb of memory. Make sure that it can run Ubuntu Linux though.
The following user(s) said Thank You: Daniel Zaharevitz
5 years 1 month ago #34931

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140

Replied by AstroNerd on topic Remote choices

I disagree with running it all on the rpi, as it’s must not fast enough and that alone will give issues, with just 1gb of RAM, it will struggle...I have tried it..
I now use the other option and must use the rpi an a server, and remote into it from another PC, but I also use something use an network cable between rpi and my PC so no wireless connection to worry about, but I find the hotspot on my rpi fine and get no issues that way either... :)
The following user(s) said Thank You: Daniel Zaharevitz
5 years 1 month ago #34943

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 0

Replied by Daniel Zaharevitz on topic Remote choices

Thanks for the feedback from everyone. I will definitely try both ways, but I am leaning toward running running the pi as an INDI server. Since I have to luxury of being able to make hardwired connections (at least in my home setup) I will try to take advantage. Sorted out some astrometry.net issues yesterday and now I just need some clear skies to start collecting some real photons.

DanZ
5 years 1 month ago #34983

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic Remote choices

There are ways to get around the memory limitations or the Raspberry Pi. The first is to create a swap partition on the SD card. Second, I also use ZRAM. ZRAM uses a little processing power to effectively increases memory capacity through compression. I have not experienced any insufficient memory issues since making these changes.
5 years 1 month ago #34991

Please Log in or Create an account to join the conversation.

Time to create page: 0.541 seconds