I get the impression the client forwards the BEAST data directly to their server.
(I checked in iptraf-ng and the bytes count was quite similar to my forwarding of 30005 beast data to my netonly dump1090 on a second computer)
It seems to be accurately reporting in journalctl as well.
OpenSky for me uses around 1.3 GB per day. (16 kByte/s or 128 kbit/s so not really a drain on my upload of roughly 30 000 kBit/s)
So if you are limited regarding data at all just don’t use it.
Planeplotter seems to be using around 1 kByte/s for me. (Checking the log view on the local interface)
That’s around 86 MB per day.
FA reports around the same 1.5 kByte/s in journalctl for the mlat client.
Not sure about the rest but i would guess 1kByte/s or less.
Overall with limited data you just won’t use opensky
It’s just so much more data.
I use the FR24 web page when I am looking at locations other than my own, it has good bookmarks. FA’s aircraft departure and arrivals is great for notifying a number of people of travel arrangements.
(1) Virtual Radar is very good for Windows Laptop + Data Stick or WiFi.
If Data Stick / Wifi / Wired internet is not available then adsbScope is a practical choice, though its map is simple land-water outline and country boundries, but serves the purpose.
(2) For mobile device like Android phone + data, the best was FlightAware’s Flight Scanner.
However after Google has introduced use of Google key, and as there is no provision in Flight Scanner to add the key, a horrible map with watermark is displyed now.
This is how Flight Scanner looked before Google made it compulsory to use a key:
.
(3) Currently the best Android App is Avare (ADSB Reciever by HIZ LLC). It has both ES 1090 Mhz and UAT 978 Mhz, but runs any one of these two at a time, no simultaneous operation
EDIT:
Above App is available at Google Play. It requires
driver “RTL2832U Driver by Martin Marinov”, which is also available at Google Play.
It displays Google map without a key, plus does NOT require data or wifi.
Need to clarify a comment I made in previous post.
I did say Virtual Radar was great for mobile devices, what I meant was the display that Virtual Radar produces is great for mobile devices. Virtual Radar itself (it is a server) needs to run on a Windows or Linux machine. Appreciate many will be aware of this but some new users may not.
I think I managed to do the same by installing the FR24 image, then SSH into teh Pi and run the commands to get the FA system installed. It appears to work as both show as online, however the FA syetm at the bottom of the My ADS-B page shows it hasn’t seen me for 4 days?
I’m not exactly familiar with the fr24 image. Using the piaware image and installing fr24 is probably a better way to go.
Anyway no matter which way to go, the file /etc/fr24.ini
needs to look like this:
If you select dvbt as a receiver it will stop dump1090-fa from working.
Anyway after changing the configuration like that, execute the following commands:
I also changed to Beast-tcp, however after reboot, it changed back to dvbt. I even tried changing it in the web setting page for FR24 without any luck.
After getting it going you can install FR24.
Even if you are using a DVB-T USB Stick, in FR24 settings, DO NOT choose Receiver “DVB-T” , as this will screw up feeding to flightaware again
Choose Receiver ModeS Beast (USB/Network) and enter the ip 127.0.0.1 and port 30005.
On Pi24 image, I have successfully installed Piaware data feeder (package install). I did NOT install dump1090-fa. Instead I used setting “receiver = dvbt”. Both the fr24feed and Piaware used the output from fr24feeder’s onstalled dump1090-mutability ver 1.14.
Try adding --net in the field “Process Arguments” in IP-OF-PI:8754/settings.html
I have used etcher to put the FA image piaware-sd-card-3.6.3 on it. It went on ok, have put it in the Pi and started, the Pi is no longer showing up on my network. It is plugged in via Ethernet and Wifi wasn’t configured.