Which ADSB.im Installation Method Should I Choose?

Updated

Choose the Single Board Computer (SBC) image unless you have a specific reason not to. ADSB.im's own documentation calls it the first choice: it is the most tested, typically the easiest to use, and has the fewest pitfalls. Pick DietPi if you want a lighter, more managed Linux base on supported hardware, and pick the plain Linux route only if you are comfortable administering a system yourself or need to run the feeder on hardware the images don't cover.

The three methods at a glance

Method Best for Effort What you manage
Single Board Computer image Most people, first-time feeders Lowest Almost nothing; flash and boot
DietPi Users who want a lean OS with a menu-driven setup Low to moderate Some OS-level choices
Linux Advanced users, non-standard hardware, existing servers Highest The whole stack

All three end up running the same ADS-B Feeder Image software, so the difference is in setup and maintenance, not in what the feeder can receive.

Single Board Computer image (easiest)

This is the path ADSB.im tests most and recommends when you are unsure.

  1. Start with one of the supported single board computers. Most people use a Raspberry Pi; several other boards are supported.
  2. Add an SDR radio dongle and an antenna.
  3. Download the matching SD-card image and write it to an SD card.
  4. Boot the SBC and wait. Depending on the model and image this usually takes a few minutes, but in some cases 15 to 20 minutes.
  5. If you have wired Ethernet, or once you have configured WiFi, open http://adsb-feeder.local. If mDNS does not work on your network, use my.adsb.im, which redirects to your new feeder.

Expected result: a running feeder reachable from a browser on your local network, ready to plot aircraft on your own map and share to aggregators.

Common snag: if you planned to use WiFi and could not configure it while writing the SD card, the image creates a WiFi hotspot named adsb.im-feeder that you connect to in order to finish setup.

DietPi (easy)

Choose this when you want a smaller, more controlled operating system underneath the feeder and are willing to make a few more decisions during setup. It sits between the fully prebuilt SBC image and a manual Linux install: less hand-holding than the image, far less work than building the stack yourself. It still assumes supported hardware and an SDR dongle plus antenna.

Linux (more advanced)

Choose this if you are already running a Linux machine you want to reuse, if your hardware is not covered by the supported board list, or if you want full control over updates and services. You take on the operating system, dependencies, and ongoing maintenance yourself. If you are new to ADS-B feeding, this is the option most likely to cost you an evening of troubleshooting.

What the feeder can receive

The image is not limited to aircraft. Beyond ADS-B it supports AIS for tracking ships, Sonde for weather balloons, and ACARS/VDL2/HFDL for data transmissions from aircraft to ground stations. Each area has its own aggregators and communities, but the setup approach is the same across them.

You can plot aircraft on your own map and share to aggregators including adsb.lol, Fly Italy Adsb, TheAirTraffic, adsb.fi, sdrmap, 1090MHz UK, ADS-B Exchange, ADSBHub, HPRadar, airplanes.live, AVDelphi, FlightAware, FlightRadar24, OpenSky Network, Plane.watch, Plane Finder, Planespotters.net, AirNav Radar, Radar Virtuel, and more.

How to decide

  • You just want it working this weekend: SBC image.
  • You want a leaner OS and don't mind a menu-driven setup: DietPi.
  • You have spare Linux hardware, unusual hardware, or want full control: Linux.
  • You are unsure: the SBC image, per ADSB.im's own guidance.

The hardware requirements are the same in every case: a supported board or Linux host, an SDR radio dongle, and an antenna.