Dump978-fa reports USB_Claim_Interface error -6 after PiAware 7.2 update

FlightAware ADS-B Flight Tracking
1

Updated to 7.2 PiAware software and have the same problem reported by winsortc (June "21) in Dump978-fa reports USB_Claim_Interface error -6 thread.

The 978 dongle will not connect to device 0.

Ran rtl_test -t and found
Found 2 device(s):
0: Realtek, RTL2832U, SN: 00001090
1: Realtec, RTL2832U, SN: 00000978

Using device 0: Generic RTL2832U
usb_claim_interface error -6
Failed to open rtlsdr device #0

pi@piaware:- $ sudo piaware-status
PiAware master process (piaware) is running with pid 459.
PiAware ADS-B client (faup1090) is running with pid 1910.
PiAware ADS-B UAT client (faup978 is not running.
PiAware mlat client (fa-mlat-client) is running with pid 908.
Local ADS-B reciever (dump1090-fa) is running with pid 1864.
Local ADS-B UAT reciever (dump978) is not running.

dump1090-fa (pid 1864) is listening for ES connections on port 30005.
no program appears to be listening for UAT connections on port 30978.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

got ‘couldn’t open socket: connection refused’
dump978 in NOT producing data on localhost::30978.
dump1090 is producing data on localhost::30005.

Your feeder ID is e79350df-5b41-4e09-517c-6aaac3e65571 (configured at /boot/piaware-config.txt:12)

2

Device #0 (Serial #00001090) is NOT dongle for dump978-fa, it is dongle for dump1090-fa

 

Test failed to open device #0 because device 0 is being used ny dump1090-fa. It has nothing to do with dump978-fa, which uses device #1 (serial # 00000978)

What are outputs of following commands?

rtl_test -d 1 -t

sudo systemctl status dump978-fa

 

3

Sorry, don’t remember journal command.

Plugged in 978 dongle by itself on Nov 10th and it returned results to FlightAware. According to Old Posts about subject 978 dongle wants to be device 0 and won’t connect if it’s not.

What happened with Update 7.2? It’s been working fine with prior updates.
See results attached.

PiAware results.png
PiAware results.png925×1040 52.7 KB

rtl-test results.png
rtl-test results.png725×562 26.4 KB

4

What is output of last command below (the journalctl command)

## First REBOOT Pi
sudo reboot  

## Immediately after reboot, give following command
sudo journalctl -u dump978-fa -b

 

Click on screenshot to see larger size

image
image1057×500 63.9 KB

5

Journalresults
Journalresults1253×914 77.4 KB

6

image
image876×92 5.43 KB

Please post output of following commands:

sudo piaware-config -show uat-receiver-type

sudo piaware-config -show uat-sdr-device

 

image

7

cat output.png
cat output.png845×418 22.9 KB

8

Just noticed the rtl_test -t command returns the serial number as 00000978 but the RECEIVER_OPTIONS returns serial=000000978 with an extra zero.

9

Yes, that is the reason for failure of dump978-fa.

 

image

As you have piaware SD card image, do NOT make any changes in file /etc/default/dump978-fa, as it will be overwritten on boot. Make changes in config using command sudo piaware-config as follows:

NOTE: To prevent mistake in the serial number, do NOT type the command. Instead copy-paste from below

sudo piaware-config uat-sdr-device driver=rtlsdr,serial=00000978    

sudo systemctl restart piaware   

sudo systemctl restart dump978-fa

CHECK

sudo piaware-config -show uat-sdr-device

 

10

Performed the code entries you requested. You did mean for the third command to be sudo systemctl restart dump978-fa (and not the dump878-fa)?

Skyaware978 now shows as device 0 and the map is present but no targets reported. Current weather is not good for small aircraft that aren’t certified for flight into known icing, Will monitor results to see if flights log when weather improves.

Never made any changes in file /etc/default/dump978-fa Also, if the Pi is rebooted will the above commands have to be reinstalled?

Thanks for your help!

Lowell

Dump978results.png
Dump978results.png741×418 28 KB

11

 

Oops typo! Thanks for pointing out.
I have now corrected it, so that in case someone tries to use it in future, wont get confused. :wink:

 

 

Same here in Toronto. Light snowfall and no GA flights

 

image
image766×464 125 KB

12

Changes most likely happened due to malfuntion during upgrade. Anyway if a correct value is saved in file /boot/piaware-config.txt , the error will be overwritten by correct value on reboot

As you have Piaware SD card image, you dont have to issue sudo piaware-config commands again. The changes in file /etc/default/dump978-fa and /etc/default/dump1090-fa are not permanent. These get over-written on boot by the values saved in file /boot/piaware-config.txt.

To see the settings saved in file /boot/piaware-config.txt, open it in nano editor

pi@piaware:~ $ sudo nano /boot/piaware-config.txt

When above file opens in nano editor, scroll down to it’s bottom. You will see the saved settings:

Click on Screeshot to see larger size

image
image783×463 24.7 KB

13

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.