Version 3.7.0 of dump1090-fa & Piaware

wiedehopf · April 5, 2019, 12:27pm

There are single quotes ' in the configuration file around driver=rtlsdr which need to be removed.
It is mentioned in this thread at least once, i think

Anyway the official build should be easier indeed.
Be sure to remove the configuration file before installing though or i guess you can fix it manually.

modea · April 5, 2019, 12:35pm

Yep, thanks. made it past that as well and resolved that issue but just couldn’t get a final working config – but ultimately it was 0100 and sleep reminded me “It will be released tomorrow” lol. The rpizw can also be a little flaky.

wiedehopf · April 5, 2019, 12:38pm

Strange. As it’s not yet released feel free to post the config and/or the relevant log (journalctl -u dump978-fa)

modea · April 5, 2019, 12:41pm

I actually wiped the card clean to take a whack at again today so logs are gone and I checked all my buffers - no scrollback logs. If I have time and the official release doesn’t drop today maybe get some time with it.

abcd567 · April 5, 2019, 12:45pm

Not only Pi Zero, my “Raspbian on Pi 2B” as well as “Debian in VM on PC” both gave me a good opportunity to take a nap while the packages were being compiled by sudo dpkg-buildpackage -b

esmathews · April 5, 2019, 1:01pm

3.7.0.1 is here!

LitterBug · April 5, 2019, 2:16pm

Downloading official beta image now. Will fire it up before heading into the woods today for a hike.

Cheers!
LitterBug

abcd567 · April 5, 2019, 2:27pm

Downloaded and wrote Piaware SD card image 3.7.0.1 on a spare microSD card, and fired it up

Serialized dongles: (CLICK HERE)
For 1090 Mhz to 00001090
For 978 Mhz to 00000978
(You can use any other serial numbers if you want)

piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 
piaware-config uat-receiver-type sdr
piaware-config rtlsdr-device-index 00001090
piaware-config uat-sdr-device driver=rtlsdr,serial=00000978
sudo reboot

.

``
.

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-05 13:52:20 UTC; 30min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 339 (dump1090-fa)
   CGroup: /system.slice/dump1090-fa.service
           └─339 /usr/bin/dump1090-fa --net-bo-port 30005 --fix --device-index 00001090 --gain -10 --ppm 0 --max-range 360 --net --net-heartbeat 60

Apr 05 13:52:20 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 05 13:52:21 piaware dump1090-fa[339]: Fri Apr  5 13:52:21 2019 UTC  dump1090-fa 3.7.0.1 starting up.
Apr 05 13:52:21 piaware dump1090-fa[339]: rtlsdr: using device #1: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00001090)
Apr 05 13:52:21 piaware dump1090-fa[339]: Detached kernel driver
Apr 05 13:52:22 piaware dump1090-fa[339]: Found Rafael Micro R820T tuner
Apr 05 13:52:22 piaware dump1090-fa[339]: rtlsdr: enabling tuner AGC

.

pi@piaware:~ $ 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: active (running) since Fri 2019-04-05 13:52:20 UTC; 29min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 342 (dump978-fa)
   CGroup: /system.slice/dump978-fa.service
           └─342 /usr/bin/dump978-fa --sdr driver=rtlsdr --raw-port 30978 --json-port 30979

Apr 05 13:52:22 piaware dump978-fa[342]: Reattached kernel driver
Apr 05 13:52:22 piaware dump978-fa[342]: usb_claim_interface error -6
Apr 05 13:52:23 piaware dump978-fa[342]: Detached kernel driver
Apr 05 13:52:23 piaware dump978-fa[342]: Found Rafael Micro R820T tuner
Apr 05 13:52:23 piaware dump978-fa[342]: Exact sample rate is: 2083333.135571 Hz
Apr 05 13:52:23 piaware dump978-fa[342]: [R82XX] PLL not locked!
Apr 05 13:52:23 piaware dump978-fa[342]: SoapySDR: using maximum manual gain 49.6 dB
Apr 05 13:52:23 piaware dump978-fa[342]: SoapySDR: INFO: Using format CS8.
Apr 05 13:52:23 piaware dump978-fa[342]: [::]:30978: accepted a connection from [::1]:60598
Apr 05 13:52:25 piaware dump978-fa[342]: [::]:30978: accepted a connection from [::1]:60602

