FlightAware Discussions

Dump1090...not dumping any data

hi all. long time feeder. wanted to get some advice here before re-imaging from scratch since the pi is in a pita location in the building.

it was humming along fine for literally years until it stopped the other day. there was a power outage over a week ago but a power cable reset was fine. the pi right now is still online and talking to fa servers but not seeing anything.

i didn’t check the web log before it went past the point of original failure but here’s some of what it was spitting out…

[2020-06-08 08:10 PDT] mlat-client(831): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-06-08 08:10 PDT] mlat-client(831): Reconnecting in 30.0 seconds
[2020-06-08 08:10 PDT] mlat-client(831): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2020-06-08 08:11 PDT] 3862299 msgs recv’d from dump1090-fa (0 in last 5m); 3862023 msgs sent to FlightAware

i saw this after a hard reset : [2020-06-08 09:17 PDT] Failed to update feeder ID file at /var/cache/piaware/feeder_id: no space left on device ----- and tried emptying some cache

now it’s just stuck showing : [2020-06-09 09:25 PDT] attempting to start dump1090…
[2020-06-09 09:25 PDT] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2020-06-09 09:25 PDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s

any femputers out there know what do? thanks.

please post output of the command
sudo systemctl status dump1090-fa

check if file dump1090-fa exist in /etc/default

thanks for the response! here’s the result…something failed…

root@piaware:/home/pi# systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-06-09 18:12:41 UTC; 8s ago
Docs: https://flightaware.com/adsb/piaware/
Process: 15129 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json %t/dump1090-fa --quiet (code=exited, status=1/FAILURE)
Main PID: 15129 (code=exited, status=1/FAILURE)

Me Too!

pi@PIAWARE:/etc/default $ 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: activating (auto-restart) (Result: exit-code) since Wed 2020-06-10 22:06:59 PDT; 24s ago
Docs: https://flightaware.com/adsb/piaware/
Process: 23328 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa --quiet (code=exited, status=1/FAILURE)
Main PID: 23328 (code=exited, status=1/FAILURE)

/etc/default/dump1090-fa exists and its contents is (note that I had to omit the comments from this file as the HASH characters confuses this comment editor):

ENABLED=yes
RECEIVER_OPTIONS="–device-index 0 --gain -10 --ppm 0"
DECODER_OPTIONS="–max-range 360 --fix"
NET_OPTIONS="–net --net-heartbeat 60 --net-ro-size 1300 --net-ro-interval 0.2 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005"
JSON_OPTIONS="–json-location-accuracy 1"

Reading Fill’s post, it dawned on me that he might also be using one of the original NooElec NESDR USB Sticks (RTL2832 + R820T2).

I bought mine in 2015. Fill, do you have the same dongle?

Is it possible that a dump1090 update broke compatibility with this?

Thanks,

David

come to think of it, i have the dongle but it’s not the first generation one, it’s the second generation orange one with the amp built into it.

Total shot in the dark here, but takes 5 seconds to test:

I’ve had this happen before and it ended up being a failed sdcard. Everything appeared normal and could read from the sdcard without issue, but nothing could be written to it.

Get to cmdline via SSH or however you normally do:

touch test.txt
ls -la

If the file test.txt shows in the listing, ‘rm test.txt’ and wait for someone smart to come along with a better idea.

Yes, I can create files:

pi@PIAWARE:~ touch test.txt pi@PIAWARE:~ ls -la test.txt
-rw-r–r-- 1 pi pi 0 Jun 10 23:31 test.txt

and I have lots of free space:

pi@PIAWARE:~ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 15070120 4867196 9541640 34% /
devtmpfs 469540 0 469540 0% /dev
tmpfs 474148 0 474148 0% /dev/shm
tmpfs 474148 43540 430608 10% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 474148 0 474148 0% /sys/fs/cgroup
/dev/mmcblk0p1 258095 53463 204632 21% /boot
tmpfs 94828 0 94828 0% /run/user/109
tmpfs 94828 0 94828 0% /run/user/1000

I started my feeding in 2015 with a Raspberry Pi 2. In 2018 I upgraded to a Raspberry Pi 3 B+, but kept the same SDR USB dongle. I didn’t know I could preserve my station GUID so I unfortunately lost my 3 years of feeding history :frowning_face:

This February, i.e. 4 months ago, I did a clean install due to problems problems getting Remote Desktop to work again, and this time I preserved my station GUID.

It’s been working mostly fine since then, with an occasional hiccup/wedge that a reboot would always fix.

Until now…

David

Looking at the PiAware logs in /var/log, these are the last non-zero dump1090 messages received:

