I was attempting to see which decoder combo worked best with my indoor pi setup and got rough results with Readsb and Piaware; which I can attribute to my cheap antennae and being in an big apartment. I enjoy the tar1090 interface of readsb for readability but I think I got better decoding results with the dump1090-fa. My gain was set to 43.9/auto and ppm to 0, but i would get like ~2.7 for signal and noise reception and nearly a 0 message reception although sometimes it would be around ~70. Has anyone ever compiled their own decoder-interface combo and what are some things i could set differently with my Flightaware Pro Stick Plus to fix that bad reception manually. This is a scatter brained post but I wanted to layout what info i could gather and what my objectives are in one swoop.
Your site hasn’t had enough up-time to establish a base performance level, so trying to optimise the decoding will be impossible (you won’t know if it’s better or worse).
School me, do I just leave it running for a while and then i can get the “history” tally underneath the messages in the skyaware/tar1090 gui? Also, I had a couple instances where I managed to get a couple planes and some helicopters in realtime when I ran a readsb setup. I havent had the same luck with the piaware 3 setup though.
If you are making gross changes, then running a station for a week (/month) will give you something to compare, but if you are making subtle changes, you really need two stations side by side - one as the control and one to play with.
You make them as identical as possible, run for long enough to prove similar performance and then start your tests (on one station only).
That way, you can compare the behaviour over the last 5min and not wait a week to see trends.
What antenna are you using and where/how do you have it situated? That can make a big difference; especially indoors.
I am using a basic indoor double coil antennae and have it positioned on my window facing desktop. I was able to resolve my tracking issues and was going to go back live after the July update so I can set it up on a Pi with Trixie. The thing that fixed my issues with my Flightaware Pro Stick Plus seems to be installing the Linux drivers from here (https://www.rtl-sdr.com/V4/).
Something very odd there - the V4 uses a different front-end chip, so needs drivers incompatible with the chip used in the ProSticks.
Edit: It’s been a while since I looked at anything to with the V4 - the drivers are now backward compatible, so yeah - that should work.
@geckoVN :
Yes, you are right.
@LeelaNotNibbler :
For ProStick and other DVB-T based dongles, driver packages are:
sudo apt install librtlsdr-dev
sudo apt install libusb-1.0-0-dev
## may be also:
sudo apt install libsoapysdr-dev
Full list of Build tools, Build Dependencies, and Run-time Dependencies:
Build-Tools
sudo apt install -y \
git \
build-essential \
devscripts
Build & Run-time Dependencies:
sudo apt install -y \
debhelper \
librtlsdr-dev \
libbladerf-dev \
libhackrf-dev \
liblimesuite-dev \
libusb-1.0-0-dev \
pkg-config \
libncurses5-dev \
libsoapysdr-dev \
adduser \
lighttpd
I wonder what has caused the increase in messaging then? I have done installs of the Piaware auto build and Readsb auto build; in this most recent test (that’s working the best thus far) its an auto Readsb compilation, but I added the first couple packages: librtlsdr-dev, libusb-1.0-0-dev. I’m planning to attempt again with a Piaware feed on Trixie and add the tcl-tls package that i noticed in your other post. 
Packages to be installed before building piaware package from source-code on Trixie:
Build Tools
sudo apt install -y \
git \
build-essential \
devscripts
Depencies:
sudo apt install -y \
debhelper \
autoconf \
python3-dev \
python3-pyasyncore \
python3-venv \
python3-setuptools \
python3-filelock \
python3-wheel \
python3-build \
python3-pip \
libz-dev \
openssl \
libboost-program-options-dev \
libboost-regex-dev \
libboost-filesystem-dev \
libboost-system-dev \
patchelf \
net-tools \
iproute2 \
tcl8.6-dev \
tclx8.4 \
tcl8.6 \
tcllib \
itcl3 \
tcl-tls \
rsyslog