I have a 3B+ running dump978-fa only successfully. My only known problem is not seeing a location marker and distance rings in Skyview. How do I resolve this?
Thank you.
@ca249
This is the solution:
1 Like
Good now, thank you.
How do I get 1090 back running after I switched to 978 only?
I had run the âsudo piaware-config receiver-type noneâ
âsudo systemctl restart piawareâ
So I tried âsudo piaware-config receiver-type sdrâ
âsudo systemctl restart piawareâ
It seems to exit after startingâŚ
sudo systemctl restart piaware
pi@piaware:~$ sudo journalctl -eu dump1090-fa
~~~~~~-- Logs begin at Thu 2016-11-03 17:16:42 UTC, end at Tue 2019-04-23 20:32:27 UTC.
--Apr 23 20:13:11 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 23 20:13:11 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=64/n/a
Apr 23 20:13:11 piaware systemd[1]: dump1090-fa.service: Unit entered failed state.
Apr 23 20:13:11 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Apr 23 20:19:17 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 23 20:19:17 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=64/n/a
Apr 23 20:19:17 piaware systemd[1]: dump1090-fa.service: Unit entered failed state.Apr 23 20:19:17 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Apr 23 20:21:15 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 23 20:21:15 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=64/n/a
Apr 23 20:21:15 piaware systemd[1]: dump1090-fa.service: Unit entered failed state.
Apr 23 20:21:15 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Apr 23 20:25:27 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 23 20:25:27 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=64/n/a
Apr 23 20:25:27 piaware systemd[1]: dump1090-fa.service: Unit entered failed state.
Apr 23 20:25:27 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
978 seems to still be running, and I did check the serials of the sdrs and also restarted etcâŚ
My config is:
pi@piaware:~$ sudo piaware-config -show
allow-auto-updates yes # value set at /boot/piaware-config.txt:67
allow-manual-updates yes # value set at /boot/piaware-config.txt:71
allow-mlat yes # value set at /boot/piaware-config.txt:75
allow-modeac yes # value set at /boot/piaware-config.txt:79
image-type piaware # value set at /usr/share/piaware-support/piaware-image-config.txt:5
manage-config yes # value set at /usr/share/piaware-support/piaware-image-config.txt:4
receiver-type sdr # value set at /boot/piaware-config.txt:84
rtlsdr-device-index 00001090 # value set at /boot/piaware-config.txt:87
rtlsdr-gain max # value set at /boot/piaware-config.txt:60
uat-receiver-type sdr # value set at /boot/piaware-config.txt:85
uat-sdr-device driver=rtlsdr,serial=00000978 # value set at /boot/piaware-config.txt:86
wired-network no # value set at /boot/piaware-config.txt:27
wireless-network yes # value set at /boot/piaware-config.txt:33
wireless-password <hidden> # value set at /boot/piaware-config.txt:49
wireless-ssid GCHanger1 # value set at /boot/piaware-config.txt:48
Thanks, sorry if I missed this somewhere aboveâŚ
#receiver-type rtlsdr # using default value
use rtlsdr instead of rtl
Thank you. That worked, but it needed a Pi reboot - restarting piaware wasnât enoughâŚ?
1 Like
restarting piaware and dump1090-fa should have sufficed.
@abcd567 I take it in time there will be an automated upgrade path from 3.6.3 ?
Ok, thanks for the info. Wasnât sure who would have known that or not. Just guessed you many know.
Yes, there will be the usual upgrade path.
1 Like
Just added the graphs. Will have to wait a while for UAT activity, none on the map currently. Well done and Thank you!
2 Likes
The graphs are by @wiedehopf, and not by me. I only posted the bash command to install it. Wiedehopf actually deserves your appreciation & thanks.
Yes I meant @wiedehopf too!
No UAT activity here yet will ahve to waitâŚ
I have installed graphs 5 days ago, and graphs show that in 5 days I got only three planes. 
Well I have had one whole plane but only half a message in two days. Think the other half of the message had the location data, nothing in the range chart. Suppose thatâs something! 
1 Like
5 Likes
I have 3.7.0.1 running 978 and 1090 and dump1090-fa is showing a lot fewer aircraft than the 3.6.3 receivers dump1090-fa. Both receivers are using the same antenna through a splitter with identical cables from the splitter to the receivers. I swapped cables and the issue remained on the 3.7.0.1 receiver. Here are the gain settings:
On 3.6.3:
rtlsdr-gain -10 # value set at /boot/piaware-config.txt:73
On 3.7.0.1:
rtlsdr-gain max # value set at /boot/piaware-config.txt:60
On 3.7.0.1 I tried manually setting the rtlsdr-gain in /boot/piaware-config.txt to -10 and it still dispaly as max.
I compared the RSSI on aircraft that appeaered on both on the 3.6.3 and 3.7.0.1 receivers and the readings were nearly identical, with a couple of tenths of a dB so it doesnât appear to be an RF issue.
Neither RPI is showing excessive CPU or memory usage in htop.
On 3.6.3 the rtlsdr-gain setting of -10 indicated AGC. Does max on 3.7.0.1 indicate it is using the AGC? If not, is there a setting for AGC on 3.7.0.1?
Has anybody else seen this?
3.7.0.1
The "rtlsdr-gain max" of piaware-config is translated to "--gain -10" when passed to dump1090-fa, which is again translated by dump1090-fa to "AGC", which actually sets the gain around 55 dB, which is maximum achievable in a RTL dongle. Hence setting âmaxâ sets dongle to maximum achievable gain.
pi@piaware:~ $ sudo piaware-config rtlsdr-gain max
Set rtlsdr-gain to max in /boot/piaware-config.txt:60
pi@piaware:~ $ grep rtlsdr-gain /boot/piaware-config.txt
rtlsdr-gain max # updated by fa_piaware_config
pi@piaware:~ $ sudo systemctl restart piaware
pi@piaware:~ $ sudo systemctl restart dump1090-fa
pi@piaware:~ $ sudo systemctl status dump1090-fa
â dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-04-26 01:13:21 EDT; 2min 52s ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 10750 (dump1090-fa)
CGroup: /system.slice/dump1090-fa.service
ââ10750 /usr/bin/dump1090-fa --net-bo-port 30005 --fix --device-index 00001090 --gain -10 --ppm 0 --max-range 360 --net --net-hea
Apr 26 01:13:21 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 26 01:13:21 piaware dump1090-fa[10750]: Fri Apr 26 01:13:21 2019 EDT dump1090-fa 3.7.0.1 starting up.
Apr 26 01:13:21 piaware dump1090-fa[10750]: rtlsdr: using device #1: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00001090)
Apr 26 01:13:21 piaware dump1090-fa[10750]: Found Rafael Micro R820T tuner
Apr 26 01:13:22 piaware dump1090-fa[10750]: rtlsdr: enabling tuner AGC
1 Like
Do you mean showing on the map or in the FA stats?
The prerelease piaware has a bug reducing FA stats because sometimes the feeder drops out and restarts only after an hour has passed.
Iâm not aware of any functional changes for dump1090-fa that would change anything. (on the local map)
1 Like