Jun 9 21:24:59 PIAWARE piaware[503]: mlat-client(5304): Receiver status: connected
Jun 9 21:24:59 PIAWARE piaware[503]: mlat-client(5304): Server status: not synchronized with any nearby receivers
Jun 9 21:24:59 PIAWARE piaware[503]: mlat-client(5304): Receiver: 1.5 msg/s received 0.8 msg/s processed (53%)
Jun 9 21:24:59 PIAWARE piaware[503]: mlat-client(5304): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
Jun 9 21:24:59 PIAWARE piaware[503]: mlat-client(5304): Aircraft: 0 of 0 Mode S, 1 of 1 ADS-B used
Jun 9 21:29:07 PIAWARE piaware[503]: 1786774 msgs recv’d from dump1090-fa (12 in last 5m); 1782379 msgs sent to FlightAware
Jun 9 21:34:07 PIAWARE piaware[503]: 1786821 msgs recv’d from dump1090-fa (47 in last 5m); 1782426 msgs sent to FlightAware
Jun 9 21:39:07 PIAWARE piaware[503]: 1786857 msgs recv’d from dump1090-fa (36 in last 5m); 1782462 msgs sent to FlightAware
Jun 9 21:40:00 PIAWARE piaware[503]: mlat-client(5304): Receiver status: connected
Jun 9 21:40:00 PIAWARE piaware[503]: mlat-client(5304): Server status: synchronized with 8 nearby receivers
Jun 9 21:40:00 PIAWARE piaware[503]: mlat-client(5304): Receiver: 1.5 msg/s received 0.9 msg/s processed (65%)
Jun 9 21:40:00 PIAWARE piaware[503]: mlat-client(5304): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
Jun 9 21:40:00 PIAWARE piaware[503]: mlat-client(5304): Aircraft: 2 of 2 Mode S, 0 of 0 ADS-B used
Jun 9 21:40:00 PIAWARE piaware[503]: mlat-client(5304): Out-of-order timestamps: 2
Jun 9 21:44:07 PIAWARE piaware[503]: 1786865 msgs recv’d from dump1090-fa (8 in last 5m); 1782470 msgs sent to FlightAware
Jun 9 21:49:07 PIAWARE piaware[503]: 1786865 msgs recv’d from dump1090-fa (0 in last 5m); 1782470 msgs sent to FlightAware
Jun 9 21:54:07 PIAWARE piaware[503]: 1786865 msgs recv’d from dump1090-fa (0 in last 5m); 1782470 msgs sent to FlightAware

then about an hour later PiAware tries to restart everything but dump1090 doesn’t come up:

Jun 9 22:43:37 PIAWARE piaware[503]: no new messages received in 3783 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…
Jun 9 22:43:37 PIAWARE piaware[503]: faup1090 exited with SIG SIGHUP
Jun 9 22:43:37 PIAWARE piaware[503]: attempting to restart dump1090…
Jun 9 22:43:37 PIAWARE piaware[503]: attempting to restart dump1090-fa using ‘systemctl --no-block try-restart dump1090-fa.service < /dev/null’…
Jun 9 22:43:37 PIAWARE piaware[503]: dump1090 restart appears to have been successful
Jun 9 22:43:47 PIAWARE piaware[503]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
Jun 9 22:43:47 PIAWARE piaware[503]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 47.494 --lon -122.464
Jun 9 22:43:47 PIAWARE piaware[503]: Started faup1090 (pid 27459) to connect to dump1090-fa
Jun 9 22:44:07 PIAWARE piaware[503]: 1786865 msgs recv’d from dump1090-fa (0 in last 5m); 1782470 msgs sent to FlightAware
Jun 9 22:45:07 PIAWARE piaware[503]: mlat-client(5304): Lost connection to localhost:30005
Jun 9 22:45:07 PIAWARE piaware[503]: mlat-client(5304): Reconnecting in 30.0 seconds
Jun 9 22:45:07 PIAWARE piaware[503]: mlat-client(5304): Beast-format results connection with ::1:30104: connection lost
Jun 9 22:45:07 PIAWARE piaware[503]: lost connection to dump1090-fa via faup1090
Jun 9 22:45:07 PIAWARE piaware[503]: faup1090 exited normally
Jun 9 22:45:07 PIAWARE piaware[503]: reconnecting to dump1090-fa
Jun 9 22:45:09 PIAWARE piaware[503]: no ADS-B data program seen listening on port 30005 for 2 seconds, next check in 60s
Jun 9 22:45:37 PIAWARE piaware[503]: mlat-client(5304): Connection to localhost:30005 lost: [Errno 111] Connection refused
Jun 9 22:45:38 PIAWARE piaware[503]: mlat-client(5304): Reconnecting in 0.5 seconds
Jun 9 22:45:38 PIAWARE piaware[503]: mlat-client(5304): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused

Hmmm. I’m at the end of time to investigate today.

David

Is the stick still working?

What give the command sudo lsusb?

Should be something like this:

Bus 001 Device 004: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
1 Like

What’s the output of sudo journalctl -u dump1090-fa? This is the logging that will show why dump1090-fa is failing to start.

1 Like

