Comment on page
If you wish to feed RadarVirtuel, follow the steps below.
The main goal of RadarVirtuel is to collect data about flights. Although RadarVirtuel welcomes feeding stations from all over the world, their differentiator is to collect information about traffic around smaller airports around the world.
The docker image
ghcr.io/sdr-enthusiasts/docker-radarvirtuelcontains the required feeder software and all required prerequisites and libraries. This needs to run in conjunction with
tar1090, or another RAW provider.
- Your name
- The Lat/Lon and nearest airport of your station
- Your Raspberry Pi model (or other hardware if not Raspberry Pi)
- Mention that you will feed using a Docker container.
Inside your application directory (
/opt/adsb), edit the
.envfile using your favorite text editor. Beginners may find the editor
nanoeasy to use:
This file holds all of the commonly used variables (such as our latitude, longitude and altitude). We're going to add our RadarVirtuel Feeder Key to this file. Add the following line to the file:
YOURFEEDERKEYwith the key you received in response to your email.
docker-compose.ymlfile that was created when deploying
Append the following lines to the end of the file (inside the
To explain what's going on in this addition:
- We're creating a container called
radarvirtuel, from the image
- We're passing several environment variables to the container:
FEEDER_KEYcontains the key that you added to
.envas per the instructions above
SOURCE_HOSTindicates where to get the RAW data from
RV_SERVERis the address of the RadarVirtuel server where your data will be sent. Please do not change this unless you're specifically instructed to
ON(meaning: show lots of information in the docker logs) or
OFF(show only errors in the docker logs)
- Enabling receiving MLAT RAW data and sending latitude, longitude and altitude from the .env file
- The mounted volumes make sure that the container will use the same timezone as your host system
docker compose, we also want to update the configuration of the
ultrafeedercontainer, so that it generates MLAT data for piaware.
docker-compose.ymland make the following environment value is part of the
ULTRAFEEDER_CONFIGvariable to the
To explain this addition, the
ultrafeedercontainer will connect to the
radarvirtuelcontainer on port
30105and receive MLAT data. This data will then be included in any outbound data streams from
Once the file has been updated, issue the command
docker compose pull radarvirtuel && docker compose up -din the application directory to apply the changes and bring up the
radarvirtuelcontainer. You should see the following output:
ultrafeeder is up-to-date
piaware is up-to-date
fr24 is up-to-date
pfclient is up-to-date
We can view the logs for the environment with the command
docker logs radarvirtuel, or continually "tail" them with
docker logs -f radarvirtuel. The logs will be fairly unexciting and look like this:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[cont-init.d] executing container initialization scripts...
[services.d] starting services
[radarvirtuel/radarvirtuel][Tue May 4 17:06:32 EDT 2021] RadarVirtuel was started as an s6 service
[radarvirtuel/imalive][Tue May 4 17:06:32 EDT 2021] Started as an s6 service
Most log messages are self-explanatory and have suggestions on how to trouble-shoot your issue. Here is some additional information that may help:
- Sometimes, the logs may show error messages that it cannot connect to your
SOURCE_HOST. If these messages show every few seconds, you have a problem (read below). If there are no new messages after a bit, it means that your station finally connected to the
SOURCE_HOST. This connection delay is often caused by RadarVirtuel becoming "up and running" before
ultrafeederdo. This will fix itself within less than a minute.
- This message keeps on scrolling and it doesn't stop after a while. In that case,
ultrafeedercannot be reached.
- If you configured
tar1090, there's nothing else to configure. Make sure the
tar1090container is up and running and is receiving data!
- You see log messages about the Feeder Key being incorrect. This is quite self-explanatory: check your feeder key.
- You see messages about not being able to reach the RadarVirtuel Server. This may be a temporary outage. If the message consists for several hours, please contact [email protected] to see if there's something going on.