Feeding Multiple sites with a Pi or other single board computer

[wiedehopf]

The default map doesn't work for you? Available as "live map" on the webinterface?

Regardless, you can find the FA map if you click the FA status link on the main page on the local IP you already found.
You'll see that it leads to http://192.168.2.xxx:8082/

[Anmer]

The default map doesn't work for you? Available as "live map" on the webinterface?

The ADSB.im map works.

Regardless, you can find the FA map if you click the FA status link on the main page on the local IP you already found.
You'll see that it leads to http://192.168.2.xxx:8082/

This wasn't working for me.  Nor was the FR24 local map.

I will now make some more tests following the post by dirkhh.

[Anmer]

I have now run a further test.

I have an RPi connected to my router via Ethernet cable.  It's running a PiAware feed, downloaded directly from FlightAware.  The locally assigned IP address is 192.168.1.72.  When I select the PiAware SkyAware link on my FlightAware My ADS-B page I'm able to view the FA PiAware map.

The RPi also has a feed to FR24.  On entering the 192.168.1.72 IP address into a browser I get to the FR24 Decoder Status page from where I can view the FR24 local map.

If I swap the SD card for one created by ADSB.im, with both FlightAware and FR24 feeds, the RPi still has a locally assigned IP address of 192.168.1.72.  However, both FlightAware and FR24 status pages show an IP address of 178.18.0.5 and 172.18.0.2 respectively, as explained in the earlier messages.

If I now enter 192.168.1.72 into a browser, I get the ADSB.im Feeder Status page.  Selecting Map displays the ADSB.im map.

Selecting FR24 Status displays the attached page.

On my FlightAware status page for the ADSB.im PiAware feed, the PiAware SkyAware option now shows View Live Data.  Selecting this returns nothing as the link is to 178.18.0.5:8080

Regardless, you can find the FA map if you click the FA status link on the main page on the local IP you already found.
You'll see that it leads to http://192.168.2.xxx:8082/

I don't have a FlightAware Status link on the ADSB.im Feeder page (see attached).  However, I can confirm that entering 192.168.2.72:8082 does display my FA PiAware map.

So, in conclusion, creating feeds to FlightAware and FR24 via ADSB.im removes the normal options to view the FlightAware and FR24 local maps.

And it also removes FlightAware's local MLAT data on port 30105.

[wiedehopf]

FR24 does not have a local map, only a status page.

port 31005 is available and has combined MLAT results from the aggregators that are active and provide MLAT results.
FA doesn't provide MLAT results for all planes you receive, it's somewhat random, quite a few planes are censored as well.
Much better to feed lol or live or fi or exchange to get better MLAT results.

Status page for FA is available via the link in the top table, see picture.

[Anmer]

Thanks but FR24 does have a local map, see attached.

Sorry, I meant a Status link similar to that for FR24, see attached.

FlightAware local MLAT is available on port 30105. This doesn't appear to be available from ADSB.im PiAware.

[wiedehopf]

The FR24 map, is that on the fr24 image?
Haven't seen that interface before.


31005 "doesn't appear to be available", how do you arrive at that conclusion?
For me the port is open and provides data.

[Anmer]

The FR24 map, is that on the fr24 image?
Haven't seen that interface before.

Yes.

31005 "doesn't appear to be available", how do you arrive at that conclusion?
For me the port is open and provides data.

I said 30105 not 31005.

FA returns all local MLAT.  Its website may not show all MLAT but port 30105 does.

[wiedehopf]

Well thus the port for MLAT results is different from FA. Yet they are available on 31005.
Didn't quite notice we were talking about 2 different ports with the digits jumbled a bit.


local FA mlat results are indeed censored.
Some military aircraft won't even be in the FA MLAT results, quite a few private aircraft only give MLAT results without the hex / callsign.

[Anmer]

local FA mlat results are indeed censored.

That's not my understanding nor experience.

I will run some further checks.

[wiedehopf]

adsb.im has been updated so that FA links are easier to find on the local adsb.im status page.
Plus there have been optimizations so it runs well on a pi zero 2 with only 512 MB of memory. (though you shouldn't quite check all the aggregator boxes as it will run out of memory then, but you can still enable plenty)



In regards to FA mlat, the issue isn't even only the anonymous results, it's that in areas with many receivers in your area you sometimes just don't get MLAT results despite MLAT working well and the flight being available on the FA site for everyone.
Their system uses a handful of receivers to get a each position, if your receiver isn't used you don't get results for that flight. If it is used, you get positions for 3 minutes (sometimes well beyond receiver range).

For this flight for example, it took FA way longer than the other services to give me MLAT results.

Also i've attached an image of what an anonymized MLAT result from FA looks like, you get a hex starting with an ~ in the FA map you get a corresponding ModeS aircraft in the list that has the correct hex and callsign but no position.

Some aircraft being completely removed from MLAT results i'm pretty sure about but with the unreliability of getting MLAT results, can't be 100% sure. The factors described are more than sufficient for me that i can't recommend relying solely on FA MLAT results.
It's simple enough to feed airplanes.live, adsb.lol, adsb.fi or adsbexchange which usually give good MLAT results.

[Oldfella]

Would be very interest in trying this program (ADSB.im). One question I need to know is can it be used to feed BaseStation.

Thanks in advance.

[Anmer]

Would be very interest in trying this program (ADSB.im). One question I need to know is can it be used to feed BaseStation.

ADSB.im is a utility that helps install selected data sharing feeds onto an SD card for use in some Single Board Computers, such as a Raspberry Pi.

In itself it doesn't feed BaseStation.

But one can use ModeSMixer2.exe to access decoded data from the SBC and "feed" BaseStation.

It's the availabilty of decoded data and ModeSMixer2 that feeds BaseStation, not ADSB.im.

[wiedehopf]

I would not recommend modesmixer on adsb.im.
Edit: misread that, i suppose you're talking about running it on the windows box running basestation. (still shouldn't be necessary unless SBS isn't the right format)

30003 is open on adsb.im and you can just pull SBS.

You can also push / tcp connect from adsb.im using the ultrafeeder arguments on the Expert page.
For example to push SBS to port / ip use this: adsb,192.168.2.81,23500,sbs_out;

[Anmer]

Edit: misread that, i suppose you're talking about running it on the windows box running basestation.

Yes, MMS2 running on Windows.

(still shouldn't be necessary unless SBS isn't the right format)

30003 is open on adsb.im and you can just pull SBS.

So, data in BaseStation format is available on Port 30003 on the SBC?

[wiedehopf]

So, data in BaseStation format is available on Port 30003 on the SBC?

Yeah that's pretty much for every SBC running dump1090-fa or readsb and adsb.im while running readsb in a container exposes the commonly used ports.