Originally posted by wiedehopf
View Post
Announcement
Collapse
No announcement yet.
Is My DVB-T RTL SDR Dongle Healthy?
Collapse
This is a sticky topic.
X
X
-
Thanks wiedehopf. I follwed your instructions and now have the tar1090 working. How do I now connect or set this up to feed to fr24?
Leave a comment:
-
You probably installed dump978 or readsb or yet another application using the SDR.
pgrep -a readsb
pgrep -a dump
Or you can try
sudo rtl_test
Maybe it's a permission issue.
Personally i wouldn't recommend the pi24 image and look at adsb.im instead. Or just start with Raspbian: https://github.com/wiedehopf/adsb-wi...ADS-B-receiver
Leave a comment:
-
I'm having difficulty with my dongle too....
Not sure what the issue is..
Rpi5 8GB
pi@pi24-bookworm:~ $ sudo systemctl stop fr24feed
pi@pi24-bookworm:~ $ sudo systemctl stop dump1090
Failed to stop dump1090.service: Unit dump1090.service not loaded.
pi@pi24-bookworm:~ $ sudo systemctl stop dump1090-fa
Failed to stop dump1090-fa.service: Unit dump1090-fa.service not loaded.
pi@pi24-bookworm:~ $ sudo systemctl stop dump1090-mutability
pi@pi24-bookworm:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001
Using device 0: Generic RTL2832U OEM
usb_claim_interface error -6
Failed to open rtlsdr device #0.
pi@pi24-bookworm:~ $
pi@pi24-bookworm:~ $ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Earlier thread suggested the usb_claim interface error was due to not stopping the 1090 but as seen above I can't stop any mor ethan I have already?
Any ideas appreciated. Maybe it is a dud dongle but it worked well for a long time on a 3B which died.
Leave a comment:
-
And if you are posting here cause it's not feeding anymore.. see the other thread where they've broken anyone with auto-update enabled (AGAIN)
Leave a comment:
-
Originally posted by T-SBAQ3 View PostStick tested as expect, however I got the message: [R82XX] PLL not locked!
Any suggestions?
See below:
pi@raspberrypi:~ $ sudo systemctl stop dump1090-mutability
pi@raspberrypi:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001
Using device 0: Generic RTL2832U OEM
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.
Dont worry about "[R82XX] PLL not locked!". This is normal behaviour of a healthy Stick when tested.
Leave a comment:
-
Stick tested as expect, however I got the message: [R82XX] PLL not locked!
Any suggestions?
See below:
pi@raspberrypi:~ $ sudo systemctl stop dump1090-mutability
pi@raspberrypi:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001
Using device 0: Generic RTL2832U OEM
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.
Leave a comment:
-
Originally posted by yousaf465 View Post
I am running Homeassistant with MaxWinterstein's https://github.com/MaxWinterstein/ho...t-addons's ADB-S Multi Portal Feeder, which is based on Thom-x's docker-fr24feed-piaware-dump1090's
It was working fine until a few days ago. Now I am facing this.
Is it installed on Raspberry PI or on a PC?
I have no experience of such a system and cant help.
Your Dongle has shown OK in rtl_test.exe, but dump1090-fa is not able to detect it.
Dont know why, may be the dongle "pass-through" of your system is not functioning ok.
Better use a simpler system, a Debian based OS, with direct install of dump1090-fa, fr24feed etc. These simple systems have much less problems than the system you are using now.Last edited by abcd567; 2021-11-09, 19:31.
Leave a comment:
-
Originally posted by abcd567 View PostThat screenshot is not enough to diagnose. Please provide following info:
1. Which OS image you have installed on your Pi, Flightradar24's PI24 image, or Flightaware's Piaware SD Card image, or Raspbian OS image?
2. Which software you have installed on that image?
It was working fine until a few days ago. Now I am facing this.
Leave a comment:
-
That screenshot is not enough to diagnose. Please provide following info:
1. Which OS image you have installed on your Pi, Flightradar24's PI24 image, or Flightaware's Piaware SD Card image, or Raspbian OS image?
2. Which software you have installed on that image?
Leave a comment:
-
Originally posted by abcd567 View Post
This one seems ok.
if you dont want to see continous output "lost at least xx bytes", use following command :
rtl_test.exe -t
.
Screenshot 2021-11-09 095311.png
Leave a comment:
-
Originally posted by yousaf465 View Post
if you dont want to see continous output "lost at least xx bytes", use following command :
rtl_test.exe -t
.
Leave a comment:
-
Originally posted by abcd567 View PostFitipower tuner chip.jpg
yousaf465:
Dongle with wrong tuner chip "Fitipower FC0012".
The Tuner chip should be Realtek R820T2.
The two chips in dongle should be RTL2832U+R820T2, but your current one has RTL2832U+FC0012.
Purchase another dongle with correct chipset.
.
Screenshot 2021-11-08 204202.png
Leave a comment:
-
Fitipower tuner chip.jpg
yousaf465:
Dongle with wrong tuner chip "Fitipower FC0012".
The Tuner chip should be Realtek R820T2.
The two chips in dongle should be RTL2832U+R820T2, but your current one has RTL2832U+FC0012.
Purchase another dongle with correct chipset.
.
Last edited by abcd567; 2021-11-06, 18:15.
Leave a comment:
Leave a comment: