Sudo sh -c "sed -i 's/DEVICE=\".*\"/DEVICE=\"\"/' /etc/default/dump1090-mutability"ĮDIT: So far as CPU use, airspy_adsb takes the grunt of the load and dump1090 will only eat up maybe 2-3% on it’s own, so don’t need to look at it like you are adding a huge load on top of whatever you regularly see when dump1090 is chomping through the raw input. To change back to “normal” use with an rtl device, I simply run the following: Sudo airspy_adsb -c localhost:30104:beast -d 2 -p -n -w 4 -g 18 -f 0 &įor whatever it’s worth anyhow. Sudo /etc/init.d/dump1090-mutability force-reload Sudo tar xzf airspy_adsb-linux-arm.tgz & sudo rm $_ I have taken a slightly different approach (mutability) - for FA use as jonhawkes2030 instructed above: Prog: Youssef, if you read this, is airspy_adsb set by default to use are optimum values for sample rate / decimation on 1090 mhz? Or should I really try and “tweak” things.Īgain, thanks to everyone who has posted so much useful information. I see there is an option in airspy_adsb to use decimation, but thus far any decimation value seems to decrease the amount of data that i get on 1090 from the Airspy. I’m vary familiar with using the Airspy for VHF/UHF digital decoding, and when used for that the Airspy beats anything I’ve ever used hands down, especially when one runs 10 msps with a decimation of 64. I might get a filter / amp combo to put up at the antenna in the attic, although I’m not sure I really need the filter. I’ve only been running the Airspy for a day, and it seems to be on par with my NESDR dongle. Jon: I’ve seen you specifically suggest that the Airspy is “deaf” on 1090 and needs an amp. Tells the Airspy to listen on TCP 30005 (net-bo-port # beast output port) for anything that wants to connect and obtain BEAST-formatted data from it, such as PlanePlotter and VRS running on a separate machine. My dump1090-fa is listening on port 30104 for BEAST-formatted input, which includes (a) the data from my Airspy and (b) the data from fa-mlat-client. Tell’s the Airspy to connect to port 30104 (net-bi-port # beast input port) of dump1090-fa. My commandline is a little different, and I’ll post it just so others who might have questions about MLAT, etc. I had tried Airspy before, but really hadn’t understood what the -w option was even though I did test -w 2. The key was to run 4 workers and split the CPU usage up among four cores so that a single core doesn’t get maxed out by Airspy + dump1090-fa + fa-mlat-client. So far I’m running my Airspy with success.
Airspy planeplotter update#
Please provide feedback and I will update this post. There are many ways to do it but here is my attempt.
0 kommentar(er)