@obj :
Jun 11 06:24:02 piaware systemd[1]: dump1090-fa.service: main process exited, code=exited, status=1/FAILURE
Jun 11 06:24:02 piaware systemd[1]: Unit dump1090-fa.service entered failed state.
Jun 11 06:24:32 piaware systemd[1]: dump1090-fa.service holdoff time over, scheduling restart.
Jun 11 06:24:32 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Jun 11 06:24:32 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Jun 11 06:24:33 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 11 06:24:33 piaware dump1090-fa[16807]: Thu Jun 11 06:24:33 2020 UTC dump1090-fa 3.8.1~bpo8+1 starting up.
Jun 11 06:24:33 piaware dump1090-fa[16807]: rtlsdr: no supported devices found.
Jun 11 06:24:33 piaware systemd[1]: dump1090-fa.service: main process exited, code=exited, status=1/FAILURE
Jun 11 06:24:33 piaware systemd[1]: Unit dump1090-fa.service entered failed state.

@foxhunter :

Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here is the problem. The USB bus cannot see the dongle (the lsusb output corroborates that). Probably it is a hardware failure.

@obj : i swapped in an old generic R820T2 (same model # marking as the flightaware usb stick i’m using but no amp built in) usb i had laying around and this is the new output

Jun 11 16:17:06 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Jun 11 16:17:07 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 11 16:17:07 piaware dump1090-fa[474]: Thu Jun 11 16:17:07 2020 UTC dump1090-fa 3.8.1~bpo8+1 starting up.
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN stratux:978)
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware systemd[1]: dump1090-fa.service: main process exited, code=exited, status=1/FAILURE
Jun 11 16:17:07 piaware systemd[1]: Unit dump1090-fa.service entered failed state.
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_read_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_write_reg failed with -1
Jun 11 16:17:07 piaware dump1090-fa[474]: No supported tuner found
Jun 11 16:17:07 piaware dump1090-fa[474]: rtlsdr_demod_write_reg failed with -1

*edit - some more after hitting enter a few times :

Jun 11 17:14:21 piaware dump1090-fa[792]: rtlsdr_write_reg failed with -4
Jun 11 17:14:21 piaware dump1090-fa[792]: Failed to submit transfer 0!
Jun 11 17:14:21 piaware dump1090-fa[792]: rtlsdr: rtlsdr_read_async returned unexpectedly, probably lost the USB device, bailing out
Jun 11 17:14:21 piaware dump1090-fa[792]: Thu Jun 11 17:14:21 2020 UTC Waiting for receive thread termination
Jun 11 17:14:21 piaware dump1090-fa[792]: rtlsdr_write_reg failed with -4
Jun 11 17:14:21 piaware dump1090-fa[792]: Thu Jun 11 17:14:21 2020 UTC Abnormal exit.
Jun 11 17:14:52 piaware systemd[1]: dump1090-fa.service holdoff time over, scheduling restart.
Jun 11 17:14:52 piaware systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Jun 11 17:14:52 piaware systemd[1]: Starting dump1090 ADS-B receiver (FlightAware customization)…
Jun 11 17:14:52 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 11 17:14:52 piaware dump1090-fa[862]: Thu Jun 11 17:14:52 2020 UTC dump1090-fa 3.8.1~bpo8+1 starting up.
Jun 11 17:14:52 piaware dump1090-fa[862]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN stratux:978)
Jun 11 17:14:53 piaware dump1090-fa[862]: Found Rafael Micro R820T tuner
Jun 11 17:14:53 piaware dump1090-fa[862]: r82xx_write: i2c wr failed=-1 reg=10 len=1
Jun 11 17:14:53 piaware dump1090-fa[862]: r82xx_init: failed=-1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr: enabling tuner AGC
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: r82xx_write: i2c wr failed=-1 reg=05 len=1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: r82xx_write: i2c wr failed=-1 reg=17 len=1
Jun 11 17:14:53 piaware dump1090-fa[862]: r82xx_set_freq: failed=-1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_demod_read_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: rtlsdr_write_reg failed with -1
Jun 11 17:14:53 piaware dump1090-fa[862]: weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)

Do you have your Stick attached via the USB HUB documented as Device 004?

If yes, remove the Hub and connect it directly. dump1090 is obviously having trouble finding your device

@foxhunter : i don’t have any hub or anything, but i plugged in an older stick and this is the new output

Bus 001 Device 008: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

so i guess my old stick is dead if it couldn’t be seen, but the new one is seen but is not supported? pretty sure it was once upon a time.

That also looks like hardware problems.

possible options are:

  • you were unlucky and both dongles have failed
  • bad power
  • bad USB cabilng / bad USB hub, if you’re not directly connecting the dongles (I see you have an external hub on the bus, at least)
  • bad USB port or controller on the Pi

Try swapping things out one at a time.

3 Likes

the first lsusb command shows something like this:

Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB

USB hub in a keyboard?

it’s been so long i completely forgot. i’m using a powered usb extension because it’s a hard to reach area, so it might think the extension is a usb hub that may have failed? i tried a third usb dongle of the same type and dump1090 still doesn’t start. i didn’t have time at the office to try but tomorrow i will try a different usb port on the pi and try all three dongles again. if that doesn’t work i’m going to take the pi down and direct usb all 3 dongles to see if it’s the usb extension that’s the issue.

does flightaware not sell the packaged dongles any more?