.

pi@piaware:~ $ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-04-05 13:52:20 UTC; 32min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 348 (piaware)
   CGroup: /system.slice/piaware.service
           ├─348 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─507 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.5xx --lon -79.6xx
           ├─516 /usr/lib/piaware/helpers/faup978 --connect localhost:30978
           └─917 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:301

Apr 05 14:17:56 piaware piaware[348]: 4360 msgs recv'd from dump1090-fa (1004 in last 5m); 4123 msgs sent to FlightAware
Apr 05 14:17:56 piaware piaware[348]: 0 msgs recv'd from dump978-fa (0 in last 5m); 0 msgs sent to FlightAware
Apr 05 14:22:56 piaware piaware[348]: 5427 msgs recv'd from dump1090-fa (1067 in last 5m); 5190 msgs sent to FlightAware
Apr 05 14:22:56 piaware piaware[348]: 0 msgs recv'd from dump978-fa (0 in last 5m); 0 msgs sent to FlightAware
Apr 05 14:23:47 piaware piaware[348]: mlat-client(917): Receiver status: connected
Apr 05 14:23:47 piaware piaware[348]: mlat-client(917): Server status:   synchronized with 132 nearby receivers
Apr 05 14:23:47 piaware piaware[348]: mlat-client(917): Receiver:  159.0 msg/s received       54.7 msg/s processed (34%)
Apr 05 14:23:47 piaware piaware[348]: mlat-client(917): Server:      0.2 kB/s from server    0.0kB/s TCP to server     0.7kB/s UDP to server
Apr 05 14:23:47 piaware piaware[348]: mlat-client(917): Results:  71.5 positions/minute
Apr 05 14:23:47 piaware piaware[348]: mlat-client(917): Aircraft: 15 of 28 Mode S, 25 of 33 ADS-B used

LitterBug · April 5, 2019, 2:50pm

Fired unit up with new image and it came up on 1090 fine on my 978 antenna. Reconfigured for UAT. As luck would have it, it’s overcast, rainy, and not otherwise a good GA day and there is nothing to see right now. LOL.

Cheers!
LitterBug

abcd567 · April 5, 2019, 3:02pm

I solved it by following:
Serialized dongles: (CLICK HERE)
For 1090 Mhz to 00001090
For 978 Mhz to 00000978

(You can use different numbers if you desire. I used above as it is easy to recognize which dongle is for what. Thanks to @wiedehopf and @N456TS for suggestion to use 00001090 & 00000978)

Then gave these commands:

piaware-config uat-receiver-type sdr
piaware-config rtlsdr-device-index 00001090
piaware-config uat-sdr-device driver=rtlsdr,serial=00000978

sudo reboot

bramjacobse · April 5, 2019, 3:50pm

Installed 3.7.0

have timing error

