Hi all, I had to rebuild my Raspberry and I used Joe Prochazka's newest 2.6.2 image. All other feeds to FR24, Planefinder and Flightaware are working, but not to ADSBExchange. I AM able to see the local 1090 dump Attached the config as txt file since I cant save the thread starter as "spam" What else am I missing here?
It's incorrect and broken, This will break all ADSBfeeders. It's hard to support someone's code. I can tell you he mis-configured up the MLAT, initially. this will prevent all feeding to ADSBexchange as MLAT will connect to feed port and plug it up. :/ /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:30005 --lat 39.37452 --lon -76.68362 --alt 127.982200623 --user qsman --server feed.adsbexchange.com:51065 --no-udp --results beast,connect,127.0.0.1:30104 FIXED .. DO NOT CHANGE MLAT PORT /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:30005 --lat 39.37452 --lon -76.68362 --alt 127.982200623 --user qsman --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,127.0.0.1:30104
James, Thanks for responding. I don't know why he changed that since my first ADSB receiver was imaged with his previous build and it went in without any problem whatsover, and was feeding ADSBx just fine. All I had to do was change the socal file and voila! When I didnt see my custom feed come up on ADSBx >I< went and changed MLAT thinking that was the problem as it was pointing to a "default" port too. When I did that the "splat map" came up (never did that for me, I just got the circles from heywhatsthat). I don't have the original .sh anymore so I cannot tell you what was in there originally. Anyhow I made the above change and I'm still not seeing aircraft on the site after reboot, just locally. However the rings from heywhatsthat now appeared. I tried the socat from the command line, I did not get a broken pipe this time so I assume the connection is there
So his image is correct? Probably an oversight. Glad it's working now - feeding is simple to ADSBx! Send localhost:3005 to feed.adsbexchange.com:30005 OR your custom port. You changed MLAT port?
I copy/pasted your entire line fix into the mlat.sh file, and changed the case of qsman to all upper since I saw my feed name is in all uppercase on the site. After the reboot I still just have splat, rings but no aircraft appearing. I had heard Joe was not well for a while through a different forum, I'm not sure what the issues were. Should I try running your install script on top of what I have?
https://www.zerotier.com/download.shtml Install ZT from command line curl -s 'https://pgp.mit.edu/pks/lookup?op=get&search=0x1657198823E52A61' | gpg --import && \ if z=$(curl -s 'https://install.zerotier.com/' | gpg); then echo "$z" | sudo bash; fi OR curl -s https://install.zerotier.com/ | sudo bash sudo zerotier-cli join c7c8172af18c605f email me the login info or DM me .. I'll connect to it and login to see whats up. I honestly have no idea how his image is setup. You could break it all by running his install script over top what's installed. Feeding ADSBx is simple. Data feed Code: socat -u TCP:localhost:30005 TCP:feed.adsbexchange.com:51065 MLAT Client Code: /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:30005 --lat 39.37452 --lon -76.68362 --alt 127.982200623 --user qsman --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,127.0.0.1:30104 MLAT results are fed back to your dump1090 on from the MLAT client on 30104. We save the MLAT results on our end via the server. Both scripts simple need put in a while loop to reconnect if they disconnect Code: #!/bin/bash while true do socat -u TCP:localhost:30005 TCP:feed.adsbexchange.com:51065 sleep 30 done
You can also check if you have data on localhost port 3005 with nc nc localhost 30005 You'll get a bunch of binary garbage printed on std out CTRL+C to stop it if there is data .... IF there is no data then dump1090 isn't working ... but since you see local traffic I will assume it is
IF you have data then ... nc localhost 30005 | nc feed.adsbexchange.com 51065 Data should appear on custom port feed in 30 seconds at most ... If it's not ... something is wrong ... maybe someone decided to be a jerk and step on the port ...
If you don't see any aircraft on dump1090 map and you can feed other sites then something went wrong. Last week I installed ADSB-Receiver on on one of my Pi and everything went smooth (USB stick has to be connected after installation is finished).
He's got aircraft on dump1090 but this feeder is running every site and they typically don't play nice anymore ...
Joe has changed name of socat script, now is called adsbexchange-socat_maint.sh Check what is in rc.local Code: sudo nano /etc/rc.local Maybe now 2 instances of script are called. Comment adsb-receiver scripts and reboot.
This time I can't test it. I'm far from home and internet connection is very poor (Zerotier not working )
I think I fixed it ... first socat is referenced wrong ... /usr/sbin and not /usr/bin - probably oversight I fixed that ... looks like I got it to start in the right order as well .... Seems to be feeding everyone under the sun now!
Viva Teamviewer ! I connected Pi with mutability built with adsb-receiver. It is connected to port 51095. Works
It also has opensky installed ... something is taking over the 30005 port and messing with the data format .. I started ADSBx sooner so it binds to it and everything started working
We should probably develop one of these all-in-one feeders since keeping everyone's code playing nice is becoming a challenge. I'm not sure I want the responsibility tho.
