Some feeders not showing on MLAT display

I periodically check http://www.adsbexchange.com/coverage-2/ to see how my four feeders are doing. Yesterday I saw two of them were missing. This morning (almost 0600 local time) I see three of the four are now missing. All also feed FA (only) and the latter shows them to be productive. (I use FA only as a "means to get started," to monitor the feeders, and as an easy means to reboot, shut down, etc. The feeders are located in the states of Georgia and Ohio.) I'm wondering what's happening here. Are the feeders not "making it" or is the MLAT depiction not authoritative? Any thoughts?

 

ADSBx custom images default to privacy mode yes - so no map dot.

Hard to tell if you are using FA image, recent FA updates have broken how MLAT client works.

https://www.adsbexchange.com/forum/threads/flightaware-3-6-3.624199/

MLAT map is generated every hour, sometimes it doesn't get all the feeders.

If you install zerotier.com on your feeders like we do with ADSBx custom image then montoring, remotely logging in, etc is a breeze.

Beyond that I can't help much without being able to login to the feeders.

install

curl -s https://install.zerotier.com/ | sudo bash

then

sudo zerotier-cli join c7c8172af18c605f
sudo zerotier-cli status
sudo zerotier-cli listnetworks


Send me that output.

 

OK. TU. Yes. I've seen that post. Actually, it is the three that are running 3.5.3 imaged with the ADSBX image that seem "broken." The one running 3.6.3 seems to be OK. I have no permitted any FA updates since the original installations.

I'll start working on zerotier -- but it'll be difficult since woof the feeders are 800 miles away.

I'm wondering if I furnish the public IP addresses associated with the feeders if there is a way to check on your end to see if they are "alive?"

 

Maybe. I'd have to ask Dan (Dan is on family vacation until next week), there was some reverse ssh in the 3.5.3 images but I think it had to be enabled on install.

Are you sure there are problems with them? Other than just not showing on the map dot.

Do they sent to custom ports or 30005?

 

Hi James. I'll try to send you a spreadsheet/PDF which has more information. The feeders are all on port 30005 - no custom ports.
I checked again this morning after returning from a 3 day trip and I see 3 of the 4 feeders are still now shown on http://www.adsbexchange.com/coverage-2/ -- the page that used to give me a useful depiction of MLAT performance. - Rick

 

Hi Rick, maybe you have something on the postings on
https://www.adsbexchange.com/forum/threads/feed-not-showing-on-map.624271/page-2
Joop.

 

Hi Joop. Yes, you're right -- thanks. It appears that yesterday someone started another thread with the exact same issue I raised rather than joining the threat I originated.

Looks like there are at least two separate issues here, unfortunately.

Rick

 

I think this MLAT issue is the probably same issue.

Anyone using 3.5.3 FA ADSBx combo image is not going to work when it reboots. It won't get an altitude from Google API and therefor MLAT client won't start.

No map pin. No sync matrix. No MLAT.

It will still feed ADSB data to ADSBx. The only that won't works is the MLAT client.

 

The directory structure is the same. So if they use the git download then it will overwrite the net and mlat scripts, that removes the issue.

 

git just gets the setup.sh .. the rest of the files are created by the sudo ./setup command

so if they are in /home/pi and run git clone
it will pull a setup.sh into adsb-exchange
then they cd adsb-exchange
sudo ./setup.sh

and are none the wiser ...

 

Which for 99% users won't be an issue. The setup script method works best. I might just keep this method instead of creating a specific FlightAware image we have to maintain.

 

I wish we had a flightaware style, plug in and go. But that requires that the Pi is talking to FA and FA web ui sends commands to it over TCL/TCK to configure it.

Which is a big undertaking to develop something like that here. We'd need some sort sort of server routing program and a client on the Pi.

Lot's of stuff to maintain and keep from breaking.