piaware received a message from dump1090-fa!
Apr 5 15:47:27 adsb piaware[20514]: multilateration data requested
Apr 5 15:47:27 adsb piaware[20514]: error handling message ‘clock\t1554479247\ttype\tmlat_enable\tudp_transport\t70.42.6.191 8793 3075530221’ from server: can’t read “::adsbLocalPort”: no
such variable, disconnecting and reconnecting…
Apr 5 15:47:27 adsb piaware[20514]: traceback: can’t read “::adsbLocalPort”: no such variable
Apr 5 15:47:27 adsb piaware[20514]: while executing
Apr 5 15:47:27 adsb piaware[20514]: “is_local_receiver $::adsbLocalPort”
Apr 5 15:47:27 adsb piaware[20514]: (procedure “start_mlat_client” line 15)
Apr 5 15:47:27 adsb piaware[20514]: invoked from within
Apr 5 15:47:27 adsb piaware[20514]: “start_mlat_client”
Apr 5 15:47:27 adsb piaware[20514]: (procedure “enable_mlat” line 16)
Apr 5 15:47:27 adsb piaware[20514]: invoked from within
Apr 5 15:47:27 adsb piaware[20514]: “enable_mlat $row(udp_transport)”
Apr 5 15:47:27 adsb piaware[20514]: (“mlat_enable” arm line 3)
Apr 5 15:47:27 adsb piaware[20514]: invoked from within
Apr 5 15:47:27 adsb piaware[20514]: “switch -exact $row(type) {
Apr 5 15:47:27 adsb piaware[20514]: “mlat_enable” {
Apr 5 15:47:27 adsb piaware[20514]: if {[info exists row(udp_transport)]} {
Apr 5 15:47:27 adsb piaware[20514]: enable_mlat $row(udp_transport)
Apr 5 15:47:27 adsb piaware[20514]: } else {
Apr 5 15:47:27 adsb piaware[20514]: enable_mla…”
Apr 5 15:47:27 adsb piaware[20514]: (procedure “::forward_to_mlat_client” line 5)
Apr 5 15:47:27 adsb piaware[20514]: invoked from within
Apr 5 15:47:27 adsb piaware[20514]: “{}$mlatCommand row"
Apr 5 15:47:27 adsb piaware[20514]: ("mlat_” arm line 3)
Apr 5 15:47:27 adsb piaware[20514]: invoked from within
Apr 5 15:47:27 adsb piaware[20514]: "switch -glob $row(type) {
Apr 5 15:47:27 adsb piaware[20514]: “login_response” {
Apr 5 15:47:27 adsb piaware[20514]: handle_login_response_message row
Apr 5 15:47:27 adsb piaware[20514]: }
Apr 5 15:47:27 adsb piaware[20514]: “notice” {
Apr 5 15:47:27 adsb piaware[20514]: handle_notice_message row
Apr 5 15:47:27 adsb piaware[20514]: }
Apr 5 15:47:27 adsb piaware[20514]: “aliv…”
Apr 5 15:47:27 adsb piaware[20514]: (object “::adept” method “::fa_adept::AdeptClient::handle_response” body line 4)

eric1tran · April 5, 2019, 3:54pm

We’ve fixed this issue on 3.7.0.1. Please use the SD image that was posted this morning in this thread:

wcnjsmith · April 5, 2019, 4:28pm

Thank you for the assistance

bramjacobse · April 5, 2019, 4:36pm

Thanks, Up and running

wiedehopf · April 5, 2019, 4:42pm

Seems the lat/long fix is also needed for dump978/skyview978, i’ve made a pull request.

There is also a compilation error for dump978 when using gcc8, made a pull request for a fix for that as well.

tahoeadsb · April 5, 2019, 8:18pm

I loaded the new image and it comes up but I cannot access the Pi now. It has an IP address that I can ping but it is refusing SSH connections. Am I missing something regarding how to access it?

LitterBug · April 5, 2019, 8:22pm

After writing the .img file to the SD card, put an empty file named “ssh” in the “boot” partition before mounting it on the pi. That will enable ssh. If you hook up a keboard and montitor, you could do it by doing a “sudo touch /boot/ssh”

Regards,
LitterBug

biekerc · April 5, 2019, 8:22pm

you put an empty text file named ssh into the boot directory?

KCGSOperations · April 5, 2019, 9:45pm

Yes. And if I remember correctly it should just be SSH. Remove the file extension .txt after saving it.

wiedehopf · April 5, 2019, 9:49pm

Pretty sure they included ssh.txt as a valid file to activate ssh to help out Windows users

Topic		Replies	Views
Dump978 Add-On Installation Procedures? ADS-B Flight Tracking	116	11823	July 4, 2019
Can't get dump 978 working ADS-B Flight Tracking	53	4546	September 29, 2020
Add UAT to existing ADS-B PiAware 7.2 add on ADS-B Flight Tracking	52	3776	December 29, 2023
Attempting to add 978, but unsuccessful ADS-B Flight Tracking	59	1081	February 22, 2025
Dump978 error help (short write, samples lost, exiting) ADS-B Flight Tracking	13	1056	February 5, 2023

Version 3.7.0 of dump1090-fa & Piaware

Related topics