Version 3.7.0 of dump1090-fa & Piaware

SoNic67 · April 5, 2019, 10:23pm

ssh.txt didn’t work for me

abcd567 · April 5, 2019, 10:24pm

Valid file names for enabling SSH:

ssh
ssh.txt
SSH
SSH.txt

wiedehopf · April 5, 2019, 10:26pm

Maybe the file extension was hidden by windows?
That would make the actual filename ssh.txt.txt

(Or the other options were introduced somehwere along the way)

SoNic67 · April 5, 2019, 10:28pm

That’s one of the first things that I un-hide on Windows. So annoying.
But this was a year ago when I imaged last my SD card, so things might have changed.

abcd567 · April 5, 2019, 10:30pm

This has happened with me once when “show extension for known file type” was unchecked in “folder options”. Since then I started using extensionless version i.e. ssh or SSH, just in case.

LitterBug · April 6, 2019, 1:03am

This is why I dumped *indows and only use *nix
Cheers!
LB

abcd567 · April 7, 2019, 11:57pm

Piaware 3.7.0 + dump1090-fa 3.7.0 on OrangePi PC / Armbian 5.75 (Stretch)

pi@orangepipc:~/piaware_builder$ sudo cat /var/log/piaware.log

Apr  7 23:34:16 localhost piaware[6641]: creating pidfile /run/piaware/piaware.pid
Apr  7 23:34:16 localhost piaware[6641]: ****************************************************
Apr  7 23:34:16 localhost piaware[6641]: piaware version 3.7.0 is running, process ID 6641
Apr  7 23:34:16 localhost piaware[6641]: your system info is: Linux orangepipc 4.19.20-sunxi #5.75 SMP Sat Feb 9 19:0
rmv7l GNU/Linux
Apr  7 23:34:18 localhost piaware[6641]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Apr  7 23:34:18 localhost piaware[6641]: Connection with adept server at piaware.flightaware.com/1200 established
Apr  7 23:34:18 localhost piaware[6641]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Apr  7 23:34:18 localhost piaware[6641]: FlightAware server certificate validated
Apr  7 23:34:18 localhost piaware[6641]: encrypted session established with FlightAware
Apr  7 23:34:19 localhost piaware[6641]: adept reported location: 43.5xxxx, -79.6xxxx, xxxft AMSL
Apr  7 23:34:19 localhost piaware[6641]: Receiver location changed, restarting dump1090 and skyview978
Apr  7 23:34:19 localhost piaware[6641]: attempting to restart dump1090..
Apr  7 23:34:19 localhost piaware[6641]: attempting to restart dump1090-fa using 'systemctl --no-block try-restart du
ce < /dev/null'...
Apr  7 23:34:19 localhost piaware[6641]: dump1090 restart appears to have been successful
Apr  7 23:34:19 localhost piaware[6641]: attempting to restart skyview978..
Apr  7 23:34:19 localhost piaware[6641]: attempting to restart skyview978 using 'systemctl --no-block try-restart sky
 < /dev/null'...
Apr  7 23:34:19 localhost piaware[6641]: skyview978 restart appears to have been successful
Apr  7 23:34:19 localhost piaware[6641]: logged in to FlightAware as user abcd567
Apr  7 23:34:19 localhost piaware[6641]: my feeder ID is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Apr  7 23:34:19 localhost piaware[6641]: site statistics URL: https://flightaware.com/adsb/stats/user/abcd567#stats-6396
Apr  7 23:34:19 localhost piaware[6641]: multilateration data requested

