[WORKING] New ADSBExchange base image v1.0

Thanks for the help, sd card burned and pi already running...
Next challenge is set up custom port for feed adsbx with data that come from flightfeeder which is running in the same lan.
Is possible to connect to my pi trough ssh?
With default port (should be 22) I'm unable to connect so I think the port is wrong.
Thanks again!

 

Not using the default port for ssh. Try this:
ssh [email protected]<ip address> -p 3226

 

obviously you're right, I've found this reply in change log on the first post. So thanks for the help!

But I think I need more help to reach my goal.
I don't understand which file I have to edit to start adsbx listening my flightfeeder.
I guess the right file is "adsbexchange-dump1090_maint.sh" but I'm not sure of this.

But first of all, is possible to feed dump1090 from net??

 

What are you trying do to? adsbexchange-netcat_maint.sh does the port forwarding from the Pi local dump1090 to adsbexchange servers

This is all configurable in the adsb-config.txt

Are you saying you have a flightfeeder somewhere and you need the pit to listen to it? Seems that you are ... if the PI has no SDR

adsbexchange-dump1090_maint.sh is where you might have to change dump1090 into --net-only mode and use as a forwarder - this keeps dump1090 from looking for a SDR

Forward your output port of the flightfeeder to dump1090 input beast port ...

Being the FA locks down the flightfeeder - I have no idea how you can do this .. I don't think you can tell dump1090 to connect to something itself but only listen

You might be able to do ..

It is possible to use Dump1090 just as an hub using --ifile with /dev/zero as argument as in the following example:

./dump1090 --net-only

then

socat TCP:<flightfeederip>:30005 TCP:localhost:30001

30001 is the raw input port for dump1090
I'm guessing flightfeeder output port is 30005 - I have no idea - it is a blackbox from FA



"-----------------------------------------------------------------------------\n"
"| dump1090 ModeS Receiver %45s |\n"
"-----------------------------------------------------------------------------\n"
"--device-index <index> Select RTL device (default: 0)\n"
"--gain <db> Set gain (default: max gain. Use -10 for auto-gain)\n"
"--enable-agc Enable the Automatic Gain Control (default: off)\n"
"--freq <hz> Set frequency (default: 1090 Mhz)\n"
"--ifile <filename> Read data from file (use '-' for stdin)\n"
"--iformat <format> Sample format for --ifile: UC8 (default), SC16, or SC16Q11\n"
"--throttle When reading from a file, play back in realtime, not at max speed\n"
"--interactive Interactive mode refreshing data on screen. Implies --throttle\n"
"--interactive-rows <num> Max number of rows in interactive mode (default: 22)\n"
"--interactive-ttl <sec> Remove from list if idle for <sec> (default: 60)\n"
"--interactive-rtl1090 Display flight table in RTL1090 format\n"
"--raw Show only messages hex values\n"
"--net Enable networking\n"
"--modeac Enable decoding of SSR Modes 3/A & 3/C\n"
"--net-only Enable just networking, no RTL device or file used\n"
"--net-bind-address <ip> IP address to bind to (default: Any; Use 127.0.0.1 for private)\n"
#ifdef ENABLE_WEBSERVER
"--net-http-port <ports> HTTP server ports (default: 8080)\n"
#endif
"--net-ri-port <ports> TCP raw input listen ports (default: 30001)\n"
"--net-ro-port <ports> TCP raw output listen ports (default: 30002)\n"
"--net-sbs-port <ports> TCP BaseStation output listen ports (default: 30003)\n"
"--net-bi-port <ports> TCP Beast input listen ports (default: 30004,30104)\n"
"--net-bo-port <ports> TCP Beast output listen ports (default: 30005)\n"
"--net-ro-size <size> TCP output minimum size (default: 0)\n"
"--net-ro-interval <rate> TCP output memory flush rate in seconds (default: 0)\n"
"--net-heartbeat <rate> TCP heartbeat rate in seconds (default: 60 sec; 0 to disable)\n"
"--net-buffer <n> TCP buffer size 64Kb * (2^n) (default: n=0, 64Kb)\n"
"--net-verbatim Do not apply CRC corrections to messages we forward; send unchanged\n"
"--forward-mlat Allow forwarding of received mlat results to output ports\n"
"--lat <latitude> Reference/receiver latitude for surface posn (opt)\n"
"--lon <longitude> Reference/receiver longitude for surface posn (opt)\n"
"--max-range <distance> Absolute maximum range for position decoding (in nm, default: 300)\n"
"--fix Enable single-bits error correction using CRC\n"
"--no-fix Disable single-bits error correction using CRC\n"
"--no-crc-check Disable messages with broken CRC (discouraged)\n"
#ifdef ALLOW_AGGRESSIVE
"--aggressive More CPU for more messages (two bits fixes, ...)\n"
#endif
"--mlat display raw messages in Beast ascii mode\n"
"--stats Print stats at exit\n"
"--stats-range Collect/show range histogram\n"
"--stats-every <seconds> Show and reset stats every <seconds> seconds\n"
"--onlyaddr Show only ICAO addresses (testing purposes)\n"
"--metric Use metric units (meters, km/h, ...)\n"
"--gnss Show altitudes as HAE/GNSS (with H suffix) when available\n"
"--snip <level> Strip IQ file removing samples < level\n"
"--debug <flags> Debug mode (verbose), see README for details\n"
"--quiet Disable output to stdout. Use for daemon applications\n"
"--show-only <addr> Show only messages from the given ICAO on stdout\n"
"--ppm <error> Set receiver error in parts per million (default 0)\n"
#ifdef HAVE_RTL_BIAST
"--enable-rtlsdr-biast Set bias tee supply on (default off)\n"
#endif
"--html-dir <dir> Use <dir> as base directory for the internal HTTP server. Defaults to " HTMLPATH "\n"
"--write-json <dir> Periodically write json output to <dir> (for serving by a separate webserver)\n"
"--write-json-every <t> Write json output every t seconds (default 1)\n"
"--json-location-accuracy <n> Accuracy of receiver location in json metadata: 0=no location, 1=approximate, 2=exact\n"
"--dcfilter Apply a 1Hz DC filter to input data (requires lots more CPU)\n"
"--help Show this help\n"
"\n"
"Debug mode flags: d = Log frames decoded with errors\n"
" D = Log frames decoded with zero errors\n"
" c = Log frames with bad CRC\n"
" C = Log frames with good CRC\n"
" p = Log frames with bad preamble\n"
" n = Log network debugging info\n"
" j = Log frames to frames.js, loadable by debug.html\n",

 

