Due to the coarser -e setting the CPU targeting is less accurate to avoid flapping around.
+/- 5% of the target value is expected.
1 Like
I read some comments about the MLAT problem. Does this now require you to do an update / restart via your settings or was it an internal fix??
It was never about airspy_adsb.
Just like the discussion of adaptive gain, off topic.
More bit dancing in a few.
1 Like
Running 2.2-RC2 for 45 min now, and must say only a few GND planes (2/260) and still no aircraft with an emergency !
Rpi4 OPTIONS= -v -t 60 -f 1 -w 5 -e 4 -E 15 -b, Gain 19, sample rate 24 (frame rate/sec 1880)
(Numbers are from wiedehopf script) cpu 51%
BTW no problems with mlat and a sample rate of 24…
1 Like
Can you help me with understanding ? Sample rate 12 / 20 /24 ? I run my R2 at 12. Cant seam to get stable MLAT at 24… Maybe need to go much lower with -e
It had nothing to do with Airspy or whatever it was a problem on FA side which is fixed meanwhile
Tried two different settings for a while, finally with pretty similar results. Looks like the tolerance on my site is pretty high
└─4494 /usr/local/bin/airspy_adsb -v -t 60 -f 1 -w 5 -e 30 -E 30 -C 80 -l 47787:beast -c localhost:30004:beast -g 19 -m 1
Sep 04 15:10:21 Raspy airspy_adsb[4494]: /!\ Lost 131072 samples /!\
Sep 04 15:10:21 Raspy airspy_adsb[4494]: /!\ Lost 131072 samples /!\
Sep 04 15:10:21 Raspy airspy_adsb[4494]: Dropped samples, adjusting preamble filter: 29 -> 28
Sep 04 15:10:25 Raspy airspy_adsb[4494]: CPU 99.6 %, target 80.0 %, adjusting preamble filter: 28 -> 27
Sep 04 15:10:35 Raspy airspy_adsb[4494]: CPU 97.0 %, target 80.0 %, adjusting preamble filter: 27 -> 26
Sep 04 15:10:44 Raspy airspy_adsb[4494]: CPU 95.4 %, target 80.0 %, adjusting preamble filter: 26 -> 25
Sep 04 15:10:54 Raspy airspy_adsb[4494]: CPU 94.3 %, target 80.0 %, adjusting preamble filter: 25 -> 23
Sep 04 15:11:04 Raspy airspy_adsb[4494]: CPU 89.5 %, target 80.0 %, adjusting preamble filter: 23 -> 22
Sep 04 15:11:14 Raspy airspy_adsb[4494]: CPU 86.5 %, target 80.0 %, adjusting preamble filter: 22 -> 21
Sep 04 15:12:24 Raspy airspy_adsb[4494]: CPU 85.1 %, target 80.0 %, adjusting preamble filter: 21 -> 20
└─5466 /usr/local/bin/airspy_adsb -v -t 60 -f 1 -w 5 -e 10 -E 30 -C 90 -l 47787:beast -c localhost:30004:beast -g 19 -m 1
Sep 04 15:13:37 Raspy airspy_adsb[5466]: Listening for beast clients on port 47787
Sep 04 15:13:37 Raspy airspy_adsb[5466]: Acquired Airspy device with serial B06C68DC371B9AA3
Sep 04 15:13:37 Raspy airspy_adsb[5466]: Decoding started at 12 MSPS
Sep 04 15:13:38 Raspy airspy_adsb[5466]: Push client connected to localhost:30004 (beast)
Sep 04 15:13:47 Raspy airspy_adsb[5466]: CPU 48.5 %, target 90.0 %, adjusting preamble filter: 10 -> 14
Sep 04 15:13:57 Raspy airspy_adsb[5466]: CPU 64.7 %, target 90.0 %, adjusting preamble filter: 14 -> 17
Sep 04 15:14:07 Raspy airspy_adsb[5466]: CPU 73.0 %, target 90.0 %, adjusting preamble filter: 17 -> 19
Sep 04 15:14:17 Raspy airspy_adsb[5466]: CPU 80.0 %, target 90.0 %, adjusting preamble filter: 19 -> 20
Sep 04 15:14:27 Raspy airspy_adsb[5466]: CPU 83.5 %, target 90.0 %, adjusting preamble filter: 20 -> 21
Sep 04 15:14:37 Raspy airspy_adsb[5466]: CPU 85.0 %, target 90.0 %, adjusting preamble filter: 21 -> 22
which settings are “better” (if any)?
It’s the same settings except the CPU target …
The starting value is irrelevant.
1 Like
In the first case, the initial setting for e is 30. So, it’s pretty normal you got lost samples at start.
Better starting with a low number for e, if using -C, so the system increases e, instead of having to go down.
EDIT : a little too late 
I must have been absent the day the DF was first discussed in this thread. Can someone please give me a quick primer on DF and how it’s used to determine the airspy_adsb settings? Thanks.
That should tell you all you need to know… 
You’re looking for the Helper scripts for recording samples / testing settings section.
1 Like
It’s really a minor difference in 99% of cases.
1 Like
Thanks. I’ll check it out.
So I a trying to capture samples with an AirSpy Mini. I have used sampling rates of both 12 and 20 (I normally run at 20) and the sample capture is aborting with a “caught signal 15”.
sudo /usr/local/share/airspy-conf/airspy_record_sample.sh 12 17 500
What do I need to try to get the sample capture to run without an error? TIA.
I have names of people spending countless hours just to get 2 more decoded messages per hour. On good days. Well, at least I know one 
two
( post must be at least 20 characters)
2 Likes
you might wanna seek help then, same goes for @LFSD , I’m worried that you guys might get withdrawl issues when this project is done and a stable release is there.
Another reason not to get into the Airspy’s 
I’m looking forward to that day 
You should not be so harsh on Foxhunter, he was just commenting on that great new product that Flightaware have released that could make all this tweaking irrelevant in the long run and seems to be about ADS-B Flight Tracking, well within the topic.