Apr  7 23:34:19 localhost piaware[6641]: error handling message 'clock\t1554680059\ttype\tmlat_enable\tudp_transport\
54 1154629014' from server: can't read "::adsbLocalPort": no such variable, disconnecting and reconnecting..
Apr  7 23:34:19 localhost piaware[6641]: traceback: can't read "::adsbLocalPort": no such variable
Apr  7 23:34:19 localhost piaware[6641]:     while executing
Apr  7 23:34:19 localhost piaware[6641]: "is_local_receiver $::adsbLocalPort"
Apr  7 23:34:19 localhost piaware[6641]:     (procedure "start_mlat_client" line 15)
Apr  7 23:34:19 localhost piaware[6641]:     invoked from within
Apr  7 23:34:19 localhost piaware[6641]: "start_mlat_client"
Apr  7 23:34:19 localhost piaware[6641]:     (procedure "enable_mlat" line 16)
Apr  7 23:34:19 localhost piaware[6641]:     invoked from within
Apr  7 23:34:19 localhost piaware[6641]: "enable_mlat $row(udp_transport)"
Apr  7 23:34:19 localhost piaware[6641]:     ("mlat_enable" arm line 3)
Apr  7 23:34:19 localhost piaware[6641]:     invoked from within
Apr  7 23:34:19 localhost piaware[6641]: "switch -exact $row(type) {
Apr  7 23:34:19 localhost piaware[6641]: #011#011"mlat_enable" {
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011if {[info exists row(udp_transport)]} {
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011#011enable_mlat $row(udp_transport)
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011} else {
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011#011enable_mla..."
Apr  7 23:34:19 localhost piaware[6641]:     (procedure "::forward_to_mlat_client" line 5)
Apr  7 23:34:19 localhost piaware[6641]:     invoked from within
Apr  7 23:34:19 localhost piaware[6641]: "{*}$mlatCommand row"
Apr  7 23:34:19 localhost piaware[6641]:     ("mlat_*" arm line 3)
Apr  7 23:34:19 localhost piaware[6641]:     invoked from within
Apr  7 23:34:19 localhost piaware[6641]: "switch -glob $row(type) {
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011"login_response" {
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011#011handle_login_response_message row
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011}
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011"notice" {
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011#011handle_notice_message row
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011}
Apr  7 23:34:19 localhost piaware[6641]: #011#011#011"aliv..."
Apr  7 23:34:19 localhost piaware[6641]:     (object "::adept" method "::fa_adept::AdeptClient::handle_response" body
Apr  7 23:34:19 localhost piaware[6641]:     invoked from within
Apr  7 23:34:19 localhost piaware[6641]: "handle_response response"
Apr  7 23:34:19 localhost piaware[6641]: multilateration data no longer required, disabling mlat client

Apr  7 23:34:19 localhost piaware[6641]: reconnecting in 71 seconds...
Apr  7 23:34:19 localhost piaware[6641]: no ADS-B data program seen listening on port 30005 for 3 seconds, next check
Apr  7 23:34:19 localhost piaware[6641]: UAT support disabled by local configuration setting: uat-receiver-type
Apr  7 23:34:51 localhost piaware[6641]: 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
Apr  7 23:35:19 localhost piaware[6641]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Apr  7 23:35:19 localhost piaware[6641]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localho
t 30005 --stdout --lat 43.5xx --lon -79.6xx
Apr  7 23:35:19 localhost piaware[6641]: Started faup1090 (pid 6715) to connect to dump1090-fa
Apr  7 23:35:20 localhost piaware[6641]: piaware received a message from dump1090-fa!
Apr  7 23:35:30 localhost piaware[6641]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Apr  7 23:35:30 localhost piaware[6641]: Connection with adept server at piaware.flightaware.com/1200 established
Apr  7 23:35:30 localhost piaware[6641]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Apr  7 23:35:30 localhost piaware[6641]: FlightAware server certificate validated
Apr  7 23:35:31 localhost piaware[6641]: encrypted session established with FlightAware
Apr  7 23:35:31 localhost piaware[6641]: logged in to FlightAware as user abcd567
Apr  7 23:35:31 localhost piaware[6641]: my feeder ID is xxxxxxxxxxxx
Apr  7 23:35:31 localhost piaware[6641]: site statistics URL: https://flightaware.com/adsb/stats/user/abcd567#stats-6
Apr  7 23:35:31 localhost piaware[6641]: multilateration data requested
Apr  7 23:35:31 localhost piaware[6641]: error handling message 'clock\t1554680131\ttype\tmlat_enable\tudp_transport\
66 3698495259' from server: can't read "::adsbLocalPort": no such variable, disconnecting and reconnecting..
Apr  7 23:35:31 localhost piaware[6641]: traceback: can't read "::adsbLocalPort": no such variable
Apr  7 23:35:31 localhost piaware[6641]:     while executing
Apr  7 23:35:31 localhost piaware[6641]: "is_local_receiver $::adsbLocalPort"
Apr  7 23:35:31 localhost piaware[6641]:     (procedure "start_mlat_client" line 15)
Apr  7 23:35:31 localhost piaware[6641]:     invoked from within
Apr  7 23:35:31 localhost piaware[6641]: "start_mlat_client"
Apr  7 23:35:31 localhost piaware[6641]:     (procedure "enable_mlat" line 16)
Apr  7 23:35:31 localhost piaware[6641]:     invoked from within
Apr  7 23:35:31 localhost piaware[6641]: "enable_mlat $row(udp_transport)"
Apr  7 23:35:31 localhost piaware[6641]:     ("mlat_enable" arm line 3)
Apr  7 23:35:31 localhost piaware[6641]:     invoked from within
Apr  7 23:35:31 localhost piaware[6641]: "switch -exact $row(type) {
Apr  7 23:35:31 localhost piaware[6641]: #011#011"mlat_enable" {
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011if {[info exists row(udp_transport)]} {
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011#011enable_mlat $row(udp_transport)
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011} else {
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011#011enable_mla..."
Apr  7 23:35:31 localhost piaware[6641]:     (procedure "::forward_to_mlat_client" line 5)
Apr  7 23:35:31 localhost piaware[6641]:     invoked from within
Apr  7 23:35:31 localhost piaware[6641]: "{*}$mlatCommand row"
Apr  7 23:35:31 localhost piaware[6641]:     ("mlat_*" arm line 3)
Apr  7 23:35:31 localhost piaware[6641]:     invoked from within
Apr  7 23:35:31 localhost piaware[6641]: "switch -glob $row(type) {
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011"login_response" {
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011#011handle_login_response_message row
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011}
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011"notice" {
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011#011handle_notice_message row
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011}
Apr  7 23:35:31 localhost piaware[6641]: #011#011#011"aliv..."
Apr  7 23:35:31 localhost piaware[6641]:     (object "::adept" method "::fa_adept::AdeptClient::handle_response" body
Apr  7 23:35:31 localhost piaware[6641]:     invoked from within
Apr  7 23:35:31 localhost piaware[6641]: "handle_response response"
Apr  7 23:35:31 localhost piaware[6641]: multilateration data no longer required, disabling mlat client
Apr  7 23:35:31 localhost piaware[6641]: reconnecting in 55 seconds...
pi@orangepipc:~/piaware_builder$

.

obj · April 8, 2019, 3:12am

You built 3.7.0, not 3.7.0.1

abcd567 · April 8, 2019, 3:27am

Thanks for the tip.
Just in time.
I have just now finished reimaging microSd card with Armbian 5.7.5, and have done apt update, apt upgrade, apt dist-upgrade. Was about to start building 3.7.0 again when saw your reply.

Will now use git checkout v3.7.0.1

abcd567 · April 8, 2019, 4:16am

.
As per your advice, now built v3.7.0.1 - THANKS

.

pi@orangepipc:~/piaware_builder$ apt-cache policy piaware 

piaware:
  Installed: 3.7.0.1
  Candidate: 3.7.0.1
  Version table:
 *** 3.7.0.1 100
        100 /var/lib/dpkg/status

.

pi@orangepipc:~/piaware_builder$ sudo systemctl status piaware -l 

● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-08 00:06:50 EDT; 1min 43s ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 10916 (piaware)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/piaware.service
           ├─10916 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─10949 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhos
           └─10987 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.5xx --lon -79.6xx

Apr 08 00:06:55 orangepipc piaware[10916]: mlat-client(10949): Beast-format results connection with ::1:30104: connection established
Apr 08 00:07:25 orangepipc piaware[10916]: 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
Apr 08 00:07:54 orangepipc sudo[10985]:  piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Apr 08 00:07:54 orangepipc sudo[10985]: pam_unix(sudo:session): session opened for user root by (uid=0)
Apr 08 00:07:54 orangepipc sudo[10985]: pam_unix(sudo:session): session closed for user root
Apr 08 00:07:54 orangepipc piaware[10916]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Apr 08 00:07:54 orangepipc piaware[10916]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --s
Apr 08 00:07:54 orangepipc piaware[10916]: Started faup1090 (pid 10987) to connect to dump1090-fa
Apr 08 00:07:55 orangepipc piaware[10916]: piaware received a message from dump1090-fa!
Apr 08 00:07:56 orangepipc piaware[10916]: piaware has successfully sent several msgs to FlightAware!

.

BONUS: Station marker and range rings also now appeared automatically

abcd567 · April 8, 2019, 5:17am

dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

pi@orangepipc:~$ apt-cache policy dump978-fa 

dump978-fa:
  Installed: 3.7.0.1
  Candidate: 3.7.0.1
  Version table:
 *** 3.7.0.1 100
        100 /var/lib/dpkg/status

.

pi@orangepipc:~$ sudo piaware-config uat-receiver-type sdr 
pi@orangepipc:~$ sudo piaware-config uat-sdr-device driver=rtlsdr,serial=00000978
pi@orangepipc:~$ sudo systemctl restart piaware

.

pi@orangepipc:~$ sudo nano /etc/default/dump978-fa

# dump978-fa configuration
# This is sourced by /usr/share/dump978-fa/start-dump978-fa as a
# shellscript fragment.

# If you are using a PiAware sdcard image, this config file is regenerated
# on boot based on the contents of piaware-config.txt; any changes made to this
# file will be lost.

# dump978-fa won't automatically start unless ENABLED=yes
ENABLED=yes

RECEIVER_OPTIONS="--sdr driver=rtlsdr,serial=00000978  --format CS8"
DECODER_OPTIONS=""
NET_OPTIONS="--raw-port 30978 --json-port 30979"

.

pi@orangepipc:~$ sudo reboot

.

pi@orangepipc:~$ sudo systemctl status dump978-fa
● dump978-fa.service - dump978 ADS-B UAT receiver
   Loaded: loaded (/lib/systemd/system/dump978-fa.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2019-04-08 00:51:22 EDT; 5s ago
     Docs: https://flightaware.com/adsb/piaware/
  Process: 2133 ExecStart=/usr/share/dump978-fa/start-dump978-fa (code=exited, status=2)
 Main PID: 2133 (code=exited, status=2)

Apr 08 00:51:22 orangepipc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 08 00:51:22 orangepipc systemd[1]: dump978-fa.service: Unit entered failed state.
Apr 08 00:51:22 orangepipc systemd[1]: dump978-fa.service: Failed with result 'exit-code'.

.

EDIT:
Tried following, but no success

pi@orangepipc:~$ groups dump978
dump978 : nogroup plugdev

pi@orangepipc:~$ sudo adduser dump978 audio
Adding user `dump978' to group `audio' ...
Adding user dump978 to group audio
Done.

pi@orangepipc:~$ groups dump978
dump978 : nogroup audio plugdev

pi@orangepipc:~$ sudo reboot

wiedehopf · April 8, 2019, 8:19am

As always the log is needed

journalctl -u dump978-fa

abcd567 · April 8, 2019, 3:04pm

pi@orangepipc:~$ sudo journalctl -u dump978-fa 

-- Logs begin at Thu 2016-11-03 13:16:42 EDT, end at Mon 2019-04-08 11:01:34 EDT. --
Apr 08 10:58:43 orangepipc systemd[1]: Started dump978 ADS-B UAT receiver.
Apr 08 10:58:43 orangepipc dump978-fa[733]: raw-port: listening for connections on 0.0.0.0:30978
Apr 08 10:58:43 orangepipc dump978-fa[733]: raw-port: listening for connections on [::]:30978
Apr 08 10:58:43 orangepipc dump978-fa[733]: json-port: listening for connections on 0.0.0.0:30979
Apr 08 10:58:43 orangepipc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 08 10:58:43 orangepipc systemd[1]: dump978-fa.service: Unit entered failed state.
Apr 08 10:58:43 orangepipc systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Apr 08 10:59:29 orangepipc systemd[1]: dump978-fa.service: Service hold-off time over, scheduling restart.
Apr 08 10:59:29 orangepipc systemd[1]: Stopped dump978 ADS-B UAT receiver.
Apr 08 10:59:29 orangepipc systemd[1]: Started dump978 ADS-B UAT receiver.
Apr 08 10:59:29 orangepipc dump978-fa[1677]: raw-port: listening for connections on 0.0.0.0:30978
Apr 08 10:59:29 orangepipc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 08 10:59:29 orangepipc systemd[1]: dump978-fa.service: Unit entered failed state.
Apr 08 10:59:29 orangepipc systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Apr 08 10:59:59 orangepipc systemd[1]: dump978-fa.service: Service hold-off time over, scheduling restart.
Apr 08 10:59:59 orangepipc systemd[1]: Stopped dump978 ADS-B UAT receiver.
Apr 08 10:59:59 orangepipc systemd[1]: Started dump978 ADS-B UAT receiver.
Apr 08 10:59:59 orangepipc dump978-fa[1702]: raw-port: listening for connections on 0.0.0.0:30978
Apr 08 10:59:59 orangepipc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 08 10:59:59 orangepipc systemd[1]: dump978-fa.service: Unit entered failed state.
Apr 08 10:59:59 orangepipc systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Apr 08 11:00:29 orangepipc systemd[1]: dump978-fa.service: Service hold-off time over, scheduling restart.
Apr 08 11:00:29 orangepipc systemd[1]: Stopped dump978 ADS-B UAT receiver.
Apr 08 11:00:29 orangepipc systemd[1]: Started dump978 ADS-B UAT receiver.
Apr 08 11:00:29 orangepipc dump978-fa[1731]: raw-port: listening for connections on 0.0.0.0:30978
Apr 08 11:00:29 orangepipc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 08 11:00:29 orangepipc systemd[1]: dump978-fa.service: Unit entered failed state.
Apr 08 11:00:29 orangepipc systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Apr 08 11:00:59 orangepipc systemd[1]: dump978-fa.service: Service hold-off time over, scheduling restart.
Apr 08 11:00:59 orangepipc systemd[1]: Stopped dump978 ADS-B UAT receiver.
Apr 08 11:00:59 orangepipc systemd[1]: Started dump978 ADS-B UAT receiver.
Apr 08 11:00:59 orangepipc dump978-fa[1752]: raw-port: listening for connections on 0.0.0.0:30978
Apr 08 11:00:59 orangepipc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 08 11:00:59 orangepipc systemd[1]: dump978-fa.service: Unit entered failed state.
Apr 08 11:00:59 orangepipc systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Apr 08 11:01:30 orangepipc systemd[1]: dump978-fa.service: Service hold-off time over, scheduling restart.
pi@orangepipc:~$

wiedehopf · April 8, 2019, 3:23pm

Hmm, strange.

Can you run it without the service?

sudo systemctl stop piaware dump978-fa dump1090-fa
sudo /usr/share/dump978-fa/start-dump978-fa

abcd567 · April 8, 2019, 3:25pm

No, it still fails

pi@orangepipc:~$ sudo systemctl stop piaware dump978-fa dump1090-fa 

pi@orangepipc:~$ sudo /usr/share/dump978-fa/start-dump978-fa 

raw-port: listening for connections on 0.0.0.0:30978
raw-port: listening for connections on [::]:30978
json-port: listening for connections on 0.0.0.0:30979
json-port: listening for connections on [::]:30979
Uncaught exception: Dynamic exception type: std::runtime_error
std::exception::what: SoapySDR::Device::make() no match

.
ADDITIONAL CHECK:

pi@orangepipc:~$ apt-cache policy libsoapysdr-dev
libsoapysdr-dev:
  Installed: 0.5.4-1
  Candidate: 0.5.4-1
  Version table:
 *** 0.5.4-1 500
        500 http://httpredir.debian.org/debian stretch/main armhf Packages
        100 /var/lib/dpkg/status

wiedehopf · April 8, 2019, 3:29pm

Wow that’s not a very helpful error message.

How old is the software you run on that thing, maybe the C++ stuff or soapySDR stuff is not recent enough.

Hmm that should be the same as on the RPi.
No clue to be honest.

Can you show the output of rtl_test ?

abcd567 · April 8, 2019, 3:32pm

libsoapysdr-dev: Installed: 0.5.4-1 Candidate: 0.5.4-1

The Armbian image is the latest

pi@orangepipc:~$ uname -a
Linux orangepipc 4.19.20-sunxi #5.75 SMP Sat Feb 9 19:02:47 CET 2019 armv7l GNU/Linux

.
Before building any packages, I did following:
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade

wiedehopf · April 8, 2019, 3:37pm

Let’s check rtl_test, maybe the dongle serial doesn’t match?

(Hmm, that shows a different error for me)

abcd567 · April 8, 2019, 3:45pm

.

(1) The /etc/default/dump978-fa file

ENABLED=yes

RECEIVER_OPTIONS="--sdr driver=rtlsdr,serial=00000978  --format CS8"
DECODER_OPTIONS=""
NET_OPTIONS="--raw-port 30978 --json-port 30979"

.

(2) The piaware-config

pi@orangepipc:~$ sudo piaware-config -show uat-receiver-type
sdr
pi@orangepipc:~$ sudo piaware-config -show uat-sdr-device
driver=rtlsdr,serial=00000978

.

(3) The rtl_test -t

pi@orangepipc:~$ rtl_test -t 

Found 2 device(s):
  0:  Realtek, RTL2838UHIDIR, SN: 00000978
  1:  Realtek, RTL2832U, SN: 00001090

Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.
Reattached kernel driver

wiedehopf · April 8, 2019, 3:46pm

Ok, do you have the correct module installed?

sudo apt-get install soapysdr-module-rtlsdr

Topic		Replies	Views
Where is dump978-fa? ADS-B Flight Tracking	9	3726	March 6, 2020
Dump1090-fa download problem ADS-B Flight Tracking	12	6482	March 29, 2021
De-installing Dump978-fa? ADS-B Flight Tracking	5	1130	April 25, 2023
Dump978 Add-On Installation Procedures? ADS-B Flight Tracking	116	11596	July 4, 2019
PiAware 3.x and Dump978 ADS-B Flight Tracking	28	12883	September 18, 2018

Version 3.7.0 of dump1090-fa & Piaware

Piaware 3.7.0 + dump1090-fa 3.7.0 on OrangePi PC / Armbian 5.75 (Stretch)

dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

Related topics