Ongoing Problems With Site

Hello. I have been experiencing ongoing problems with my site. I have the blue USB device. My site show an error with MLAT. The note says “MLAT disabled/not synchronized/Latitude Longtitude Not Set”. When I go into device settings it shows “Manually enter location” under Receiver Location. But I cannot interact with the box. When I look at the MLAT section it says MLAT is enabled and my location is correctly displayed. There is however a message saying “This feeder has been inactive for an extended period of time.” And offering the option to delete the feeder from my account.

When I look at the log I see lots of “30005, not starting multilateration client yet
[2023-04-03 12:53 AEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2023-04-03 12:54 AEST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2023-04-03 12:54 AEST] no ADS-B data program is serving on port 30005, not starting multilateration client yet”

I have regularly did the upgrade and restart but it doesnt fox the issue. Currently my feeder type is PiAware (Debian Package Add-on) 8.2

Site Information shows PiAware working and connected to FlightAware.

I also seem to see days in a row where the device has detected no aircraft. I also received emails that my device isnt reporting. But when I look at my webpage I see PiAware working and FlightAware connected.

Also when I click the View Live data link it shows me a map of Portugal. I live in east coast Australia.

Anyone have an idea what is wrong?

The dump1090-fa is NOT working.
Either dump1090-fa software has failed OR the Dongle has failed

Please post output of following commands:

sudo systemctl status dump1090-fa   

sudo journalctl -u dump1090-fa  -n 20   

 

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 pres
Active: activating (auto-restart) (Result: exit-code) since Mon 2023-04-03 06
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 17307 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json
Main PID: 17307 (code=exited, status=1/FAILURE)
lines 1-6/6 (END)…skipping…
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2023-04-03 06:01:22 BST; 20s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 17307 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1
Main PID: 17307 (code=exited, status=1/FAILURE)

sudo journalctl -u dump1090-fa -n 20
– Logs begin at Thu 2023-03-30 05:25:15 BST, end at Mon 2023-04-03 06:02:28 BST. –
Apr 03 06:01:52 raspberrypi systemd[1]: dump1090-fa.service: Service RestartSec=30s expired, scheduling restart.
Apr 03 06:01:52 raspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 18259.
Apr 03 06:01:52 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Apr 03 06:01:52 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 03 06:01:52 raspberrypi dump1090-fa[17319]: Mon Apr 3 06:01:52 2023 BST dump1090-fa 6.1 starting up.
Apr 03 06:01:52 raspberrypi dump1090-fa[17319]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 0000100
Apr 03 06:01:52 raspberrypi dump1090-fa[17319]: usb_claim_interface error -6
Apr 03 06:01:52 raspberrypi dump1090-fa[17319]: rtlsdr: error opening the RTLSDR device: Device or resource busy
Apr 03 06:01:52 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Apr 03 06:01:52 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Apr 03 06:02:22 raspberrypi systemd[1]: dump1090-fa.service: Service RestartSec=30s expired, scheduling restart.
Apr 03 06:02:22 raspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 18260.
Apr 03 06:02:22 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Apr 03 06:02:22 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Apr 03 06:02:22 raspberrypi dump1090-fa[17327]: Mon Apr 3 06:02:22 2023 BST dump1090-fa 6.1 starting up.
Apr 03 06:02:22 raspberrypi dump1090-fa[17327]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 0000100
Apr 03 06:02:22 raspberrypi dump1090-fa[17327]: usb_claim_interface error -6
Apr 03 06:02:22 raspberrypi dump1090-fa[17327]: rtlsdr: error opening the RTLSDR device: Device or resource busy
Apr 03 06:02:22 raspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Apr 03 06:02:22 raspberrypi systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.

The dump1090-fa is repeatedly trying to start, but fails. Most likely dongle issue.

Let us check the dongle. Please issue following commands, and post output of last command below

sudo apt install rtl-sdr   

sudo systemctl stop piaware dump1090-fa   

rtl_test -t  

 

That means some other software is using the SDR.
Post the output for these commands:

pgrep -fa readsb
pgrep -fa dump
pgrep -fa rtl

pi@raspberrypi:~ $ pgrep -fa readsb
pi@raspberrypi:~ $ pgrep -fa dump
568 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 --adaptive-range --fix --lat -27.89534 --lon 153.28017 --max-range 360 --net-ro-port 30002 --net -sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-ac curacy 1 --write-json /run/dump1090-fa
640 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --in put-type dump1090 --results beast,connect,localhost:30104 --results beast,listen ,30105 --results ext_basestation,listen,30106 --udp-transport 206.253.84.196:601 7:2218087955
710 /usr/bin/dump978-fa --sdr driver=rtlsdr --format CS8 --raw-port 30978 --json -port 30979
pi@raspberrypi:~ $ pgrep -fa rtl
568 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 --adaptive-range --fix --lat -27.89534 --lon 153.28017 --max-range 360 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --write-json /run/dump1090-fa
pi@raspberrypi:~ $

pi@raspberrypi:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000

Using device 0: Generic RTL2832U
usb_claim_interface error -6

Please issue following commands to stop piaware and dump1090-fa, then run the test.

Post result of last comnand

sudo systemctl stop piaware dump1090-fa   

rtl_test -t  

 

You appear to be trying to run both a 1090 and a 978 receiver. You need two dongles, individually serialized, and appropriate configuration for this to work correctly.

In your case where you have only one dongle, dump1090 and dump978 are fighting over access to the hardware.

ok. what do i do about it? I just have the one dongle (the blue one) plugged into my Raspberry pi.

Quick and dirty approach. Try:

sudo systemctl stop dump978-fa
sudo systemctl disable dump978-fa

Then restart.

UAT / 978 isn’t used in Australia, so no need for it here.

2 Likes

thankyou very much. ill see how it goes.

MLAT is not going to work if you live in Australia and the location detail shows you in Portugal. You could use Google Earth to get your correct Latitude and Longitude to correct that in the system.

Is it correct to assume your piaware-config file contains the following text?

Should PiAware enable multilateration where possible?

You may need to disable this if multilateration overloads your receiver.

allow-mlat yes
mlat-results yes

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