AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: Millsey on April 11, 2018, 06:33:57 AM
-
I have two RPi's currently feeding ADSB data, one to FR24 and one to RB24. I wondered if I could feed both from one RPi, so downloaded the img for FR24 and installed on an SD card for a spare RPi. I then added the RB24 software from https://www.radarbox24.com/raspberry-pi/guide and followed the install path for an existing DUMP1090 running. However RB24 just refuses to run, I wonder if the FR24 software has a block built in ? I can see the dump1090 output @ :8080 on my local network, so I know data is available.
Anyone done this sucessfully ?
John
-
Yes indeed, I'm feeding 4 site from each of my 3 Raspberry Pi's
I was guided through the setup here on the forum. Take a look at this thread:
https://www.airnavsystems.com/forum/index.php?topic=16971.0
-
@Millsey
Most likely wrong settings.
post output of following commands:
(1) cat /etc/rbfeeder.ini
(2) cat /etc/fr24feed.ini
I have Pi24-2.0.0 img from FlightRadar24 written to my microSD card, and have installed rbfeeder, flightaware, and planefinder feeders on it. All work perfectly well.
Below are outputs from my RPi. Compare with your outputs.
cat /etc/rbfeeder.ini
[client]
network_mode=true
log_file=/var/log/rbfeeder.log
key=C E N S O R E D
sn=EXTRPI000008
[network]
mode=beast
external_port=30005
external_host=127.0.0.1
cat /etc/fr24feed.ini
receiver="dvbt"
fr24key="C E N S O R E D"
bs="no"
raw="no"
logmode="1"
procargs="--net --net-bi-port 30104 --lat 43.xxxx --lon -79.xxxx --gain 42"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="no"
mlat="yes"
mlat-without-gps="yes"
NOTE:
When FR24 feeder is set to "receiver=dvbt" mode, it installs and uses dump1090-mutability v1.14. The entries in field "procargs" then control dump1090-mutability v1.14.
Adding --lat and --lon of receiver will show on map range circles at 100, 150, and 200 nm, centered at receiver location.
Adding --net-bi-port 30104 will enable MLAT feedback planes from Flightaware to be displayed on map
Adding --gain xx will control gain of Dongle through dump1090-mutability v1.14
-
Thanks Allocator and abcd567 for your swift response.
I will post command outputs as requested once I have a chance to get time - probably at the weekend now.
abcd567 - you have also helped me to learn more arguments in procargs - thanks
-
The post on the form here suggests setting the receiver to (4) Mode-s Beast and this works for me.
https://forum.flightradar24.com/threads/10232-How-to-Install-dump1090-mutability_1-15-dev-on-RPi
Is it better to select (1) DVBT USB) to get other options via procargs?
Step 4.1 - Receiver selection:
1 - DVBT Stick (USB)
-----------------------------------------------------
2 - SBS1/SBS1er (USB/Network)
3 - SBS3 (USB/Network)
4 - ModeS Beast (USB/Network)
5 - AVR Compatible (DVBT over network, etc)
6 - microADSB (USB/Network)
7 - SBSx via Basestation (localhost:30006)
Enter your receiver type (1-7)$: 4
-
The post on the form here suggests setting the receiver to (4) Mode-s Beast and this works for me.
https://forum.flightradar24.com/threads/10232-How-to-Install-dump1090-mutability_1-15-dev-on-RPi
The above instruction are for those who have installed dump1090-mutability v1.15~dev and therefore will NOT use FR24 supplied dump1090-mutability v1.14.
In case of @Millsey, he mentioned he is using the FR24 supplied dump1090. The settings "receiver=dvbt" I have shown in my above post are for this situation, as the FR24 supplied dump1090 will now use the DVB-T dongle.
The setting "Beast, 127.0.0.1:30005" are required when the user has installed a decoder software (dump1090) of his own choice, and DVB-T will be used by that software. FR24 feeder will get data from that decoder software on port 30005, format beast.
Is it better to select (1) DVBT USB) to get other options via procargs?
If you select DVBT (USB), FR24 feeder will start its own dump1090 at startup and grab the DVBT. Your dump1090-mutability will become orphan - no dongle left for it.
The FR24 feeder starts/stops and passes these arguments at startup ONLY to the dump1090 provided by FR24.
The FR24 feeder has no control over user installed dump1090, and does NOT start/stop it or pass any process arguments to it.
The FR24feeder in this case only "listens" to the data from user installed dump1090.
User has to make configuration settings of his dump1090 by editing the file /etc/default/dump1090-mutability.
-
.
How to Feed Data to Multiple Sites - A Brief Guide (https://forum.flightradar24.com/threads/11137-How-to-Feed-Data-to-Multiple-Sites-A-Brief-Guide)
.
-
Thanks for the update and the clarification of the use of dump1090 and the USB stick receiver.
I'm also feeding to 360Radar now making it 5 feeds from the one Rpi. Installation of the 360Radar on top of the existing 4 feed installation was simple and straightforward, only requiring the MLAT and ADSB install using the instructions on their website.
I just have't got enough monitors to watch all the feeds :)
-
Thanks abcd567 for the guide, but even more confused by which bits to ignore. I have just asked FR24 for another key, so I can experiment further without taking my 24/7 feed down. I'll then be able to try the various options suggested to find what works for me. Rest assured I will doubtless be in more trouble and posting here again soon
-
...but even more confused by which bits to ignore.
You dont have to. Simply give following 2 commands and post their outputs. Hopefully after seeing the outputs, I will be able to tell you the remedy.
Note: Remove the actual values of fr24 and rb24 keys when posting.
cat /etc/fr24feed.ini
cat /etc/rbfeeder.ini
-
Ok, abcd567, so should I do the following steps on a new card:
Burn FR24 img and run setup (will get new FR24 key)
Add extra Dump1090 args: --net --net-http-port 8080
Download RB software: sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
Then do I add: sudo rbfeeder --set-network-mode on --set-network-host ‹host› --set-network-port ‹port› --set-network-protocol ‹beast/raw› --no-start
Sorry but this is where I am getting confused with all the talk of Beast protocols and ports
My current RPi feeding FR24 is set:
RAW data: No
SBS Feed: No
Decoded data: Yes
From this I can view Dump1090 on my browser as well as through VRS
Idiot guide would be much appreciated
-
@Millsey
In my previous posts, I have twice asked you to post output generated by two commands (cat /etc/fr24feed.ini and cat /etc/rbfeeder.ini). Instead of doing so, you again asked for a solution of your problem.
This is equivalent to refusing to take blood test, urine test, and x-ray prescribed by your doctor, and insisting that the doctor diagnose the disease and prescribe medication without these tests.
-
I was intending to start with a clean slate and start again from scratch on a new SD card. I have every intention of posting as requested the outputs from the .ini files, but thought it would be a good idea to install both FR24 and RB24 correctly on the new card first. As I have two working feeds on two Rpi's I might just leave well alone and stick with them. Just seemed a good idea to run all from one.
Sorry I have seemed to have angered you.
-
Millsey, just take your time to work through the instructions at the link posted by abcd567 and concentrate initially on getting dump1090 mutability working. That's half of the battle. You can then concentrate on adding one feed at a time and checking that that feed is actually being received by viewing the appropriate online page. I've setup 3 Rpi's using the guide. Once I had one working I copied the image and flashed that to the other two SD cards. I did then struggle a bit to edit the ini/conf files so that I had 3 lots of feeds and not 3 Rpi's all feeding the same, but I got there in the end.
I do understand abcd567's frustration. He's trying to help and you might be very close, but if you don't answer his questions then he might as well not bother :0
He's been very patient with me and has answered my silly questions and I wouldn't have got my setup running without his help. Stick with it and let us know how you get on - and do take notes as you go through the process, it really helps at a later date.
-
@Millsey:
For Existing microSD card
I cannot tell you anything unless you post output of following commands, as most likely these no longer are at default settings.
cat /etc/fr24feed.ini
cat /etc/rbfeeder.ini
For NEW microSD card
FR24 feeder:
Setting you have mentioned is OK.
You did not mention the MOST IMPORTANT setting "Receiver: DVBT"
RB feeder:
You have asked: "Then do I add: sudo rbfeeder --set-network-mode on --set-network-host ‹host› --set-network-port ‹port› --set-network-protocol ‹beast/raw› --no-start"
You do NOT have to issue any command for rbfeeder. It is by default set to get data from a running dump1090 (in your case the dump1090 provided by FR24 feeder).
After installation of rbfeeder, you have to go to following page and complete claim procedure.
https://www.radarbox24.com/raspberry-pi/claim
-
Ok, just installed FR24, working fine and Dump1090 on local IP :8080
receiver="dvbt"
fr24key="xxxxxxx"
path="/usr/lib/fr24/dump1090"
bs="yes"
raw="no"
logmode="0"
procargs="--net --net-http-port 8080"
logpath="/var/log/fr24feed"
mlat="yes"
mlat-without-gps="yes"
But get the following from rb24 result:
pi@raspberrypi:~ $ cat /etc/rbfeeder.ini
cat: /etc/rbfeeder.ini: No such file or directory
pi@raspberrypi:~ $ sudo rbfeeder --showkey
sudo: rbfeeder: command not found
pi@raspberrypi:~ $ sudo systemctl restart rbfeeder
Failed to restart rbfeeder.service: Unit rbfeeder.service not found.
This is the same as where I got to last weekend, which prompted my first question. The install log is as follows:
pi@raspberrypi:~ $ sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
--2018-04-13 18:48:00-- http://apt.rb24.com/inst_rbfeeder.sh
Resolving apt.rb24.com (apt.rb24.com)... 104.25.103.118, 104.25.104.118, 2400:cb00:2048:1::6819:6876, ...
Connecting to apt.rb24.com (apt.rb24.com)|104.25.103.118|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1753 (1.7K) [text/x-sh]
Saving to: ‘STDOUT’
- 100%[===================>] 1.71K --.-KB/s in 0s
2018-04-13 18:48:00 (30.6 MB/s) - written to stdout [1753/1753]
Get:1 http://mirrordirector.raspbian.org/raspbian stretch InRelease [15.0 kB]
Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.3 kB]
Get:3 http://repo.feed.flightradar24.com flightradar24 InRelease [13.0 kB]
Get:4 http://mirrordirector.raspbian.org/raspbian stretch/main armhf Packages [11.7 MB]
Get:5 http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable armhf Packages [605 B]
Get:6 http://archive.raspberrypi.org/debian stretch/main armhf Packages [145 kB]
Get:7 http://mirrordirector.raspbian.org/raspbian stretch/contrib armhf Packages [56.8 kB]
Get:8 http://archive.raspberrypi.org/debian stretch/ui armhf Packages [28.2 kB]
Fetched 11.9 MB in 24s (496 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
dirmngr is already the newest version (2.1.18-8~deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 84 not upgraded.
Executing: /tmp/apt-key-gpghome.XARqrDQIeF/gpg.1.sh --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 1D043681
gpg: keyserver receive failed: Cannot assign requested address
Hit:1 http://archive.raspberrypi.org/debian stretch InRelease
Hit:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Hit:3 http://repo.feed.flightradar24.com flightradar24 InRelease
Get:4 https://apt.rb24.com rpi-stable InRelease [3,812 B]
Ign:4 https://apt.rb24.com rpi-stable InRelease
Get:5 https://apt.rb24.com rpi-stable/main armhf Packages [499 B]
Fetched 4,311 B in 3s (1,338 B/s)
Reading package lists... Done
W: GPG error: https://apt.rb24.com rpi-stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F2A8428D3C354953
W: The repository 'https://apt.rb24.com rpi-stable InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
rbfeeder
0 upgraded, 1 newly installed, 0 to remove and 84 not upgraded.
Need to get 78.1 kB of archives.
After this operation, 204 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
rbfeeder
E: There were unauthenticated packages and -y was used without --allow-unauthenticated
!!!! IMPORTANT !!!!
By default, RBFeeder is configured to connect to your local dump1090 instance (localhost,
port 30005). If you want to use a USB RTL-SDR dongle instead, please run this command:
sudo rbfeeder --set-network-mode off --no-start
Then, restart the daemon:
sudo systemctl restart rbfeeder
After a few seconds, RBFeeder will connect to the AirNav servers and you can view your
sharing-key with this command:
sudo rbfeeder --showkey
If you already have a sharing-key from preivous a installation, you can set the same
key using this command:
sudo rbfeeder --setkey ‹your sharing key›
Installation finished.
Looks like the RB24 software failed to install but I have no idea why not ??
I need to go out now, so I'll check back for your answers first thing in the morning (UK Time)
-
@Millsey
After running the bash script, if rbfeeder is not installed, run following commands and it will be installed
sudo apt-get update
sudo apt-get install rbfeeder
The installation process will start.
After few minutes, it will stop and display:
"WARNING: The following packages cannot be authenticated!
rbfeeder
Install these packages without verification? [y/N]"
Type "y" and press Enter key. The installation process will continue and complete the installation in a minute or two.
Now go ahead with claim: https://www.radarbox24.com/raspberry-pi/claim
See this thread:
Bake a Pi (https://www.airnavsystems.com/forum/index.php?topic=10201.msg205861#msg205861)
-
@abcd567
Getting there now, but now no feed to RB24 on the same Rpi as FR24. Installed current key to RB24 but got this:
pi@raspberrypi:~ $ sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxxxxxx
[2018-04-14 09:11:01] Starting RBFeeder Version 0.2.6 (build 20180313082038)
[2018-04-14 09:11:01] Using configuration file: /etc/rbfeeder.ini
[2018-04-14 09:11:01] Network-mode enabled.
[2018-04-14 09:11:01] Remote host to fetch data: 127.0.0.1
[2018-04-14 09:11:01] Remote port: 30005
[2018-04-14 09:11:01] Remote protocol: BEAST
Error opening the listening port 32008 (Beast TCP input): bind: Address already in use
pi@raspberrypi:~ $ cat /etc/rbfeeder.ini
[client]
network_mode=true
log_file=/var/log/rbfeeder.log
key=xxxxxxxxxxxxxxxxxxxxxxxxx
sn=EXTRPI006014
[network]
mode=beast
external_port=30005
external_host=127.0.0.1
[mlat]
FR24 is as follows:
receiver="dvbt"
fr24key="xxxxxxxxxxxxxxx"
path="/usr/lib/fr24/dump1090"
bs="yes"
raw="no"
logmode="0"
procargs="--net --net-http-port 8080 --lat xx.xxxx --lon x.xxxx"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="no"
mlat="yes"
mlat-without-gps="yes"
Maybe turn off bs="yes" in FR24 ?? If so what do I edit ?
-
To edit config of fr24
Method 1
Open file in nano editor
sudo nano /etc/fr24feed.ini
Change bs="yes" to bs="no"
After editing, Save (Ctrl+o) and close (Ctrl+x)
Then restart fr24feed
sudo systemctl restart fr2feed
Method 2
In browser go to page ip-of-pi:8754/settings.html
Change settings, then click "Save" button, then click Restart button.
Both these buttons are at bottom right of settings page.
This is my setting which works perfectly well with (1) fr24feed (2) rbfeeder, (3) flightaware feeder (4) planefinder feeder, and (5) VRS on my Windows Desktop.
Please note that saving the settings on "ip-of-pi:8754/settings.html" actually saves these in file /etc/fr24feed.ini
(https://s20.postimg.cc/edi2d7ki5/fr24feed_setting_using_integral_dump1090-mutability_v1.14.png)
-
@abcd567
Thanks for all your patience, that has done the trick, just burning img of card now for backup and then I'll take both existing RPi's offline to replace with the single one which is the faster RPi2 as well.
Millsey
-
@Millsey
Glad to know your problem is solved. The problem was beneficial to you, as you learned that settings are saved in files /etc/fr24feed.ini and /etc/rbfeeder.ini
Just now realized that the rbfeeder was already running when you gave the command
"sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxxxxxx"
This command not only sets the key, but also tries to start rbfeeder. As rbfeeder was already running, you got the error message "Error opening the listening port 32008 (Beast TCP input): bind: Address already in use".
Check if rbfeeder is healthy and running by following command
sudo systemctl status rbfeeder
If it is running, it will give output like this
● rbfeeder.service - RBFeeder Service
Loaded: loaded (/lib/systemd/system/rbfeeder.service; enabled; vendor pre Active: active (running) since Sat 2018-04-14 06:28:01 EDT; 1h 7min ago
Main PID: 450 (rbfeeder)
Now give following single-worded command, and you will again get the same error message "Error opening the listening port 32008 (Beast TCP input): bind: Address already in use"
rbfeeder
.
-
@abcd567
Thanks for the heads up, but it's fine thanks, I'm seeing my usual feed on RB24, oh just remembered I need to change my FR24 sharing key now .....
-
@abcd567
Just did it all again on my earlier RPi B+ with a new SD and all up and running 100%.
Just one question, can you have more than one net process arg ? I am running --net-http-port 8080 can I also add the line you use --net-bi-port 30104 or is only one arg allowed ?
Millsey
-
can you have more than one net process arg ? I am running --net-http-port 8080 can I also add the line you use --net-bi-port 30104 or is only one arg allowed ?
- You can add as many arguments as you need.
- Try to see map at http://<IP of Pi>/dump1090/gmap.html
- No need for --net-http-port 8080. You can see map at http://<IP of Pi>:8080 without this argument.
- The argument --net is essential to feed data to other sites like RadarBox24. Keep it.
- Please see this post
How to Feed Data to Multiple Sites - A Brief Guide (https://forum.flightradar24.com/threads/11137-How-to-Feed-Data-to-Multiple-Sites-A-Brief-Guide?p=92413&viewfull=1#post92413) >> Scroll down to "FR24 FEEDER CONFIGURATION".
[/list]
-
@abcd567
Great, thanks for the info, guess my port 8080 is left over from my first forays with Dump1090 years ago ?
But how about external access, I have my router set to forward port 8080 ?
Mind you unless I can understand how to add the Google Api key I cannot see it now anyway :-(
Millsey
-
But how about external access, I have my router set to forward port 8080 ?
In dump1090-mutability v 1.14 installed by FR24feeder installation, BY DEFAULT the port 8080 redirects to /dump1090/gmap.html which is Map page. Hence you do NOT need to add process argument --net-http-port 8080
Because of this redirect, you can see the map on your Desktop on same Local Network as Pi, as well as from an external network.
You can test this by deleting proc arg --net-http-port 8080 and saving the settings, then check:
(1) From local network < IP OF PI >:8080
(2) From local network < IP OF PI >/dump1090/gmap.html
(3) From external network http:// < YOUR-INTERNET-IP > with and without :8080 at the end.
I have done this test by first port forwarding 8080 in my router. For me it worked without :8080 at the end of address, IP only. When I added :8080 at the end of IP, it said "Unable to connect".
Mind you unless I can understand how to add the Google Api key I cannot see it now anyway :-(
You have to add Google API Key in file gmap.html
1. Give following command to open file gmap.html in editor nano:
sudo nano /usr/share/dump1090-mutability/html/gmap.html
2. Above command will open file gmap.html for editing. ADD script line shown in red, and in it replace YOUR_KEY_HERE by your actual Google Key.
3. Save changes (Ctrl+o) and close file (Ctrl+x).
4. Reboot Pi (not necessary but preferable).
5. Go to map page. If it gives problems, try Clear browser cache (Ctrl+Shift+Delete) and browser force reload (Ctrl+F5).
<html>
<head>
<meta charset="utf-8"/>
<link rel="stylesheet" type="text/css" href="style.css" />
<link rel="stylesheet" href="http://code.jquery.com/ui/1.10.3/themes/smoothness/jquery-ui.css" />
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/jqueryui/1.10.3/jquery-ui.min.js"></script>
<script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?sensor=false&libraries=geometry"></script>
<script type="text/javascript" src="config.js"></script>
<script type="text/javascript" src="planeObject.js"></script>
<script type="text/javascript" src="script.js"></script>
<script type="text/javascript" src="coolclock/excanvas.js"></script>
<script type="text/javascript" src="coolclock/coolclock.js"></script>
<script type="text/javascript" src="coolclock/moreskins.js"></script>
<script type="text/javascript" src="//maps.googleapis.com/maps/api/js?key=YOUR_KEY_HERE&libraries=geometry"></script>
<title>DUMP1090</title>
</head>
-
@abcd567
Odd - when I added the Api key script line it refuses to save the script saying the file is read only ?
Millsey
-
Odd - when I added the Api key script line it refuses to save the script saying the file is read only ?
The file opens as "read only" if you dont use sudo at the start of the command.
sudo nano /usr/share/dump1090-mutability/html/gmap.html
-
Thanks but I did copy your first command which started sudo as well, I was also trying to install another private tracking site with similar problems and this guy suggested I run fsck.mode=force as he said it looked like my file system was read only, but I didn't fancy that, so I just rebooted the RPi and hey presto it has now accepted the APi key and the external IP is working through my 4G connection as you suggested to try.
Weird
Millsey
-
...so I just rebooted the RPi and hey presto it has now accepted the APi key and the external IP is working through my 4G connection as you suggested to try.
Weird
Millsey
Weird, yes, but I am glad finally your problems are solved and you are up and running. :)
Pi do misbehave sometimes, and often gets right when rebooted.