it’s not getting better, this is the view for the last eight hours:
Had the same issue here (see previous reply). This happens with some setups.
Mine is orange FA stick, blue FA filter (2019) and FA antenna, no LNA etc.
AFAIK this does not occur on AirSpy based setup.
Run the next 8 hours without the --fix, but with --no-fix (Disable error correction using CRC) instead and see what it does for you.
Thanks,
just seen the switch in my dump1090 config file. This might be the case why it changed.
As long as my other values are not impacted negative, i am fine with it.
This has been definitively increased:
checked the difference in dump1090 config, these are different to my previous one.
–net-ro-size 1300
–net-ro-interval 0.2
the previous values were 1000 and 1.0
Can somebody explain what these values are and what they are impacting?
Read the help or the source code.
In short they don’t affect you.
I’ve read the help. There it’s explained but did not tell what impact it has on a change 
But i am good with your reply
Oh, right, this is a package install? I fixed some inconsistencies in the default options for package installs to match what the sdcard install would generate (notably, --fix as noted by @hbokh); you probably picked up that change. It’s normal to see an increased rate of single-track aircraft with --fix, dump1090 will be filtering those out. Up to you whether you want to retain that change or not.
Thanks for explanation. I am good with it right now as the other values are ok.
If you have enough CPU work for multiple cores then they’ll get used. It’s not useful to use multiple cores just for the sake of “sharing load”; swapping processes between cores is relatively expensive and it makes more sense to just keep the extras idle so they can stay in a low power state. Anyway, this is not something that the piaware sdcard does anything special about; if you can make standard Raspbian do whatever it is you want to do, the same should work on the piaware sdcard image.
1 Like
so to go from 3.7.2 SD card image to 3.8.0 simply do the “upgrade and restart piaware” on the “configure” page? also, since i’m using airspy mini i need to reinstall wiedehopf’s script? sorry for the question but all of the Buster references are a bit confusing…by the way, i’m still using RPI3B+
All three of the Pis I’m responsible for have been built from bare Stretch or Buster Lite images and for each one today, I’ve gone through
sudo apt-get update
sudo apt-get dist-upgrade
And now all three are running 3.8.0
Previously, one was on 3.7.2 and I think the other two were on 3.7.1
thanks keithma…the upgrade to 3.8.0 worked great
I have upgraded yesterday to 3.8.0. It’s this normal?
A little bit further above i raised the same question and received an answer 
Check here:
Thank you. Everthing else seems as usual…
It is normal behavior due to the newly added --fix in the default config at /etc/default/dump1090-fa.
See dump1090/dump1090-fa.default at master · flightaware/dump1090 · GitHub
If you don’t want it, simply remove it as an option. It will hardly affect your reception.
Also check the gain: it might have been (re)set to -10!
@obj did you mean to overwrite the configuration file with the new defaults?
I’m curious why the debian package is doing that.
It will update the configuration file without prompting if the existing configuration file exactly matches the configuration file provided by the existing installed version of the package, i.e. if the user has made no changes. Otherwise, it will prompt and ask what to do. This is the normal Debian packaging behaviour and the packaging isn’t doing anything special beyond marking /etc/defaults/dump1090-fa as a conffile; dpkg does the rest.
For upgrades triggered via piaware, the upgrade is set up to always respond “no, keep the existing config file” if there are modifications.
So the TL;DR is that the defaults only get changed if the user didn’t touch the old defaults (or if they explicitly say to use the new version)
1 Like
All three of mine asked about replacing and in each instance, I told it to keep the existing file.
Ah that makes sense, should actually have thought of that