ADSB.im

In general, the basic setup should be sufficient for most use cases. The bare minimum of information is entered on the Basic Setup page, aggregators can be selected on the Data Sharing page.

You can backup the settings as well as the history of statistics on the Backup page. Click one of the three Backup buttons and store the zip file on your computer. You can backup just the configuration, include the graphs, or include the full history of data. If needed, you can later go to the Restore page (for example after installing a newer Feeder Image on your system) and restore the data. Once you upload the zip file you will be shown all files and folders that differ from the running system and can choose which ones to restore.

On the Map Options page you are offered a few ways to adjust what you see when showing the live map

• By default, the ADSB Feeder Image shows the best open data guess for the route information of the planes shown in the tar1090 user interface. If you don't want this information, you can turn it off here.
• If you want the theoretical range of an ideal antenna at your location shown in the tar1090 user interfacem, you can use HeyWhatsThat to create an ID that will be used to provide that visualization.
• If you want to reset the actual range outline of the planes that you have received data from, there's also an option to do that here. Note that the range outline by default always tracks the last 24 hours of data, so things will reset on their own after a day.

On the Data Sharing page you are adjusting how your data is shared with aggregators.
By default, MLAT privacy is not enabled, which allows (a rough estimate of the location of)your site to be shown on typical MLAT coverage maps. Turning this on informs the aggregators that you would like to opt out of having your data shown on such maps.
The rest of this page is used to select the aggregators you want to feed. The first group are the semi-anonymous aggregators that don't require any authentication. Below them are the various commercial and non-commercial aggregators for which you need some kind of sharing key or similar. For many of them, getting those key is automated, others require some extra steps -- see the help texts in the UI.

On the SDR setup page you are offered some additional options, some of which depend on your hardware.

• By default, automatic gain is enabled for your SDR. You most likely don't want to change this if you are using an airspy SDR, but with traditional RTL SDRs this can be useful if the manual auto gain process is getting stuck or is taking too long to find an acceptable value
• If you are using an LNA or some other device that requires power via bias-T (assuming your SDR supports this setting), you can turn this on here.
• If you have more than one SDR connected to your feeder SBC, there will be a selection below this to assign each SDR its role. This is commonly needed when supporting both standard ADS-B at 1090MHz as well as the US-only UAT at 978MHZ.

On the Expert page you will find some more advanced settings

• In some very unusual circumstances you may want to be able to add extra arguments for the Ultrafeeder, e.g., if you are feeding a "standard aggregator" that accelpts beast input but for whatever reason isn't supported by the web UI.
• While in most circumstances you shouldn't need to to access the adsb feeder SBC directly, if this is something you want to be able to do, here is where you enter the public key of an ssh key-pair which will allow you to log in as root.
• Conversly, if you want to slightly reduce the attack surface of your SBC (for example if it is installed on someone else's premises), you can remove some obvious attack vectors that would allow someone else to take over your feeder. This is not the same as truly hardening the image; you should assume that someone with access to the hardware will be able to remove the µSD card which will allow them to get access to the system.
• There are also options that allow you to shutdown or reboot your SBC. Please note that there are several scenarios where an SBC will not successfully reboot (or not turn of power on shutdown). Please test this capability before relying on it.
• The feeder can be set up to update its base OS, the containers that implement the feeder functionality as well as the feeder application (i.e. the web UI that controls the device) automatically.
• You can also trigger the feeder app updates manually from this page.
• Finally, you can add your feeder system to a ZeroTier or Tailscale global area network in order to be able to access it remotely. Enter the network ID here (you have to set this up at the ZeroTier website, first), or connect to your pre-existing Tailscale network.

As the title indicates, the options here are generally for people who are somewhat more familiar with the setup of a feeder system, so they are not fully explained in this guide.