Announcement

Collapse
No announcement yet.

ADS-B receiver faulty?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ADS-B receiver faulty?

    Hi all,

    I’ve been feeding FR24 for a few years using the same ADS-B receiver without any major problems.
    A week ago, without any change on the setup, my feeder stopped sending data to FR24.
    I’ve tried reinstalling dump1090, Flightradar24 software, change configuration, rebooting the raspberry pi, ... with no success.
    At the moment I’m starting to believe that the receiver is faulty somehow. I’d like to have some opinions before buying a new one.

    Below I show the output of some commands.
    I truly appreciate any feedback


    pi@rpi2:~ ❯ fr24feed-status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2019-12-13 18:01:39.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EGVF43.
    [ ok ] FR24 Tracked AC: 0.
    [ ok ] Receiver: connected ( MSGS/ SYNC).
    [FAIL] FR24 MLAT: not running ... failed!


    pi@rpi2:~ ❯ rtl_test -t
    Found 1 device(s):
    0: Realtek, RTL2838UHIDIR, SN: 00000001

    Using device 0: Generic RTL2832U OEM
    No supported tuner found
    Enabled direct sampling mode, input 1
    Supported gain values (1): 0.0
    Sampling at 2048000 S/s.
    No E4000 tuner found, aborting.


    pi@rpi2:~ ❯ less /etc/fr24feed.ini
    receiver="beast-tcp"
    fr24key="013fdc4de100dedb"
    host="127.0.0.1:30005"
    bs="yes"
    raw="yes"
    logmode="2"
    logpath="/var/log/fr24feed"
    mlat="yes"
    mlat-without-gps="yes"


    pi@rpi2:~ ❯ tail -n30 /var/log/fr24feed/fr24feed.log
    2019-12-13 19:48:47 | [reader][i]Connection terminated
    2019-12-13 19:48:52 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
    2019-12-13 19:48:52 | [reader][i]Connected to the receiver, configuring
    2019-12-13 19:48:52 | [reader][i]Configured, processing messages
    2019-12-13 19:49:12 | [feed][n]ping 204
    2019-12-13 19:49:13 | [feed][n]syncing stream result: 1
    2019-12-13 19:49:42 | [feed][n]ping 205
    2019-12-13 19:49:43 | [feed][n]syncing stream result: 1
    2019-12-13 19:50:12 | [feed][n]ping 206
    2019-12-13 19:50:13 | [feed][n]syncing stream result: 1
    2019-12-13 19:50:42 | [feed][n]ping 207
    2019-12-13 19:50:43 | [feed][n]syncing stream result: 1
    2019-12-13 19:51:12 | [feed][n]ping 208
    2019-12-13 19:51:13 | [feed][n]syncing stream result: 1
    2019-12-13 19:51:42 | [feed][n]ping 209
    2019-12-13 19:51:43 | [feed][n]syncing stream result: 1
    2019-12-13 19:52:12 | [feed][n]ping 210
    2019-12-13 19:52:13 | [feed][n]syncing stream result: 1
    2019-12-13 19:52:42 | [feed][n]ping 211
    2019-12-13 19:52:43 | [feed][n]syncing stream result: 1
    2019-12-13 19:53:12 | [feed][n]ping 212
    2019-12-13 19:53:13 | [feed][n]syncing stream result: 1
    2019-12-13 19:53:42 | [feed][n]ping 213
    2019-12-13 19:53:43 | [feed][n]syncing stream result: 1
    2019-12-13 19:54:12 | [feed][n]ping 214
    2019-12-13 19:54:13 | [feed][n]syncing stream result: 1
    2019-12-13 19:54:42 | [feed][n]ping 215
    2019-12-13 19:54:43 | [feed][n]syncing stream result: 1
    2019-12-13 19:55:12 | [feed][n]ping 216
    2019-12-13 19:55:13 | [feed][n]syncing stream result: 1







  • #2
    No supported tuner found

    The tuner has gone awol. So it can't be tuned to the frequency required.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      Yes I noticed that too.
      Does this mean the only solution is getting a new receiver? I’m happy to get a new one, just want to check if it’s not something software related.

      Thanks for the quick reply!

      Comment


      • #4
        Try these simple things before you buy another receiver:

        (1) If you have connected receiver to Pi using a USB cable, remove it and plug the dongle directly into Pi and reboot Pi.

        (2) If the dongle is directly plugged into Pi, unplug then replug it and reboot Pi.

        You may try another USB port of Pi. This will solve the problem in case the current usb port has some issue.
        Last edited by abcd567; 2019-12-13, 23:52.

        Comment


        • #5
          I’ve tried that already. Receiver is directly plugged into Pi.
          Did it again and used different USB ports, no luck.
          I guess the receiver tuner died, it lasted 5 years which is not bad, it’s not an expensive receiver.
          I’ll get a new one and will let you know about the result.
          Many thanks for your feedback on this issue

          Comment

          Working...
          X