The dump1090-fa was working ok last night when I started it and piaware (by rebooting Pi) at about 1 am last night. The Piaware status showed it received messages from dump1090-fa, and sent to Flightaware.Please see last 4 lines below
Well when you set the receiver type to UAT it will not use dump1090-fa data.
Currently if you want to feed UAT and 1090 then you need two piaware instances.
Strange that it still does MLAT using the data from port 30005 when in UAT mode though, doesn’t make sense.
That I did only 3 hrs ago at about 2pm today. Why there was no ADS-B data from 1 am to 2pm (13 hrs) on 29 March (today)?
I don’t know maybe you are using a bad version, mine works just fine.
Or maybe you are confusing two stations?
Just turn the UAT mode off and check again maybe?
No there is no confusion about stations. I am experimenting on RaspberryPi, which is station 5252. The other station is 6396, which is Orange Pi located in another room. There is no chance of confusion.
Restarted dump1090-fa. No luck.
[2019-03-29 17:26 EDT] manual update (user-initiated via their flightaware control page) requested by adept server
[2019-03-29 17:26 EDT] performing manual update, action: restart_dump1090
[2019-03-29 17:26 EDT] update request complete
[2019-03-29 17:26 EDT] attempting to restart dump1090-fa using 'systemctl --no-block try-restart dump1090-fa.service < /dev/null'...
[2019-03-29 17:26 EDT] attempting to restart dump1090..
[2019-03-29 17:26 EDT] mlat-client(737): Beast-format results connection with ::1:30104: connection lost
[2019-03-29 17:26 EDT] dump1090 restart appears to have been successful
[2019-03-29 17:26 EDT] mlat-client(737): Lost connection to localhost:30005
[2019-03-29 17:26 EDT] mlat-client(737): Reconnecting in 30.0 seconds
[2019-03-29 17:26 EDT] no ADS-B data program seen listening on port 30978 for 71 seconds, next check in 60s
[2019-03-29 17:26 EDT] mlat-client(737): Beast-format results connection with 127.0.0.1:30104: connection established
[2019-03-29 17:26 EDT] mlat-client(737): Input format changed to BEAST, 12MHz clock
[2019-03-29 17:27 EDT] no ADS-B data program seen listening on port 30978 for 131 seconds, next check in 60s
[2019-03-29 17:28 EDT] no ADS-B data program seen listening on port 30978 for 191 seconds, next check in 60s
what are you trying to run anyway?
why do you have dump1090-fa running at all if you want to run dump978?
I guess he wants to run both.
If you don’t set the receiver type back to rtl-sdr for you piaware the piaware won’t use dump1090-fa.
sudo su -l
piaware-config receiver-type rtlsdr
piaware-config uat-receiver-type none
systemctl restart piaware
If you want to test dump978 you should just stop dump1090-fa.
I compiled myself dump978 just for trying it even if there are no UAT planes around.
But it doesn’t work correctly on my x86_64 laptop.
Don’t feel like compiling all that C++ boost stuff on my main feeder (the pi)
I used a spare microSD card, and wrote on it Raspbian Stretch image. I then slipped out my normal microSD card, and slipped in the spare microSD card, and compiled dump1090-fa 3.7.0 and piaware 3.7.0. This is the card now powering my station 5252.
When my trial is over, I will slip out spare microSD card, and slip in the normal microSD card with ver 3.6.3, restoring my station 5252 back to normal.
2 Likes
(3) Installed dump978
3.1 - Installed dependencies & build tools
sudo apt update
sudo apt install build-essential debhelper dh-systemd
sudo apt install libboost-system-dev libboost-program-options-dev libboost-regex-dev
sudo apt install libboost-filesystem-dev libsoapysdr-dev soapysdr-module-rtlsdr
EDIT: soapysdr-module-rtlsdr was added in above commands later (April 8, 2019).
.
3.2 - Cloned source code, checkout to ver 3.7.0, and built package
git clone https://github.com/flightaware/dump978.git
cd dump978
git checkout v3.7.0
.... ....
.... ....
HEAD is now at 7bc0a43... Release 3.7.0
sudo dpkg-buildpackage -b
.
3.3 - Checked if package is actually built
cd ../
ls
dump1090_3.7.0_all.deb dump1090-fa-dbgsym_3.7.0_armhf.deb dump978-fa-dbgsym_3.7.0_armhf.deb
dump1090-fa dump978 piaware_builder
dump1090-fa_3.7.0_armhf.buildinfo dump978-fa_3.7.0_armhf.buildinfo skyview978_3.7.0_armhf.deb
dump1090-fa_3.7.0_armhf.changes dump978-fa_3.7.0_armhf.changes skyview978-dbgsym_3.7.0_armhf.deb
dump1090-fa_3.7.0_armhf.deb dump978-fa_3.7.0_armhf.deb
.
3.4 - Installed dump978
sudo dpkg -i dump978-fa_3.7.0_armhf.deb
Selecting previously unselected package dump978-fa.
(Reading database ... 59002 files and directories currently installed.)
Preparing to unpack dump978-fa_3.7.0_armhf.deb ...
Unpacking dump978-fa (3.7.0) ...
Setting up dump978-fa (3.7.0) ...
Adding user `dump978' to group `plugdev' ...
Adding user dump978 to group plugdev
Done.
Created symlink /etc/systemd/system/default.target.wants/dump978-fa.service → /lib/systemd/system/dump978-fa.service.
sudo reboot
.
3.5 Checked Status Piaware - RUNNING
Mar 30 02:37:02 raspberrypi piaware[904]: creating pidfile /run/piaware/piaware.pid
Mar 30 02:37:02 raspberrypi piaware[904]: ****************************************************
Mar 30 02:37:02 raspberrypi piaware[904]: piaware version 3.7.0 is running, process ID 904
Mar 30 02:37:02 raspberrypi piaware[904]: your system info is: Linux raspberrypi 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
Mar 30 02:37:04 raspberrypi piaware[904]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Mar 30 02:37:04 raspberrypi piaware[904]: Connection with adept server at piaware.flightaware.com/1200 established
Mar 30 02:37:04 raspberrypi piaware[904]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Mar 30 02:37:04 raspberrypi piaware[904]: FlightAware server certificate validated
Mar 30 02:37:04 raspberrypi piaware[904]: encrypted session established with FlightAware
Mar 30 02:37:05 raspberrypi piaware[904]: adept reported location: 43.xxxxx, -79.xxxxx, xxxft AMSL
Mar 30 02:37:05 raspberrypi piaware[904]: logged in to FlightAware as user abcd567
Mar 30 02:37:05 raspberrypi piaware[904]: my feeder ID is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Mar 30 02:37:05 raspberrypi piaware[904]: site statistics URL: https://flightaware.com/adsb/stats/user/abcd567#stats-5252
Mar 30 02:37:05 raspberrypi piaware[904]: multilateration data requested
Mar 30 02:37:05 raspberrypi piaware[904]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.198:8735:3575166541
Mar 30 02:37:05 raspberrypi piaware[904]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Mar 30 02:37:05 raspberrypi piaware[904]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.xxx --lon -79.xxx
Mar 30 02:37:05 raspberrypi piaware[904]: Started faup1090 (pid 940) to connect to dump1090-fa
Mar 30 02:37:05 raspberrypi piaware[904]: no ADS-B data program seen listening on port 30978 for 3 seconds, next check in 60s
Mar 30 02:37:06 raspberrypi piaware[904]: mlat-client(931): fa-mlat-client 0.2.10 starting up
Mar 30 02:37:06 raspberrypi piaware[904]: mlat-client(931): Using UDP transport to 70.42.6.198 port 8735
Mar 30 02:37:06 raspberrypi piaware[904]: mlat-client(931): Listening for Beast-format results connection on port 30105
Mar 30 02:37:06 raspberrypi piaware[904]: mlat-client(931): Listening for Extended Basestation-format results connection on port 30106
Mar 30 02:37:06 raspberrypi piaware[904]: mlat-client(931): Input connected to localhost:30005
Mar 30 02:37:06 raspberrypi piaware[904]: mlat-client(931): Input format changed to BEAST, 12MHz clock
Mar 30 02:37:06 raspberrypi piaware[904]: mlat-client(931): Beast-format results connection with ::1:30104: connection established
Mar 30 02:37:07 raspberrypi piaware[904]: piaware received a message from dump1090-fa!
Mar 30 02:37:21 raspberrypi piaware[904]: piaware has successfully sent several msgs to FlightAware!
Mar 30 02:37:37 raspberrypi piaware[904]: 10 msgs recv'd from dump1090-fa; 10 msgs sent to FlightAware
Mar 30 02:37:37 raspberrypi piaware[904]: 0 msgs recv'd from dump978; 0 msgs sent to FlightAware
Mar 30 02:38:05 raspberrypi piaware[904]: no ADS-B data program seen listening on port 30978 for 63 seconds, next check in 60s
Mar 30 02:39:06 raspberrypi piaware[904]: no ADS-B data program seen listening on port 30978 for 124 seconds, next check in 60s
.
3.6 - Checked Status dump1090-fa - RUNNING
pi@raspberrypi:~ $ 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 Sat 2019-03-30 02:36:09 EDT; 7min ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 429 (dump1090-fa)
CGroup: /system.slice/dump1090-fa.service
└─429 /usr/bin/dump1090-fa --device-index 0 --gain -10 --ppm 0 --net-bo-port 30005 --max-range 360 --net --net-heartbe
Mar 30 02:36:09 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Mar 30 02:36:09 raspberrypi dump1090-fa[429]: Sat Mar 30 02:36:09 2019 EDT dump1090-fa 3.7.0 starting up.
Mar 30 02:36:10 raspberrypi dump1090-fa[429]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832UFA, SN 00000001)
Mar 30 02:36:10 raspberrypi dump1090-fa[429]: Detached kernel driver
Mar 30 02:36:10 raspberrypi dump1090-fa[429]: Found Rafael Micro R820T tuner
Mar 30 02:36:11 raspberrypi dump1090-fa[429]: rtlsdr: enabling tuner AGC
.
3.7 - Checked status dump978-fa - 
FAILED
pi@raspberrypi:~ $ 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 Sat 2019-03-30 02:44:46 EDT; 27s ago
Docs: https://flightaware.com/adsb/piaware/
Process: 1648 ExecStart=/usr/share/dump978-fa/start-dump978-fa (code=exited, status=2)
Main PID: 1648 (code=exited, status=2)
Mar 30 02:44:46 raspberrypi systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
.
3.8 - Checked Dongle 0 & Dongle 1 - BOTH DONGLES ARE OK
pi@raspberrypi:~ $ sudo systemctl stop dump1090-fa
pi@raspberrypi:~ $ sudo systemctl stop dump978-fa
pi@raspberrypi:~ $ rtl_test -t -d 0
Found 2 device(s):
0: Realtek, RTL2832UFA, SN: 00000001
1: Generic, RTL2832U, SN: 77771111153705700
Using device 0: Generic RTL2832U
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
pi@raspberrypi:~ $ rtl_test -t -d 1
Found 2 device(s):
0: Realtek, RTL2832UFA, SN: 00000001
1: Generic, RTL2832U, SN: 77771111153705700
Using device 1: Generic RTL2832U
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
3.9 - Serial number of dongle 1 abnormal (SN: 77771111153705700), tried to fix it - FAILED
pi@raspberrypi:~ $ rtl_eeprom -s 00000000 -d 1
Found 2 device(s):
0: Generic RTL2832U
1: Generic RTL2832U
Using device 1: Generic RTL2832U
Detached kernel driver
Found Rafael Micro R820T tuner
Current configuration:
Error: invalid RTL2832 EEPROM header!
Error: invalid string descriptor!
Error: invalid string descriptor!
Error: invalid string descriptor!
__________________________________________
Vendor ID: 0xa0a0
Product ID: 0x9880
Manufacturer:
Product: ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Serial number:
Serial number enabled: no
IR endpoint enabled: no
Remote wakeup enabled: no
__________________________________________
New configuration:
Error: string too long, truncated!
Reattached kernel driver
3.10 - Used another dongle, still dump978-fa FAILED
.
1 Like
Try to make dump1090-fa use device 1.
I am not sure how you even specify the device for dump978 because it uses the soapy sdr driver indirectly using rtl-sdr or something like that.
So the configuration is different.
So first stop dump1090-fa and see if you can make dump978 work alone.
Already tried it, no luck. 
sudo systemctl stop dump1090-fa
sudo systemctl restart dump978-fa
Then check the dump978-fa log:
journalctl -u dump978-fa -f
What the hell “audio” is doing here?
pi@raspberrypi:~ $ journalctl -u dump978-fa -f
-- Logs begin at Sat 2019-03-30 03:22:16 EDT. --
Mar 30 08:29:23 raspberrypi dump978-fa[29714]: Cannot connect to server request channel
Mar 30 08:29:23 raspberrypi dump978-fa[29714]: jack server is not running or cannot be started
Mar 30 08:29:23 raspberrypi dump978-fa[29714]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 30 08:29:23 raspberrypi dump978-fa[29714]: SoapySDR: using maximum manual gain 0.0 dB
Mar 30 08:29:23 raspberrypi dump978-fa[29714]: SoapySDR: INFO: Using format CS8.
Mar 30 08:29:23 raspberrypi dump978-fa[29714]: Uncaught exception: Dynamic exception type: std::runtime_error
Mar 30 08:29:23 raspberrypi dump978-fa[29714]: std::exception::what: RtAudio init error 'RtApiPulse::probeDeviceOpen: unsupported sample rate.
Mar 30 08:29:23 raspberrypi systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 30 08:29:23 raspberrypi systemd[1]: dump978-fa.service: Unit entered failed state.
Mar 30 08:29:23 raspberrypi systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
Mar 30 08:29:53 raspberrypi systemd[1]: dump978-fa.service: Service hold-off time over, scheduling restart.
Mar 30 08:29:53 raspberrypi systemd[1]: Stopped dump978 ADS-B UAT receiver.
Mar 30 08:29:53 raspberrypi systemd[1]: Started dump978 ADS-B UAT receiver.
Mar 30 08:29:53 raspberrypi dump978-fa[29799]: raw-port: listening for connections on 0.0.0.0:30978
Mar 30 08:29:53 raspberrypi dump978-fa[29799]: raw-port: listening for connections on [::]:30978
Mar 30 08:29:53 raspberrypi dump978-fa[29799]: json-port: listening for connections on 0.0.0.0:30979
Mar 30 08:29:53 raspberrypi dump978-fa[29799]: json-port: listening for connections on [::]:30979
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: Cannot connect to server socket err = No such file or directory
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: Cannot connect to server request channel
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: jack server is not running or cannot be started
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: usb_claim_interface error -6
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: Detached kernel driver
Mar 30 08:29:54 raspberrypi dump978-fa[29799]: Found Rafael Micro R820T tuner
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: Reattached kernel driver
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: Cannot connect to server socket err = No such file or directory
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: Cannot connect to server request channel
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: jack server is not running or cannot be started
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: Cannot connect to server socket err = No such file or directory
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: Cannot connect to server request channel
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: jack server is not running or cannot be started
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: SoapySDR: using maximum manual gain 0.0 dB
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: SoapySDR: INFO: Using format CS8.
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: Uncaught exception: Dynamic exception type: std::runtime_error
Mar 30 08:29:55 raspberrypi dump978-fa[29799]: std::exception::what: RtAudio init error 'RtApiPulse::probeDeviceOpen: unsupported sample rate.
Mar 30 08:29:56 raspberrypi systemd[1]: dump978-fa.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 30 08:29:56 raspberrypi systemd[1]: dump978-fa.service: Unit entered failed state.
Mar 30 08:29:56 raspberrypi systemd[1]: dump978-fa.service: Failed with result 'exit-code
I get the exact same error on my debian unstable x264 system.
Seems the new dump978 version is not quite ready to be used.
It’s some kind of permission problem.
This fixes it:
sudo usermod -a -G audio dump978
For whatever reason soapysdr wants to open a pcm sound device -.-
I appreciate the enthusiasm but this is not yet released and stuff is going to break especially stats-related until we’ve completed the release. I suggest you wait for the sdcard image which should “just work”.
You have soapysdr-module-audio installed. This is for “soundcard” SDRs (where you feed the baseband signal to an audio input). The sdcard image we’re testing doesn’t see this failure because that package is not installed; but it’s still useful to know. It’s unfortunate that it looks like merely having the module installed causes an outright failure even though the driver=rtlsdr device string should cause all the audio stuff to be skipped.
1 Like
Just to clarify, we do support two dongles (assuming you can physically fit and power them) but
a) there’s no unified skyview for them;
b) you will need to ensure that you make both dump1090 and dump978 use the right dongle; they have different mechanisms for this.
1 Like
I’ll shut off the new version of piaware until it is the released version.
Adding the dump978 user to the audio group should be an easy enough fix.
(And it seems this problem will come up for the package install)
Would that be something you would do on the official version or do you think dump978 just shouldn’t be in the audio group. (had a pull request ready to go)