I don't see anything either ... Want to try changing the port? Maybe try 51118 Do you remember where you changed the port? You'll have to edit the config file and reboot the pi. Fill out the form and Dan can get it named and send you the port. For now trying changing the port .. I assume that's what your talking about .. the custom feed name not the mlat-client name for the feeder ..
edited the attached - just changed it from 51008 to 51118... OMG - it works ! EDIT: Form filled. Thanks!
Oh yeah you're setup long before the setup script someone made .... nice ... having to edit the shell scripts While you're plugging around in there .... check the mlat script! There is probably some numpty connected to that other port but not sending data .... only one person/feed can connect to each custom port
You've got a nice range on the feed. I've been trying to get a hold of the Gatwick Museum or the Gatwick Aviation Society and see about putting up a feeder there. Nobody returns my emails. Makes me sad.
So once we get you setup with a custom feed name - it will start making range plots and all kinds of stuff
No ports need changed in the mlat-client. The custom feed server is just hooking into the other infrastructure - MLAT servers are the same overloaded pigs eating electrons.
Yeah - it's a good loft mount 1090mhz aerial with the blue fa dongle - I'm in a competition with a feeder on FA, who keeps getting marginally more hits than I do! I also have a RPI2 here at the same location - would it help (MLAT) if I set that up as a feeder as well. Stats arent quite as good as the RPI3, but still pretty good.
Strange but true! I modified netcat /home/pi/adsb-exchange/adsbexchange-netcat_maint.sh connection established but indeed no traffic on map. Port 30005. Maybe port number has to be changed? I wonder if the custom feed named ports are overlapping with those maybe. I dunno. Changing the port worked I think for him!
Nah it needs distance between each MLAT client, in theory up to like 400 nautical miles. MLAT more or less calculates a probability curve based on a bunch of receivers and the signal strength of the ICAO that's transmitting. It's CPU hungry and no real way to do it efficiently.
Code: #!/bin/sh #while true # do # sleep 30 # /bin/nc 127dot0dot0dot1 30005 | /bin/nc feed.adsbexchange.com 30005 # /bin/nc 127dot0dot0dot1 30005 | /bin/nc feed.adsbexchange.com 51014 # done Modified file.
Remove all # except of 5th line, replace dot with . (security issues ). 53000 ports are OK, feeding from VRS works fine.
Everyone hates VRS <joke?, maybe .... >, 53XXX only accept VRS output. I wonder if the no traffic one some of these is people trying to push VRS data to the raw - plugging up the port .. doing no good. Someone last night got his IP blocked for sending so much data it crashed the server. Technically didn't crash it .. just put the CPU at 100% .... all the time
I hope not my IP. Data are only from my feeders (no circular feeding). Anyway, tutorials and "howto's" should be improved. I needed quiet long time to make it running, how much newbies will need??? Now your turn James, write something... for people without any experience.
BOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!! Now you are SSH Wizard! PS I don't think you need to feed to main port 30005 and custom port ... custom also goes to main feed via aggregator @James My Debian station is aggregating most of my feeders and sending compressed VRS data. Today i just wanted to help by testing new config.
