Question concerning feeding

adsbexchange-netcat_maint.sh

If you have a GUI on the Linux machine, then just use gedit or whatever text editor ..

Reboot and it will be sending to your custom port .. If you just want to test it ..

socat -u TCP:localhost:30005 TCP:feed.adsbexchange.com:51389

You may need to

sudo apt install socat



https://customglobal4.adsbexchange.com/VirtualRadar/desktop.html#

51398 seems open right now ... there's only a few .. I'm going to go through and cleat out the ones with no data and get them caught up. I also might setup another custom feeder server ...

 

Ok on radioshack for coax source. I'll use your Linux info James. I'm leaving for the local hardware store now to purchase some home-made antenna material. Thanks to you both for good advice and have a good evening.

 

Update. I registered the port you mentioned... 51389 and everything seemed fine. Installed an antenna outside... many more 'craft. Here's the problem... dump1090 in linux now crashes frequently and stops decoding. So, I'm temporarily rebroadcasting to ads-b exchange on another (windows) pc on the default (41000) setup through the program Virtual Radar Server. Is there a way to direct my feed to end up on my "home port"? I would have to select a format other than compressed VRS to use "my" port, but not sure which format in the given drop-down box selection. Is it do-able?

 

Easier to figure out why linux is crashing than deal with VRS.

Are you sure dump1090 is crashing? how did you setup that Pi?

 

Not using a Pi, James. Dump1090 installed on a pc running Lubuntu. Starting dump1090 in Terminal ... ./dump1090. That opens up another window with 'craft data. Feeds data fine into Exchange until dump1090 window goes "blank" ... no data in box at all. Restarting again but it keeps crashing. I'm going to try re-installing dump1090 again tomorrow. Hope that works. Time for bed. Will look tomorrow for your reply. Thanks.

 

Was using Malcolm Robb fork. Uninstalled it and am now running the "old code" mutability version. Saw a newer mutability-fa fork but didn't use it. It's been running for about 3 hrs now, so I'll keep an eye on it.

 

I'm not sure. I got it from github.com/mutability/dump1090. It says it's old code and to use the mutability-fa instead, but I used it anyway (and so far, it's still running).

 

Local browser no longer works to pull up map. Doesn't respond to localhost:8080 anymore. I'll have to look into it later and get back to you.

 

mutability 1.15 needs it's own webserver ... see the tutorial for NGINX here .. STEP 3 ...

https://www.adsbexchange.com/forum/threads/install-dump1090-fa-from-base-raspbian-image-ssh.623994/

 

To be honest, I'm pretty happy with running dump1090 on the little pc in terminal mode while feeding Exchange and it not crashing. It's been up all day now. I really don't need a local GUI on that pc anyway, and can see the output of my feed in the Exchange browser on my main pc if I need to. I'll read up on the comments above and get to it in the next couple days. Hope you both have a Happy New Year!

 

are you just executing dump1090 in the terminal or via bash script that will restart it if it crashes ..

 

I am just executing dump in a terminal and letting it run and feed Exchange. That's all I expect it to do on that pc. I would like to have dump1090 start from a script and auto-restart from a crash. I'm not that advanced enough in Linux to write a script, nor where to place the script/file once it is written.

 

It's easy. You are running on Linux already, so ..

send me your command line you a launching dump1090 with ..

 

Ok. In terminal I cd to the dump1090 directory, then issue this command and hit the enter key:

./dump1090 --interactive --net --net-ro-size 500 --net-ro-rate 5 --net-buffer 5 --net-beast --mlat --lat (my lat) --lon (my lon) --interactive-ttl 20 --gain -10 --no-fix
pause

 

Let's learn some *nix .. well bash ..
http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_09_02.html

while <condition>; do <commands> done;

So if I wanted to print 'echo' every 5 seconds ...

while true; do echo 'echo'; sleep 5; done;

Not real useful.

Say we want to run a command and if it exits .. wait .. then rerun the same command .. let's put it all together!

while true; do ./dump1090 --interactive --net --net-ro-size 500 --net-ro-rate 5 --net-buffer 5 --net-beast --mlat --lat (my lat) --lon (my lon) --interactive-ttl 20 --gain -10 --no-fix; sleep 5; done;

But this is .. not a great way .. if the terminal window closes or the machine restarts ..

if we create a file .... in the same directory as dump1090 binary ..

nano run_dump1090.sh

Code:

#!/bin/bash
# This script keeps dump1090 alive!

while true;
do
./dump1090 --interactive --net --net-ro-size 500 --net-ro-rate 5 --net-buffer 5 --net-beast --mlat --lat (my lat) --lon (my lon) --interactive-ttl 20 --gain -10 --no-fix;
sleep 5;
done;

CTRL+O .. that writes it out ...

And we need to make it executable ...

chmod +x run_dump1090.sh

Then we can cd to the file and ..

./run_dump1090.sh


You should also do the same with socat to feed ADSBx with because every time the proxy server restarts or the daily reboot happens, our server closes the connection and socat exits .. thus you won't be feeding ADSBx.

I assume you might be thinking dump1090 feeds ADSBx automatically .. it does not ..

You need to send traffic from your local dump1090 to ADSBx ..

socat -u TCP:localhost:30005 TCP:feed.adsbexchange.com:30005

You guessed it ... inside a while loop ...

socat is not installed by default.

sudo apt update
sudo apt install socat