It's been about a month now since I've put the Linux Eee-pc and the V3 rtl-sdr to work feeding adsbx. For the most part, things are good with this setup. Here's an observation/question: It seems that the vast majority use the PI to decode/feed for ads-b, and are not doing what I'm doing (no worries there). Here's the point: After doing some research, It seems that I'm unable to use the latest or "best" code because Dump1090 is no longer updated/forked for any other system than the PI. I'm using the Malcolm Robb fork because it seems to be the latest fork that can be used by a non-PI system. I tried to install a mutability fork and couldn't because the "architecture" is wrong. I'm getting the idea that the Dump version I'm using will be obsoleted, and that it will fall behind in the ability to decode efficiently and properly, as compared to the newer forks that presumably are continually updated. Yes, I know that I could just simply buy a PI and join the majority, but I've put to use an unused pc and made it work for ads-b, without an additional expenditure. Am I seeing this situation correctly... concerning the software Dump1090?
Hmm. My PC is 32-bit Intel running Lubuntu, not sure if that has anything to do with it. Perhaps I can try again. Thought sure it stopped me last time because of the aforementioned architecture difference.
Try as described here: https://forum.flightradar24.com/threads/10232-How-to-Install-dump1090-mutability_1-15-dev-on-RPi or use automated install from adsb-receiver: https://github.com/jprochazka/adsb-receiver (select what you want to install).
Took you're advice on the automated install... it works... now running mutability instead of Malcolm Robb fork. I had parameters set with the old fork, but this one is "automatic"... just have to run ./dump1090 with no parameters to start the program. I need to see what it's parameters are, so have to look for the particular file it's using to start dump1090 and then possibly edit the start-up parameters to my liking.
