Announcement

Collapse
No announcement yet.

Help me get my FR24 running

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

  • Help me get my FR24 running

    Hey guys,

    a while back I had my FR24 running fine and eventuallty it stopped working. I stopped using it...

    I want to start using it again, but not getting any luck. I have a Nooelec DVB-T that is currently working (can listen to stuff on SDRSharp).

    When I start up FR24, it's not working, and I'm not sure if it's connectivity or something else... Looking for any help. I'm on Windows 10 running comcast to linksys velop

    Code:
    [main][i]FR24 Feeder/Decoder
    [main][i]Version: 1.0.18-9/generic
    [main][i]Built on Apr 21 2017 14:51:08 (???/Windows/i386)
    [main][i]Copyright 2012-2017 Flightradar24 AB
    [main][i]http://flightradar24.com
    [main][i]Reader thread started
    [master][i]Starting processing thread
    [reader][i]Initializing reader
    [main][i]Socket server started
    [bs][i]Initializing server
    [httpd][i]Server started, listening on 0.0.0.0:8754
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe  --raw)
    [time][i]Synchronizing time via NTP
    [bs][i]Starting server on 0.0.0.0:30003
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [time][i]Time synchronized correctly, offset +0.0711 seconds
    [main][i]Feed Network client started
    [main][i]RAW data server started
    [feed][i]Downloading configuration
    [raw][i]Initializing server
    [raw][i]Starting server on 0.0.0.0:30002
    [feed][c]Interval: 5s
    [feed][c]Latitude: 26.6832
    [feed][c]Longitude: -80.0955
    [feed][c]GND: YES
    [feed][c]NonADSB: YES
    [feed][c]Timestamps: optional
    [feed][c]Max range AIR: 350.0nm
    [feed][c]Max range GND: 100.0nm
    [feed][i]defined 5 servers
    [stats][i]Stats thread started
    [feed][n]KPBI9@83.140.21.87:8099/UDP
    [feed][n]connecting
    [feed][n]connected via UDP (fd 948)
    [feed][n]working
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe  --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    Running mr-dump1090

    Code:
    Found 2 device(s):
    0: ■, ┤■, SN:  (currently selected)
    1: Realtek, RTL2838UHIDIR, SN: 00000001
    usb_open error -12
    Error opening the RTLSDR device: No error
    config screen:

    Code:
    Flightradar24 Feeder/Decoder
    
    Windows/generic/i386/1.0.18-9
    
    Updated: 14:23:42 GMT-0400 (Eastern Daylight Time)
    
    FR24 Link:	Connected via UDP
    FR24 Radar Code:	T-KPBI9
    Aircraft Tracked (ModeS & ADS-B):	0
    Aircraft Uploaded:	N/A
    Receiver:	dvbt, Connected
    MLAT running:	N/A
    Last edited by razorseal; 2017-09-17, 18:25.

  • #2
    Try the additional command as stated here

    Note the issue with usb selection.

    https://forum.flightradar24.com/showthread.php?p=95686
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      Originally posted by Oblivian View Post
      Try the additional command as stated here

      Note the issue with usb selection.

      https://forum.flightradar24.com/showthread.php?p=95686
      Oblivian,

      Got it, slightly diff than what that said (it's not interface-index, but device-index) setting --device-index 1 did the trick. Much thanks!

      Comment


      • #4
        Seems theres some variation depending on Dump1090 version

        Was that the latest raspian OS? Finding some other quirks with it too. It appears either the sticks, or something on the later PIs are being detected first and associated as the wrong device to pick
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #5
          Originally posted by Oblivian View Post
          Was that the latest raspian OS? Finding some other quirks with it too. It appears either the sticks, or something on the later PIs are being detected first and associated as the wrong device to pick
          Hi Oblivian!
          You are right. Raspbian STRETCH is pain in neck

          Just to test, I installed Raspbian STRETCH, and found following problems:

          (1) dump1090-mutability fails to open DVB-T.
          Reason missing rtl-sdr.rules.


          Workaround:
          Code:
          sudo wget -O  /etc/udev/rules.d/rtl-sdr.rules "https://raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules"
          
          sudo reboot

          (2) FlightRadar24's fr24feed fails to install by bash script.
          Reason missing package "dirmngr".


          Workaround:
          Code:
          sudo apt-get update
          sudo apt-get install dirmngr
          
          sudo bash -c "$(wget -O - http://repo.feed.flightradar24.com/install_fr24_rpi.sh)"
          #Enter details when prompted.

          (3) RadarBox24's rbfeeder fails to install by bash script
          Code:
          sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
          .........
          W: GPG error: http://apt.rb24.com jessie Release: The following signatures were invalid: A7E7D5E3786CA2212A3A5F4769D62C99357DF51A
          W: The repository 'http://apt.rb24.com jessie Release' is not signed.
          .........
          WARNING: The following packages cannot be authenticated!
            rbfeeder
          .....
          Failed to start rbfeeder.service: Unit rbfeeder.service not found.

          Workaround:
          Code:
          sudo apt-get update
          sudo apt-get install rbfeeder
          Ignore following warning during install and say y
          Code:
          WARNING: The following packages cannot be authenticated!
            rbfeeder
          Install these packages without verification? [y/N]

          Comment


          • #6
            Originally posted by Oblivian View Post
            Seems theres some variation depending on Dump1090 version

            Was that the latest raspian OS? Finding some other quirks with it too. It appears either the sticks, or something on the later PIs are being detected first and associated as the wrong device to pick
            it's the windows one. I don't have rasperry pi

            Comment

            Working...
            X