×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Documentation/tips for installing KStars/EKOS on an Odroid-N2.

  • Posts: 460
  • Thank you received: 69
While not trying to lead you astray...
I've attempted to document my process for installing KStars/EKOS on an Odroid-N2 based largely on Ron Lancaste's excellent AstroPi3 installer script.
Installing KStars on an Odroid N2
Any comments / suggested improvements are welcome.

Thanks
3 years 2 months ago #66865

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

  • Posts: 294
  • Thank you received: 54
Nice write-up Jerry. Thanks for those who may want to try the ODroid route. One can also consider the newer 4GB ODroid C4 as a smaller (RPI size) and cheaper alternative to the N2/N2+ as, from benchmark, it is somewhat better than the RPI 4.

If I may add my comments (re: ODroid), I would like to add that I am running ODroids N2 and C4 for my 'transportable' observatory and telescope setup. The observatory runs a subset of the INDI suite (Dome Scripting Gateway, Weather Radio, Watchdog, GPS, DIY Flip Flat) on the C4, and the telescope runs the mount, cameras, UPB, astrometry, etc... on the N2, in a distributed INDI setup that I run from inside my house via NoMachine.

A big advantage of the ODroids I use is that they run on 12 volts with standard 5.5/2.1mm power connectors so, no need for voltage converters or special adapters to power them. Both have been working flawlessly, in our cold canadian winter, in < -20°C (-4°F) temperature for many hours, contrary to my RPI based observatory security camera that would not boot when it is -10°C or below. Another plus for the ODroids is that they generate less localized heat that the RPI as they have substantial heatsinks, making heat management one less thing to worry about.

Thanks again, from a "statisfied ODroid customer" :)

Gilles
The following user(s) said Thank You: Jerry Black
3 years 2 months ago #66880

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

Time to create page: 0.206 seconds