Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 23

Thread: Is My DVB-T RTL SDR Dongle Healthy?

  1. #11
    Passenger
    Join Date
    Apr 2018
    Posts
    14
    Quote Originally Posted by abcd567 View Post
    @Damianiw:

    Sorry for late reply. Have missed your post earlier.

    Following are possibilities
    (1) The Dongle is not properly plugged into Pi. Unplug and replug it, and reboot Pi.
    (2) If dongle is connected to Pi through a USB Cable, the cable is defective
    (3) AC to 5V DC Power adapter is not good.
    (4) Dongle is defective.
    Thanks for your help, after proving the dongle on Windows I came to the conclusion the pi either has two faulty usb sockets or couldnít provide enough power (original model b) I realised I have a powered usb hub for another project and tried it - problem resolved ! The hub is actually being powered by the second USB port on the pi!

    So maybe the later models of pi provide more power over usb - now to find the best placement and start playing with the software.

    Thanks also to the mod who helped explain and release my post


    Sent from my iPhone using Tapatalk

  2. #12
    Purser
    Join Date
    Nov 2016
    Posts
    155
    I've got a black DVB-T dongle that's never received any data since new - so I used abcd567's test method above - thanks for this. When plugged into the RPi 3B, the dongle LED lights up so its connected properly and powered up. But the test fails - no supported devices found.

    I've also tested a light blue dongle and that outputs the codes indicating its healthy so I know the install is correct.

    Is there anything else I should try before consigning the black dongle to its destruction and purchasing a Flightaware Dark Blue replacement ?

    Cheers

    ylis

  3. #13
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,049
    Quote Originally Posted by ylis View Post
    I've got a black DVB-T dongle that's never received any data since new - so I used abcd567's test method above - thanks for this. When plugged into the RPi 3B, the dongle LED lights up so its connected properly and powered up. But the test fails - no supported devices found.

    I've also tested a light blue dongle and that outputs the codes indicating its healthy so I know the install is correct.

    Is there anything else I should try before consigning the black dongle to its destruction and purchasing a Flightaware Dark Blue replacement ?

    Cheers
    Linux?

    lsusb

    Possibly a real tv tuner and not a realtek device which is needed
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  4. #14
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,852
    ylis:

    1) Please post the full output of the test for black dongle.

    2) As suggested by Oblivian, please give command lsusb, and post its full output.

  5. #15
    Purser
    Join Date
    Nov 2016
    Posts
    155
    Oblivian: thanks - tried this

    abcd567:

    Black dongle - that has never worked:

    pi@raspberrypi:~ $ rtl_test -t
    No supported devices found.

    pi@raspberrypi:~ $ lsusb
    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
    pi@raspberrypi:~ $
    Blue Dongle - working:

    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
    Sampling at 2048000 S/s.
    No E4000 tuner found, aborting.

    pi@raspberrypi:~ $ lsusb
    Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 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.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    pi@raspberrypi:~ $
    IMG_0541.jpg

    The black one could be just a dud - a case of lights on but no-one's home. I'm happy to simply purchase another dongle if there's no obvious quick fix...

    Thanks for your time

  6. #16
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,852
    ylis:

    The results of rtl_test -t and lsusb both show that the black one is just a dud.

    .

  7. #17

    Join Date
    Jan 2019
    Location
    London
    Posts
    0
    pi@raspberrypi:~ $ lsusb
    Bus 001 Device 005: ID 07ca:a815 AVerMedia Technologies, Inc. AVerTV DVB-T Volar X (A815)
    Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
    Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. SMC9512/9514 USB Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    pi@raspberrypi:~ $ sudo service fr24feed status
    ● fr24feed.service - Flightradar24 Decoder & Feeder
    Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
    Active: active (running) since Tue 2019-01-29 21:22:46 UTC; 19min ago
    Process: 248 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=0/SUCCESS)
    Process: 241 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
    Process: 219 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
    Main PID: 289 (fr24feed)
    CGroup: /system.slice/fr24feed.service
    └─289 /usr/bin/fr24feed

    Jan 29 21:22:42 raspberrypi systemd[1]: Starting Flightradar24 Decoder & Feeder...
    Jan 29 21:22:46 raspberrypi systemd[1]: Started Flightradar24 Decoder & Feeder.

    pi@raspberrypi:~ $ rtl_test -t
    No supported devices found.

    pi@raspberrypi:~ $ sudo fr24feed-status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2019-01-29 21:31:32.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EGWU113.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!

    pi@raspberrypi:~ $ cat /var/log/fr24feed/fr24feed.log
    2019-01-29 21:22:47 | ______ _ _ _ _ _ _____ ___
    2019-01-29 21:22:47 | | ___|| |(_) | | | | | | / __ \ / |
    2019-01-29 21:22:47 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
    2019-01-29 21:22:47 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
    2019-01-29 21:22:47 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
    2019-01-29 21:22:47 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
    2019-01-29 21:22:47 | __/ |
    2019-01-29 21:22:47 | |___/
    2019-01-29 21:22:47 | [main][i]FR24 Feeder/Decoder
    2019-01-29 21:22:47 | [main][i]Version: 1.0.23-8/generic
    2019-01-29 21:22:47 | [main][i]Built on Oct 11 2018 18:27:28 (HEAD-3c696a7.git/Linux/static_armel)
    2019-01-29 21:22:47 | [main][i]Running on: pi24-raspbian9
    2019-01-29 21:22:47 | [main][i]Local IP(s):
    2019-01-29 21:22:47 | [main][i]Copyright 2012-2018 Flightradar24 AB
    2019-01-29 21:22:47 | [main][i]flighttrader website url
    2019-01-29 21:22:47 | [main][i]DNS mode: PING
    2019-01-29 21:22:47 | [main][i]Automatic updates are ENABLED
    2019-01-29 21:22:48 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
    2019-01-29 21:22:48 | [main][i]Reader thread started
    2019-01-29 21:22:48 | [main][i]Socket server started
    2019-01-29 21:22:48 | [time][i]Synchronizing time via NTP
    2019-01-29 21:22:48 | [bs][i]Initializing server
    2019-01-29 21:22:48 | [bs][i]Starting server on 0.0.0.0:30003
    2019-01-29 21:22:48 | [master][i]Starting processing thread
    2019-01-29 21:22:48 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2019-01-29 21:22:48 | [reader][i]Initializing reader
    2019-01-29 21:22:48 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:22:48 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:22:48 | [reader][i]Configured, processing messages
    2019-01-29 21:22:50 | [reader][i]Connection terminated
    2019-01-29 21:22:50 | [main][i]Terminating child process 320 with SIGTERM
    2019-01-29 21:22:52 | [time][e]Failed to synchronize time
    2019-01-29 21:22:52 | [main][w]Failed to synchronize time, waiting 5 seconds
    2019-01-29 21:22:55 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:22:55 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:22:55 | [reader][i]Configured, processing messages
    2019-01-29 21:22:55 | [reader][i]Connection terminated
    2019-01-29 21:22:55 | [main][i]Terminating child process 405 with SIGTERM
    2019-01-29 21:22:57 | [time][i]Synchronizing time via NTP
    2019-01-29 21:23:01 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:23:01 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:23:01 | [reader][i]Configured, processing messages
    2019-01-29 21:23:01 | [reader][i]Connection terminated
    2019-01-29 21:23:01 | [main][i]Terminating child process 513 with SIGTERM
    2019-01-29 21:23:03 | [time][i]Time synchronized correctly, offset +12.0406 seconds
    2019-01-29 21:23:03 | [main][i]Feed Network client started
    2019-01-29 21:23:03 | [main][i]RAW data server started
    2019-01-29 21:23:03 | [raw][i]Initializing server
    2019-01-29 21:23:03 | [raw][i]Starting server on 0.0.0.0:30002
    2019-01-29 21:23:03 | [feed][i]Downloading configuration
    2019-01-29 21:23:04 | [feed][d]fetching configuration
    2019-01-29 21:23:04 | [feed][i]configuring decoder
    2019-01-29 21:23:04 | [feed][c]Max range AIR: 350.0nm
    2019-01-29 21:23:04 | [feed][c]Max range GND: 100.0nm
    2019-01-29 21:23:04 | [feed][i]configuration changed
    2019-01-29 21:23:04 | [feed][i]defined 3 servers
    2019-01-29 21:23:04 | [feed][c]Timestamps: optional
    2019-01-29 21:23:04 | [stats][i]Stats thread started
    2019-01-29 21:23:04 | [feed][n]EGWUnnn@185.218.24.22:8099/UDP
    2019-01-29 21:23:04 | [feed][n]connecting
    2019-01-29 21:23:04 | [feed][n]connected via UDP (fd 14)
    2019-01-29 21:23:04 | [feed][i]Feed connected
    2019-01-29 21:23:04 | [feed][n]working
    2019-01-29 21:23:04 | info | Stopping ReceiverACSender threads for feed
    2019-01-29 21:23:04 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: EGWUnnn, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
    2019-01-29 21:23:04 | info | Network thread connecting to 185.218.24.22:8099 for feed EGWUnnn
    2019-01-29 21:23:07 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:23:07 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:23:07 | [reader][i]Configured, processing messages
    2019-01-29 21:23:07 | [reader][i]Connection terminated
    2019-01-29 21:23:07 | [main][i]Terminating child process 540 with SIGTERM
    2019-01-29 21:23:25 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:23:25 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:23:25 | [reader][i]Configured, processing messages
    2019-01-29 21:23:25 | [reader][i]Connection terminated
    2019-01-29 21:23:25 | [main][i]Terminating child process 556 with SIGTERM
    2019-01-29 21:23:26 | [time][w]Time jumped forward by 12.41s, resynchronizing
    2019-01-29 21:23:26 | [time][i]Synchronizing time via NTP
    2019-01-29 21:23:31 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:23:31 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:23:31 | [reader][i]Configured, processing messages
    2019-01-29 21:23:31 | [reader][i]Connection terminated
    2019-01-29 21:23:31 | [main][i]Terminating child process 587 with SIGTERM
    2019-01-29 21:23:34 | [time][i]Time synchronized correctly, offset -0.0004 seconds
    2019-01-29 21:23:36 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:23:36 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:23:36 | [reader][i]Configured, processing messages
    2019-01-29 21:23:37 | [reader][i]Connection terminated
    2019-01-29 21:23:37 | [main][i]Terminating child process 598 with SIGTERM
    2019-01-29 21:23:42 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
    2019-01-29 21:23:42 | [reader][i]Connected to the receiver, configuring
    2019-01-29 21:23:42 | [reader][i]Configured, processing messages
    2019-01-29 21:23:42 | [reader][i]Connection terminated
    2019-01-29 21:23:42 | [main][i]Terminating child process 600 with SIGTERM
    2019-01-29 21:23:45 | [feed][n]ping 1
    2019-01-29 21:23:46 | [feed][n]syncing stream result: 1
    :
    :

    /etc/fr24feed.ini
    receiver="dvbt"
    fr24key="myKey"
    path="/usr/lib/fr24/dump1090"
    bs="yes"
    raw="yes"
    logmode="2"
    windowmode="0"
    logpath="/var/log/fr24feed"
    mpx="no"
    mlat="no"
    mlat-without-gps="no"
    use-http=yes
    http-timeout=10

    Does this mean my DVB-T adaptor is not compatible? Shall I give it up?

  8. #18
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,049
    Quote Originally Posted by Icosphere View Post
    pi@raspberrypi:~ $ lsusb
    Bus 001 Device 005: ID 07ca:a815 AVerMedia Technologies, Inc. AVerTV DVB-T Volar X (A815)
    Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
    Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. SMC9512/9514 USB Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


    pi@raspberrypi:~ $ rtl_test -t
    No supported devices found.


    Does this mean my DVB-T adaptor is not compatible? Shall I give it up?
    I've highlighted the key factors.

    That is not a realtek based USB stick which is required. So no, not compatible.

    https://forum.flightradar24.com/thre...e-Requirements
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  9. #19
    Passenger
    Join Date
    Apr 2018
    Posts
    14
    Hi my raspberry pi model b setup has been working well for year but just stopped, Iíve tried rebuilding, replacing pi for a pi zero w and an official 5.1v 2.5a psu and am wondering if my dvbt dongle has failed, the light on the dongle seems to go out or flitter like thereís a loose connection and it gets warm whilst making a high pitch noise.

    Iíll try troubleshooting over the weekend any recommended tips or ways to troubleshoot please.

    Iím convinced the original PI (model b) had an issue as running lsusb shows the dongle but after a time doesnít.

    Using the new pi zero w I have followed the steps above on it and get what looks like a good test:

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

    Using device 0: Generic RTL2832U OEM
    Found Rafael Micro R820T tuner
    [R82XX] PLL not locked!
    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.
    pi@raspberrypi:~ $

    The device keeps showing on lsusb

    pi@raspberrypi:~ $ lsusb
    Bus 001 Device 002: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    pi@raspberrypi:~ $



    Sent from my iPhone using Tapatalk

  10. #20
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,852
    Try another 5v power supply adaptor for Pi B.

    As you already have Pi Zero, use Pi zero's 5v adapter with Pi B for trial.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •