Announcement

Collapse
No announcement yet.

New setup works, but no planes found

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

  • New setup works, but no planes found

    Hi,
    I prepared my RaspberryPi as documented and attached an old DVB-T antenna just to try out if it works. I can see that my device successfully connected to fr24 and I can see my stats in my fr24 online account. The Raspberry should have a sufficient power supply and the antenna is attached to a USB hub with seperate power supply.

    But the antenna doesn't find any planes (I'm living 100km south of FRA, there is quite some traffic). I guess it is because of the DVB-T antenna but before ordering a new one I'd like to know if there are some settings which could help me out aswell. I already checked thread "FR24feed uploader - Additional Info" but to be honest, I'm not really understanding everything there

    I also tried "sudo systemctl stop/start fr24feed".

    All I know about the DVB-T antenna is "CSL DVB-T Stick Realtek Chip"and it's uhm...well.. black, if that info helps

    My fr24feed software version:
    Code:
    fr24feed:
    Installed: 1.0.25-1
    Candidate: 1.0.25-1
    Version table:
    *** 1.0.25-1 500
    500 http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable armhf Packages
    100 /var/lib/dpkg/status
    My config:
    Code:
     [TABLE]
    [TR]
    [TD]FR24 Link:[/TD]
     			[TD]Connected via UDP[/TD]
     		[/TR]
    [TR]
    [TD]FR24 Radar Code:[/TD]
     			[TD]T-ETIE112[/TD]
     		[/TR]
    [TR]
    [TD]Local IP(s):[/TD]
     			[TD]XXX.XXX.XXX.XX[/TD]
     		[/TR]
    [TR]
    [TD]Aircraft Tracked:
    [I](ModeS & ADS-B)[/I][/TD]
     			[TD]0[/TD]
     		[/TR]
    [TR]
    [TD]Aircraft Uploaded:[/TD]
     			[TD]0[/TD]
     		[/TR]
    [TR]
    [TD]Receiver:[/TD]
     			[TD]dvbt, Connected[/TD]
     		[/TR]
    [TR]
    [TD]MLAT running:[/TD]
     			[TD]NO[/TD]
     		[/TR]
    [/TABLE]


    I may add that I have no chance to change the settings in the WebUI: the changes are not getting saved here and stay the same.

    This is the protocol I get:
    Code:
    $ sudo systemctl stop fr24feed
     $ sudo fr24feed
    2020-04-30 22:25:43 | ______ _ _ _ _ _ _____ ___
    2020-04-30 22:25:43 | | ___|| |(_) | | | | | | / __ \ / |
    2020-04-30 22:25:43 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
    2020-04-30 22:25:43 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
    2020-04-30 22:25:43 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
    2020-04-30 22:25:43 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
    2020-04-30 22:25:43 | __/ |
    2020-04-30 22:25:43 | |___/
    2020-04-30 22:25:43 | [main][i]FR24 Feeder/Decoder
    2020-04-30 22:25:43 | [main][i]Version: 1.0.25-1/generic
    2020-04-30 22:25:43 | [main][i]Built on Mar 5 2020 14:41:55 (HEAD-138e2b2.git/Linux/static_armel)
    2020-04-30 22:25:43 | [main][i]Running on: pi24-raspbian10
    2020-04-30 22:25:43 | [main][i]Local IP(s): XXX.XXX.XXX.XX
    2020-04-30 22:25:43 | [main][i]Copyright 2012-2020 Flightradar24 AB
    2020-04-30 22:25:43 | [main][i]https://www.flightradar24.com
    2020-04-30 22:25:43 | [main][i]DNS mode: PING
    2020-04-30 22:25:44 | [main][i]Automatic updates are ENABLED
    2020-04-30 22:25:44 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
    2020-04-30 22:25:44 | info | [httpd]Server started, listening on 0.0.0.0:8754
    2020-04-30 22:25:45 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
    2020-04-30 22:25:45 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
    2020-04-30 22:25:46 | [main][i]Reader thread started
    2020-04-30 22:25:46 | [main][i]Socket server started
    2020-04-30 22:25:46 | [main][i]MLAT data feed started
    2020-04-30 22:25:46 | [master][i]Starting processing thread
    2020-04-30 22:25:46 | [reader][i]Initializing reader
    2020-04-30 22:25:46 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --raw --mlat)
    2020-04-30 22:25:46 | [mlat][i]Waiting for MLAT configuration
    2020-04-30 22:25:46 | [bs][i]Initializing server
    2020-04-30 22:25:46 | [bs][i]Starting server on 0.0.0.0:30003
    2020-04-30 22:25:46 | [reader][i]Connected to the receiver, configuring
    2020-04-30 22:25:46 | [reader][i]Configured, processing messages
    Thu Apr 30 22:25:46 2020 BST EB_SOURCE EB_VERSION starting up.
    Using sample converter: UC8, integer/table path
    Found 1 device(s):
    0: Realtek, DVB-T Dongle, SN: 00000991 (currently selected)
    Found Fitipower FC0013 tuner
    Using automatic gain control.
    2020-04-30 22:25:47 | [time][i]Synchronizing time via NTP
    Gain reported by device: 0.00 dB
    Allocating 15 zero-copy buffers
    2020-04-30 22:25:47 | [time][i]Time synchronized correctly, offset -0.001 seconds
    2020-04-30 22:25:47 | [main][i]Feed Network client started
    2020-04-30 22:25:47 | [main][i]RAW data server started
    2020-04-30 22:25:47 | [raw][i]Initializing server
    2020-04-30 22:25:47 | [raw][i]Starting server on 0.0.0.0:30002
    2020-04-30 22:25:47 | [feed][i]Downloading configuration
    2020-04-30 22:25:47 | [feed][d]fetching configuration
    2020-04-30 22:25:48 | [feed][i]configuring decoder
    2020-04-30 22:25:48 | [feed][c]Max range AIR: 350.0nm
    2020-04-30 22:25:48 | [feed][c]Max range GND: 100.0nm
    2020-04-30 22:25:48 | [feed][i]configuration changed
    2020-04-30 22:25:48 | [feed][i]defined 3 servers
    2020-04-30 22:25:48 | [feed][c]Timestamps: optional
    2020-04-30 22:25:48 | info | Stopping ReceiverACSender threads for feed
    2020-04-30 22:25:48 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: ETIE112, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
    2020-04-30 22:25:48 | info | [stats]Stats thread started
    2020-04-30 22:25:48 | info | Network thread connecting to 185.218.24.22:8099 for feed ETIE112
    2020-04-30 22:25:48 | [feed][n]YAY@XXX.XXX.XX.XX:8099/UDP
    2020-04-30 22:25:48 | [feed][n]connecting
    2020-04-30 22:25:48 | [feed][n]connected via UDP (fd 32)
    2020-04-30 22:25:48 | [feed][i]Feed connected
    2020-04-30 22:25:48 | [feed][n]working
    2020-04-30 22:26:18 | [feed][n]ping 1
    2020-04-30 22:26:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:26:48 | [feed][n]ping 2
    2020-04-30 22:26:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:27:18 | [feed][n]ping 3
    2020-04-30 22:27:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:27:48 | [feed][n]ping 4
    2020-04-30 22:27:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:28:18 | [feed][n]ping 5
    2020-04-30 22:28:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:28:48 | [feed][n]ping 6
    2020-04-30 22:28:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:29:18 | [feed][n]ping 7
    2020-04-30 22:29:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:29:48 | [feed][n]ping 8
    2020-04-30 22:29:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:30:18 | [feed][n]ping 9
    2020-04-30 22:30:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:30:48 | [feed][n]ping 10
    2020-04-30 22:30:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:31:18 | [feed][n]ping 11
    2020-04-30 22:31:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:31:48 | [feed][n]ping 12
    2020-04-30 22:31:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:32:18 | [feed][n]ping 13
    2020-04-30 22:32:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:32:48 | [feed][n]ping 14
    2020-04-30 22:32:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:33:18 | [feed][n]ping 15
    2020-04-30 22:33:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:33:48 | [feed][n]ping 16
    2020-04-30 22:33:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:34:18 | [feed][n]ping 17
    2020-04-30 22:34:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:34:48 | [feed][n]ping 18
    2020-04-30 22:34:49 | [feed][n]syncing stream result: 1
    sudo systemctl stop fr24feed
    2020-04-30 22:35:18 | [feed][n]ping 19
    2020-04-30 22:35:19 | [feed][n]syncing stream result: 1
    ^[
    2020-04-30 22:35:48 | [feed][n]ping 20
    2020-04-30 22:35:49 | info | [stats]sent 16 bytes
    2020-04-30 22:35:49 | [feed][n]syncing stream result: 1
    2020-04-30 22:36:09 | [reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting
    2020-04-30 22:36:09 | [reader][i]Connection terminated
    2020-04-30 22:36:09 | [main][i]Terminating child process 4392 with SIGTERM
    Thu Apr 30 22:36:09 2020 BST Caught SIGTERM, shutting down..
    
    Thu Apr 30 22:36:09 2020 BST Waiting for receive thread termination
    Thu Apr 30 22:36:10 2020 BST Normal exit.
    2020-04-30 22:36:15 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --raw --mlat)
    2020-04-30 22:36:15 | [reader][i]Connected to the receiver, configuring
    2020-04-30 22:36:15 | [reader][i]Configured, processing messages
    Thu Apr 30 22:36:15 2020 BST EB_SOURCE EB_VERSION starting up.
    Using sample converter: UC8, integer/table path
    Found 1 device(s):
    0: Realtek, DVB-T Dongle, SN: 00000991 (currently selected)
    Found Fitipower FC0013 tuner
    Using automatic gain control.
    Gain reported by device: 0.00 dB
    Allocating 15 zero-copy buffers
    2020-04-30 22:36:18 | [feed][n]ping 21
    2020-04-30 22:36:19 | [feed][n]syncing stream result: 1
    2020-04-30 22:36:49 | [feed][n]ping 22
    2020-04-30 22:36:50 | [feed][n]syncing stream result: 1
    ^C2020-04-30 22:37:00 | [main][i]Terminating on user request
    Thu Apr 30 22:37:00 2020 BST Caught SIGINT, shutting down..
    
    2020-04-30 22:37:00 | [main][i]Terminating worker threads
    Thu Apr 30 22:37:00 2020 BST Waiting for receive thread termination
    2020-04-30 22:37:00 | [bs][i]Server terminated!
    Thu Apr 30 22:37:01 2020 BST Normal exit.
    2020-04-30 22:37:01 | [reader][i]Connection terminated
    2020-04-30 22:37:01 | [main][i]Terminating child process 5344 with SIGTERM
    2020-04-30 22:37:02 | [raw][i]Server terminated!
    2020-04-30 22:37:02 | [reader][i]Terminating on request
    2020-04-30 22:37:06 | [master][i]Terminating on request
    2020-04-30 22:37:06 | [feed][x]Feeding thread terminated
    2020-04-30 22:37:06 | info | Stopping ReceiverACSender threads for feed ETIE112
    2020-04-30 22:37:06 | [feed][n]busy
    2020-04-30 22:37:06 | [feed][i]Feed disconnected
    2020-04-30 22:37:06 | [feed][n]disconnected
    2020-04-30 22:37:06 | warning | Exited network thread for feed ETIE112
    2020-04-30 22:37:06 | info | Joined network thread for feed ETIE112
    I hope it's just a wrong setting and the solution is a no-brainer for the experts here

    Thanks in advance!

  • #2
    Couple of things.

    That is the old version that doesn't allow saving

    Sudo apt-get update
    Sudo apt-get install fr24feed

    Secondly if you note the dvbt requirements/output messages section you would see your old stick is not the right type :/

    Found Fitipower FC0013 tuner
    From your output screen

    Supplemental to information found at https://www.flightradar24.com/build-your-own (spurred from user finding stick information not so forthcomming) If you do not chose to purchase a marketed 'ADSB stick' or USB TV Tuner via the suggested link there are specific requirements to be made aware of before purchasing generic sticks
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      I tried wiedehopfs analysis tool:

      Code:
      "$(wget -nv -O - https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/rtl_test.sh)"
      Result:
      Code:
      -----
      Lost samples in the first 2 seconds after starting the test are common and not a problem!
      Starting 30 second rtl_test, standby!
      -----
      Found 1 device(s):
      0: Realtek, DVB-T Dongle, SN: 00000991
      
      Using device 0: Dexatek DK DVB-T Dongle (Logilink VG0002A)
      Found Fitipower FC0013 tuner
      Supported gain values (23): -9.9 -7.3 -6.5 -6.3 -6.0 -5.8 -5.4 5.8 6.1 6.3 6.5 6 .7 6.8 7.0 7.1 17.9 18.1 18.2 18.4 18.6 18.8 19.1 19.7
      Sampling at 2400000 S/s.
      
      Info: This tool will continuously read from the device, and report if
      samples get lost. If you observe no further output, everything is fine.
      
      Reading samples in async mode...
      Allocating 15 zero-copy buffers
      lost at least 16 bytes
      Signal caught, exiting!
      
      User cancel, exiting...
      Samples per million lost (minimum): 0
      -------
      Test finished!
      More than 2 lost samples per million or other errors probably mean the receiver isn't working correctly.
      Try another power supply before condemning the receiver though!
      -------
      -------
      No undervoltage detected, looking fine!
      -> So I attached the antenna directly to the raspberry and repeated the test:

      Code:
      Lost samples in the first 2 seconds after starting the test are common and not a problem!
      Starting 30 second rtl_test, standby!
      -----
      Found 1 device(s):
      0: Realtek, DVB-T Dongle, SN: 00000991
      
      Using device 0: Dexatek DK DVB-T Dongle (Logilink VG0002A)
      Found Fitipower FC0013 tuner
      Supported gain values (23): -9.9 -7.3 -6.5 -6.3 -6.0 -5.8 -5.4 5.8 6.1 6.3 6.5 6.7 6.8 7.0 7.1 17.9 18.1 18.2 18.4 18.6 18.8 19.1 19.7
      Sampling at 2400000 S/s.
      
      Info: This tool will continuously read from the device, and report if
      samples get lost. If you observe no further output, everything is fine.
      
      Reading samples in async mode...
      Allocating 15 zero-copy buffers
      lost at least 152 bytes
      Signal caught, exiting!
      
      User cancel, exiting...
      Samples per million lost (minimum): 1
      -------
      Test finished!
      More than 2 lost samples per million or other errors probably mean the receiver isn't working correctly.
      Try another power supply before condemning the receiver though!

      Comment


      • #4
        Originally posted by Oblivian View Post
        [...]

        Secondly if you note the dvbt requirements/output messages section you would see your old stick is not the right type :/



        From your output screen

        https://forum.flightradar24.com/foru...e-requirements
        Ok, thanks. So I'll get a new stick

        Comment


        • #5
          Some sticks suited or even specifically made for ADS-B are listed here:

          https://github.com/wiedehopf/adsb-wi...-shopping-list

          Comment


          • #6
            Thanks Wiedehopf, I saw your list already. But sadly many of the links point to products which are not available anymore.

            Now I ordered this one:

            NESDR Mini (TV28T v2) USB RTL-SDR, DVB-T und ADS-B-Empfängerset

            Cheers,

            Comment

            Working...
            X