Hey guys. First let me express my appreciation for putting all this together, very cool. I have now burned through about 4 hours trying to simply feed your service from my PiAware feed that's been running all year. It's 3.6.3-bpo8+1 (from the Skyview upper right corner). I followed what appeared to be your simple instructions to run scripts to add your feed, but when done it's kind of frustrating to have no way to know if it's working, no way to see your data being fed as you can with PiAware Skyview. Initially, I could see the two scripts in htop so I thought it was running, but there was no other way to verify. I tried going to this map (customglobal4 adsbexchange com VirtualRadar desktop html) and zooming into my home by IAD airport, and could easily see that my Skyview showed many planes but your map didn't. So after much digging and poking around these forums I managed to find a suggestion to see if some service was running, and found accidentally that neither your socat or mlat-client programs were installed. I don't even see anywhere in your instructions where you tell us about any of this, seems kind of important. At this point I deleted the old installation and reinstalled your scripts, this time seeing that briefly some garbled (some kind of screen error) error messages about socat and mlat-client not being installed, but then these disappeared and at the end it acted happy, I guess I missed this fleeting info the first time. At this point after more forum reading I did another Raspian update/upgrade/reboot and reinstalled your scripts a 3rd time, noticing that it took much longer, this time monitoring /var/log/syslog and seeing that it seemed to go through some failure iterations and then seemed to succeed. Now I have more of your processes running in htop, seems like it should be working. But...I still don't seem to be feeding your map. I have no other way to validate that I'm feeding. Can you please help? Hmmm....uploading htop and syslog to you, noticing there are log messages that don't look happy, no clue what it means. Scott
sudo apt install socat hit f5 on htop ... to group by thread .. Setup should be a 30 minute at most process .. When you run the adsbexchange script ... make sure you filled in all fields ... ... if you want to see you own traffic for whatever reason ... we aren't flightaware ... so ...you'll need to ... Feed to a custom port .. https://customglobal4.adsbexchange.com/VirtualRadar/desktop.html# Pick an open xCons-51xxx with no data on it and run the setup and use that port when prompted .... 30005 is default .. If you a just enough competent with linux ... nano adsbexchange-netcat_maint.sh probably in /home/pi/adsb-exchange edit the feed.adsbexchange.com:30005 to your custom port Be aware flightaware has gimped the Pi by overriding the Raspbian source lists ..
Thanks James, but telling me how easy it should be isn't particularly helpful when it actually isn't for my case. Thanks for the htop tip, I didn't know that, but not sure how that addresses the issue. I ran this 3 times, always filled out all the fields. Not interested in a custom port, how is that going to help? The strange thing is, all of the sudden the logs went from showing errors for hours, to this without me changing anything: Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Sun Dec 9 19:27:37 2018 Server says: Dec 9 19:27:37 DSBADSB-1 rc.local[445]: In-development v2 server. Expect odd behaviour. Dec 9 19:27:37 DSBADSB-1 rc.local[445]: The multilateration server source code is available under Dec 9 19:27:37 DSBADSB-1 rc.local[445]: the terms of the Affero GPL (v3 or later). You may obtain Dec 9 19:27:37 DSBADSB-1 rc.local[445]: a copy of this server's source code at the following Dec 9 19:27:37 DSBADSB-1 rc.local[445]: location: <deleted> Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Sun Dec 9 19:27:37 2018 Handshake complete. Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Sun Dec 9 19:27:37 2018 Compression: zlib2 Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Sun Dec 9 19:27:37 2018 UDP transport: disabled Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Sun Dec 9 19:27:37 2018 Split sync: disabled Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Sun Dec 9 19:27:37 2018 Input connected to localhost:30005 Dec 9 19:27:37 DSBADSB-1 rc.local[445]: Sun Dec 9 19:27:37 2018 Input format changed to BEAST, 12MHz clock Dec 9 19:28:03 DSBADSB-1 rc.local[445]: Sun Dec 9 19:28:03 2018 Receiver status: connected Dec 9 19:28:03 DSBADSB-1 rc.local[445]: Sun Dec 9 19:28:03 2018 Server status: ready Dec 9 19:28:03 DSBADSB-1 rc.local[445]: Sun Dec 9 19:28:03 2018 Receiver: 21.4 msg/s received 3.7 msg/s processed (17%) Dec 9 19:28:03 DSBADSB-1 rc.local[445]: Sun Dec 9 19:28:03 2018 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server Dec 9 19:28:03 DSBADSB-1 rc.local[445]: Sun Dec 9 19:28:03 2018 Aircraft: 0 of 65 Mode S, 0 of 70 ADS-B used Dec 9 19:43:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:43:04 2018 Receiver status: connected Dec 9 19:43:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:43:04 2018 Server status: ready Dec 9 19:43:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:43:04 2018 Receiver: 687.8 msg/s received 290.1 msg/s processed (42%) Dec 9 19:43:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:43:04 2018 Server: 0.3 kB/s from server 3.3kB/s TCP to server 0.0kB/s UDP to server Dec 9 19:43:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:43:04 2018 Results: 306.1 positions/minute Dec 9 19:43:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:43:04 2018 Aircraft: 54 of 74 Mode S, 70 of 77 ADS-B used Dec 9 19:58:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:58:04 2018 Receiver status: connected Dec 9 19:58:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:58:04 2018 Server status: ready Dec 9 19:58:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:58:04 2018 Receiver: 715.3 msg/s received 322.2 msg/s processed (45%) Dec 9 19:58:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:58:04 2018 Server: 0.3 kB/s from server 3.8kB/s TCP to server 0.0kB/s UDP to server Dec 9 19:58:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:58:04 2018 Results: 371.3 positions/minute Dec 9 19:58:04 DSBADSB-1 rc.local[445]: Sun Dec 9 19:58:04 2018 Aircraft: 74 of 91 Mode S, 75 of 82 ADS-B used Not sure how it changed itself, but does this mean it's working? I am seeing some of my low-flying planes showing up on your map now, but not always such as planes on the ground, do you not display them?
Just saw you responded while I was writing the last post! (thanks). So, it must be at least kind of working, I do see landing planes now live at IAD, that must be from me. Just not sure why sometimes planes I see on PiAware aren't on your map, do you delete them immediately if messages stop flowing? PiAware has some persistence, maybe that's the difference. I have no idea what "anonymous" means, I just followed your script, and I entered a username DSBADSB1 so I guessed that must associate or create my account for this data. If I need to do something further to see my data and feeder on your site, please explain and perhaps that should be explained in your setup instructions. Thanks!
Pick an open xCons-51xxx with no data on it and run the setup and use that port when prompted .... 30005 is default ..Ok, did this and picked 51515, nothing on there. If you a just enough competent with linux ... nano adsbexchange-netcat_maint.sh probably in /home/pi/adsb-exchange edit the feed.adsbexchange com:30005 to your custom portHaha, I used vi I did this, and rebooted, and it didn't work. I re-ran the setup and did it that way, rebooted, and still no joy. Now it's broken: Be aware flightaware has gimped the Pi by overriding the Raspbian source lists ..Not sure what this means...
FYI, it's really hard to share debug info with you guys, your spam filter forbids log files when I try to paste them as text (says it's either too big or spam), even trying to quote your last message was illegal for me, had to remove it lol.
just realized I didn't show enough of the log, see attached. Also attached are the two scripts as a picture, can't even post that as text!:
Vi ?! You must be one of those people who like punishment and having to memorize 42,000 short cuts and quick keys. use [ CODE ] [ /CODE ] tags if you need to paste paths and 'code' Looks like 51515 is someone from Norway? People step on each other now and then .. I'll PM you a port ... I really need to suppress MLAT client messages. New images will dump all those logs to /dev/null so people stop staring at them for hours worried out what the MLAT server is doing ...
Well .. sort of a long answer ... If you are trying to send data to 51515 then it's not working ... 51515 has some guy from Norway on it. PiAware does it's own thing, the source is closed. Best guess is explained below. FlightAware is a multi-million dollar commercial operation built on selling of feeder data. FA has more feeders - so they will have more MLAT (most likely). FA also consumes the FAA feeds so they are required to block aircraft on the block list - this also means they get data at airport, taxi movement. FlightAware sells your feeder unit data - the FlightAware business model is to get individuals to setup feeders - then they get an aircraft owner to request to be on the block list of either source or industry. They push for industry. Then FlightAware tells the aircraft owners to pay a monthly fee and they will show them a dashboard of their aircraft. The FlightAware business model is based on selling tracking to block list aircraft and other things. FlightAware is not pleased with ADSBx or the ADSBx community of feeders. Why? We don't block aircraft that pay FlightAware to be hidden. We don't block anyone, no matter the offer, the threat, or the amount of bribe. We don't sell dashboards, 'enterprise accounts', or anything of the sort. ADSBx gets the data to those who would otherwise not be able to pay FlightAware, et all hundreds to hundreds of thousands a month for data. We only ask that enthusiast, non-profit, non-commercial research pay for their usage to keep the ADSBx project funded and operational. We're not university funded and operating as a commercial business selling data while disguised as some 'opensource project' like OpenSky with unlimited funding from 'sponsors' paying to be removed from the data. ADSBx data is put to good use by a lot of organizations that would otherwise have not access to live ADS-B data globally, a AWS hosted historical database going back to 2016, etc .... Commercial entities are required to license the ADSBx data. This licensing funds the six figure plus a year it takes to make all of this work. ADSBx has no employees, only volunteers. It would be awesome if Dan and I could get ADSBx to a point where we could work on it full time - but alas that is not currently the case. We both have full time real world responsibilities. As for the data, ADSBx has to get a feeder within line of sight of the airport or an ADS-B tower. Towers are interesting because the 978 dump will decode the puck data and create mode-s messages. We aren't FlightAware, ADSBx doesn't have automatic association of accounts or tracking of individual feeders. Outside of the custom port, we collect no data on the feeder. I PM'd you an open port to send data to. Edit the adsbexchange-netcat_maint.sh script .. Change 51515 to that port I PM'd you ... Reboot the Pi .. everything should then work ..
Thank you James for the intro to your world. I assumed you guys were a larger operation, very cool that you have put this together in your spare time. Well, hopefully I'll be up and running and feeding you soon. I made the change, but very little is flying right now. The log shows starting without error, but then nothing so far: CODE Dec 10 01:51:46 DSBADSB-1 systemd[1]: Starting /etc/rc.local Compatibility... Dec 10 01:51:46 DSBADSB-1 systemd[1]: Started /etc/rc.local Compatibility. Dec 10 01:52:16 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:16 2018 mlat-client 0.2.6 starting up Dec 10 01:52:16 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:16 2018 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Dec 10 01:52:17 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:17 2018 Beast-format results connection with ::1:30104: connection established Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:22 2018 Server says: Dec 10 01:52:22 DSBADSB-1 rc.local[465]: In-development v2 server. Expect odd behaviour. Dec 10 01:52:22 DSBADSB-1 rc.local[465]: The multilateration server source code is available under Dec 10 01:52:22 DSBADSB-1 rc.local[465]: the terms of the Affero GPL (v3 or later). You may obtain Dec 10 01:52:22 DSBADSB-1 rc.local[465]: a copy of this server's source code at the following Dec 10 01:52:22 DSBADSB-1 rc.local[465]: location: https://github.com/mutability/mlat-server Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:22 2018 Handshake complete. Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:22 2018 Compression: zlib2 Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:22 2018 UDP transport: disabled Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:22 2018 Split sync: disabled Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:22 2018 Input connected to localhost:30005 Dec 10 01:52:22 DSBADSB-1 rc.local[465]: Mon Dec 10 01:52:22 2018 Input format changed to BEAST, 12MHz clock /CODE I still have no idea how to view my feeder info, I can follow your couple of links (why isn't it just one link?) to various custom map viewers, and pull up lists of receivers, but I can find neither the port or user name that you set me up as. I will take a look in the morning again when planes are flying. Thanks! --Scott
Sigh. We don't have feeder info, we are not FlightAware, we don't have dashboards, leader boards, and competitions to see who has the longest dongle. It's really not in the budget, ADSBx could use someone who is Golang programmer to finish coding some stuff that would let us do things like that, seeing as it's pro-bono and fairly complex - not exactly a line out the door of volunteers. If you send BEAST/AVR to feed.adsbexchange.com 30005, it gets integrated into the Global UI with everyone's traffic. If you send to a custom port then it gets sent to custom feed port first, so you care stare it at your ADS-B data, then that data gets sent to the Global UI and merged with all the other traffic. Looks like it's working .. Thanks for the feed! You are also getting really good MLAT from the other feeds around you! https://customglobal4.adsbexchange.com/VirtualRadar/desktop.html# Menu -> Reciever -> DSBADSB1
Now that you have this working. Are you brave enough to use another SDR, the FA orange one or the RTL-SDR to decode 978?
Excellent, it is working! James...I didn't mean to frustrate you as well, and no contest between ADSBx and FA was implied or intended. But please realize this doesn't always just work (I'm quite technically competent, not a newbie), and when it doesn't there isn't much help on here so it's the wild west. So we put in a bunch of effort in order to help ADSBx by feeding you, I think you underestimate our basic need to get confirmation and a bit of gratification that it's working, and it isn't obvious how to tell. I could not find DSBADSB1 in any of the lists last night, not sure why. Anyway, I now see it's working and am thrilled. My motivations for feeding ADSBx are twofold: 1) improve your coverage near my house so that Airnoise works better here!; 2) I have my FA map running on my desk all day because the IAD planes launch right over my house and it's interesting to know who they are, but I quite often have planes fly over that are restricted, or don't even show up on FA at all. I hope to see who they are, but I need your map to do that! I am still curious why the ADSBx map doesn't show everything I should be feeding. Please see attached for the two maps at about the same moment, ADSBx only shows 4 planes while FA has many more on the ground too, are you just not showing those? I'm curious, in the log what does 361.6 msg/s processed (50%) mean? How can you tell that MLAT is working and that I have good peers, I don't see that? OK...please elaborate on "another SDR, the FA orange one or the RTL-SDR to decode 978". I have not played at all with 978. I guess I would need another SDR, I'm not sure if the ones with a 1080 pre-amp will work at 978, obviously a different BPF and probably a 978 tuned antenna would be needed. I actually have extra dongles lying around, but what are you offering or recommending for the antenna/filter/amp? I currently have the FA Pro Stick Plus and their big 1080 antenna, but I don't think that will work at 978. I'm curious what information this additional feed will tell us?
Oh very cool. You're working with Chris?! http://www.adsbexchange.com/coverage-2/ The coverage map will give you the general area and altitude of MLAT you are participating in as a heat map. The difference is because FA uses the FAA SWIM and ADSI - therefor other sites are required by LoA to block aircraft that request it. But that also means FA will show planes taxiing, etc .... due getting data from the government sources. ADSBx is independent - so we do not block or respond to block lists, but that also hurts reception - though the trade off is acceptable so ADSBx can track all kinds of very cool things. The custom feed port only shows the ADS-B traffic. We can't show the MLAT on the custom feed because FA has money to pay lawyers and claims copyright over MLAT data on PiAware. ADSBx MLAT is only shown aggregated on the Global Map. This is how it must be done - there is no alternative. re: 978 The ones with 1090 filter will not work. Orange FA one (pre-amp only?) or the RTL-SDR .. something without 1090 filter. We have a combo antenna that should do both 1090 and 978 ... the FA one doesn't do 978 .. http://towers.stratux.me/ If you can get line of sight to one of these towers in the area ... that would improve mode-c / mode-s non ads-b aircraft reception and even some ads-b. Also in the US, a lot of small part 91 general aviation is going 978 ... anything that fly's below 18,000 ... so I think we are going to have to further develop 978 towers.
Hey James. Well I'm just an Airnoise subscriber and button-owner , but I've discussed with Chris why I get results like the attached 5 most recent complaints today, empty reports--I can see the plane (and of course hear it!) on FA but it doesn't show up in the report. Chris said he used ADSBx and it wasn't picking these flights up until well past my house (higher), pointed me to ADSBx and said hey, if you feed them, it will help everybody and you will get what you want too. Unfortunately, as the attached shows, it's not helping completely, I think these missing flights were FA MLAT. So, I think I'm hearing that you are running your own MLAT network and computation and you can put that on the public map, but perhaps don't have the same MLAT coverage (more than me) to get these planes I'm missing? Ok, I'll take a look at those links. Sure, I'm up for learning anything new and playing with this, but I'm really busy. Chris made this suggestion months ago, I finally got time this weekend to run the "simple" script setup Consumed most of my yesterday, but I'm glad it's up now. As to 978, are we listening to just the tower or the aircraft too? I don't know where the tower is, but of course a directional antenna could work much better if that's all we want.
Well .. those might be Mode-c .. maybe ... we can only track Mode-S .. Mode-C aircraft are altitude only .. no hex code -- so you can't tell who or what they are .. that will change coming into 2020 as they are all required to upgrade to ADS-B mode-s
Ahh, ok. By the way, I forgot to mention on the ground aircraft, I thought my FA Skyview map was only my own reception, and I see all the planes on the ground, it says I'm receiving many ADSB messages.
Well, all the planes on the ground say "ADS-B". When it's MLAT it says that instead. And these are mostly green, which is supposed to be ADSB, MLAT is yellow.