simply (more or less) I'm trying to use dump1090 without an rtlsdr dongle and to do this the only way is to feed dump1090 with data already present on my net (which comes from my flightfeeder for example...)
So I'm looking for a way to make it possible... I'm not a newbie for this kind of things, but for sure I'm not an electronic engineer!

(ps I'm sorry for my bad english)

 

Ok.

You need to add --net-only to dump1090 adsbexhage-dump1090_maint.sh - that prevents it from looking for SDR

Then you need to figure out how to get the output port beast from flight feeder to the pi.

If you are using my image then .. socat should work
socat TCP:<flightfeederip>:30005 TCP:localhost:30001

If 30005 is output port of flight feeder

for input on pi dump1090 .... maybe 30001 or maybe 30004 .. depending on format

"--net-ri-port <ports> TCP raw input listen ports (default: 30001)\n"
"--net-ro-port <ports> TCP raw output listen ports (default: 30002)\n"
"--net-sbs-port <ports> TCP BaseStation output listen ports (default: 30003)\n"
"--net-bi-port <ports> TCP Beast input listen ports (default: 30004,30104)\n"
"--net-bo-port <ports> TCP Beast output listen ports (default: 30005)\n"
"--net-ro-size <size> TCP output minimum size (default: 0)

You need to test it first via ssh and looking at the local dump1090 map or dashboard

You need to set MLAT no in the config-adsb.txt .... probably .. I don't know if FA mlat forwards back to FA on flight feeder output port - if it does then FA might yank you flightfeeder; because they don't like their data being used on any other adsb website. Just a warning there - we got threatened - that's why we have our own mlat.

Then if all that works ... create a flightfeder.sh file that has similar format
remove <flightfeederip> and put ip of flight feeder on your network

#!/bin/bash

while true
do
socat socat TCP:<flightfeederip>:30005 TCP:localhost:30001
sleep 30
done

This is all speculation .. but the idea

You need to set dump1090 to --net-only
You need to forward flightfeeder output to Pi
You need to create a forward script on the pi

Leave adsbexchange-netcat_maint.sh unchanged - that is how dump1090 output port gets fed to feed.adsbexchange.com

As bonus points -- pick a custom port to see if you are actually feeding data to adsbexchange.com

https://www.adsbexchange.com/how-to-feed/custom-feed-how-to/

 

Flightfeeder get out data and mlat results in many formats as below:

• 30002 for raw/unparsed messages in AVR format
• 30003 for parsed messages in BaseStation format
• 30005 for raw/unparsed messages in Beast binary format
• 30105 for multilateration results (only) in Beast binary format (for FlightFeeders, the device must be running 7.x or newer software)
• 30106 for multilateration results (only) in extended BaseStation format (for FlightFeeders, the device must be running 7.x or newer software)

So I can (could) forward potentially every kind of data (including merged data) to the PI where adsbx image is running.

And as FlightAware says on its website:
"Can I share data from the FlightFeeder with other sites?
Sure! FlightAware encourages the sharing of all available ADS-B data for maximum collaboration and sharing within the community. However we ask that MLAT data not be used for commercial purposes."

This means that I'm not violating their policy

I'm trying to set up a bat to run dump1090 on a local win machine only for try purpose... the bat is set up as follow:
dump1090.exe --net --net-only --interactive
socat TCP:192.168.1.50:30005 TCP:localhost:30004
pause

30005 is beast port out from flightfeeder
30004 is beast port in for dump1090
but nothing appear on "--interactive" screen...

 

That's interesting the FA publishes that but then makes behind the scenes threats of lawsuits to more than one adsb site. We were told to absolutely not to use FA data to adsbexchange.com or else.

I though you said you had a Pi? That looks like you are trying to use windows.

Also dump1090 30004 is listening port - you need to forward traffic to it from the 30005 flight feeder.


ssh into pi
pi adsb123
sudo nano /boot/adsb-config.txt
Confirm MLAT yes in PI adsb-config.txt

ctrl+o to write
ctrl+x t0 exit

nano /home/pi/adsbexchange-dump1090.sh
Add --net-only to dump1090 in adsbexchange-dump1090_maint.sh

ctrl+o to write
ctrl+x to exit


sudo rebbot now

ssh into pi again

Then in terminal:

sudo socat TCP:<flightfeederip>:30005 TCP:localhost:30004

Point web browser to IP of pi and see if you have traffic on the map or dasboard, if yes - SUCCESS! If no, try something else.

If yes,
make script like I said above and add to rc.local

sudo nano /etc/rc.local

/home/pi/flightfeed.sh &


inside flightfeed.sh

Code:

#!/bin/bash
while true
do
socat socat TCP:<flightfeederip>:30005 TCP:localhost:30004
sleep 30
done

EDIT: WORKS SEE POST

 

SUCCESS!

10.10.10.110 30005 is my feeder (your FA flightfeeder)
10.10.10.109 is local dump1090 install (your pi feeding adsbexchange)

booom! works!

both socat and nc commands tested.

My initial instructions are correct! I doubt myself for no reason!


in your case .. do as I say ..

shh into pi feeding adsbexchange

nano /home/pi/adsbexchange-dump1090_maint.sh

set dump1090 arg --net-only in adsbexchange-dump1090_maint.sh

reboot pi

shh into pi feeding adsbexchange

sudo socat TCP:<IP FEEDER>:30005 TCP:localhost:30004

Replace <IP FEEDER> with your flight feeder IP

works.

Then make startup script like I said ... works when reboot! GREAT SUCCESS!

you must make script to do on boot or no worky when disconnect or reboot .. so you must ....


sudo nano /etc/rc.local

/home/pi/flightfeed.sh &

nano /home/pi/flightfeed.sh

inside flightfeed.sh

Code:

#!/bin/bash
while true
do
  socat socat TCP:<flightfeederip>:30005 TCP:localhost:30004
  sleep 30
done

 

Well done! The map and dashboard show correctly data and positions so I can say you was right XD

Now I have to work on script but since this moment I know that everything works fine!
Thanks a lot for your efforts!!

 

You are welcome! Enjoy!

 

Got a problem. Feeding multiple sources on the same Raspberry Pi running this image causes Grafana to break.

I've installed this image and all was well. I managed to install feeds to Flight Radar, Plane Finder, Radar Box and 360radar (I think). Everything is fine up til this point. I can see data on maps on my local machine from my local IP, and I can see data feeding the ADSBx Custom Feed page as well as everyone else.

The data is also uploading to Flight Aware, and I can see the data coming in on their website, and all data is appearing in Grafana. However I cannot access the data locally, via localhost:8080

The problem occurs if I then update PiAware and dump1090. After updating, I can see data on localhost:8080 correctly, and everything else continues to feed normally...

But then Grafana stops updating. Everything appears as N/A and the map at the bottom says "problem fetching data from dump1090".

Now obviously installing the PiAware dump1090 is what is breaking this. Either I can see data in Grafana but not on localhost:8080, or can see data on localhost:8080 but nothing in Grafana.

How can I get the PiAware dump1090 to feed Grafana??

I had a look at the above re socat, but couldn't get that to work. I'm not that proficient in Linux so "explain like I'm 5" would be useful.

 

Where do I find this script? I've used the Find command via SSH and can only see something in local/bin/ but it's not a configurable file nor does it show any ports.

Also, please do explain it to me like I'm an idiot. That might help me

 

Thanks Marcin. Attached is the file.

Just to be clear where I am at the moment... I have re-imaged my back-up so the attached htop screen grab is BEFORE I have installed the PiAware package. I will now install the package and upload a 2nd screen grab. I have also redacted some location details, just for peace of mind.

 

Okay, since reinstalling the backup image back onto the card, I have now run the PiAware update for dump1090 and attached in the htop screen grab.

I notice some of the differences, the main one being the original install without the updated dump1090 was running "dump1090-mutability", and that's the version where Grafana worked. The second screen grab shows "dump1090-fa" running, and this is when Grafana stops working.

So just trying to figure out either how to point Grafana to the dump1090-fa data, or somehow remove that and re-install dump1090-mutability and point PiAware at that data stream. If that makes sense.

 

Attached is a grab showing dup1090exporter with redacted location co-ords.

Grafana runs (no red error box appearing), but it is not interpreting any data. All graphs show N/A and the embedded map at the bottom of the page shows "problem fetching data from 1090".