Announcement

Collapse
No announcement yet.

my feeder online but can not send any data

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

  • my feeder online but can not send any data

    hi. i have tried so much but can not find any solution. my feeder is online but can not send any data. i will share you all infos abt. it.

    the console after typed "sudo fr24feed"
    HTML Code:
    2020-04-16 02:00:11 | [main][i]FR24 Feeder/Decoder
    
    2020-04-16 02:00:11 | [main][i]Version: 1.0.25-3/generic
    
    2020-04-16 02:00:11 | [main][i]Built on Apr 8 2020 07:06:55 (HEAD-5e8ef0c.git/Linux/static_armel)
    
    2020-04-16 02:00:11 | [main][i]Running on: raspbian10
    
    2020-04-16 02:00:11 | [main][i]Local IP(s): 192.168.0.27
    
    2020-04-16 02:00:11 | [main][i]Copyright 2012-2020 Flightradar24 AB
    
    2020-04-16 02:00:11 | [main][i]https://www.flightradar24.com
    
    2020-04-16 02:00:11 | [main][i]DNS mode: PING
    
    2020-04-16 02:00:11 | [main][i]Automatic updates are ENABLED
    
    2020-04-16 02:00:11 | [httpd][w]bind function failed, errno: 98, waiting 1 seconds
    
    2020-04-16 02:00:11 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
    
    2020-04-16 02:00:11 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
    
    2020-04-16 02:00:11 | [main][i]Reader thread started
    
    2020-04-16 02:00:11 | [master][i]Starting processing thread
    
    2020-04-16 02:00:11 | [main][i]MLAT data feed started
    
    2020-04-16 02:00:11 | [reader][i]Initializing reader
    
    2020-04-16 02:00:11 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
    
    2020-04-16 02:00:11 | [mlat][i]Waiting for MLAT configuration
    
    2020-04-16 02:00:11 | [reader][e]Could not connect to tcp://127.0.0.1:30005
    
    2020-04-16 02:00:12 | [httpd][w]bind function failed, errno: 98, waiting 6 seconds
    
    2020-04-16 02:00:12 | [time][i]Synchronizing time via NTP
    
    2020-04-16 02:00:13 | [time][i]Time synchronized correctly, offset +0.013 seconds
    
    2020-04-16 02:00:13 | [feed][i]Downloading configuration
    
    2020-04-16 02:00:13 | [main][i]Feed Network client started
    
    2020-04-16 02:00:13 | [feed][d]fetching configuration
    
    2020-04-16 02:00:16 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
    
    2020-04-16 02:00:16 | [reader][e]Could not connect to tcp://127.0.0.1:30005
    
    2020-04-16 02:00:18 | [httpd][w]bind function failed, errno: 98, waiting 11 seconds
    
    2020-04-16 02:00:18 | [feed][i]configuring decoder
    
    2020-04-16 02:00:18 | [feed][c]Max range AIR: 350.0nm
    
    2020-04-16 02:00:18 | [feed][c]Max range GND: 100.0nm
    
    2020-04-16 02:00:18 | [feed][i]configuration changed
    
    2020-04-16 02:00:18 | [feed][i]defined 3 servers
    
    2020-04-16 02:00:18 | [feed][c]Timestamps: optional
    
    2020-04-16 02:00:18 | info | [stats]Stats thread started
    
    2020-04-16 02:00:18 | info | Stopping ReceiverACSender threads for feed
    
    2020-04-16 02:00:18 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: LTCD2, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
    
    2020-04-16 02:00:18 | [feed][n]LTCD2@185.218.24.22:8099/UDP
    
    2020-04-16 02:00:18 | [feed][n]connecting
    
    2020-04-16 02:00:18 | info | Network thread connecting to 185.218.24.22:8099 for feed LTCD2
    
    2020-04-16 02:00:21 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
    
    2020-04-16 02:00:21 | [reader][e]Could not connect to tcp://127.0.0.1:30005
    the main problem is can not connect to 30005 port.

    this is the web status page.
    Screen Shot 2020-04-16 at 04.04.53.png

    "/etc/fr24feed.ini"
    HTML Code:
    receiver="beast-tcp"
    
    fr24key="***"
    
    host="127.0.0.1:30005"
    
    bs="no"
    
    raw="no"
    
    logmode="0"
    
    logpath="/var/log/fr24feed"
    
    mlat="yes"
    
    mlat-without-gps="yes"
    "dump1090-mutability" (all the ports are default)
    HTML Code:
    Thu Apr 16 02:07:22 2020 BST dump1090-mutability v1.15~dev starting up.
    
    Using sample converter: UC8, integer/table path
    
    Found 1 device(s):
    
    0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
    
    Found Fitipower FC0013 tuner
    
    Max available gain is: 19.70 dB
    
    Setting gain to: 19.70 dB
    
    Gain reported by device: 19.70 dB
    
    Allocating 15 zero-copy buffers

    if you need any other thing, i will upload asap. thank you for your time...




  • #2

    Found Fitipower FC0013 tuner

    https://forum.flightradar24.com/foru...e-requirements

    Adverts that specify 'Fitpower', 'FC0012' or 'FC0013' are NOT suitable for ADSB


    Unfortunately Dump1090 cannot tune that (nor can it tune to 1090) so is not starting to open the port
    Last edited by Oblivian; 2020-04-16, 01:41.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      Originally posted by Oblivian View Post
      Found Fitipower FC0013 tuner

      https://forum.flightradar24.com/foru...e-requirements

      Adverts that specify 'Fitpower', 'FC0012' or 'FC0013' are NOT suitable for ADSB


      Unfortunately Dump1090 cannot tune that (nor can it tune to 1090) so is not starting to open the port
      but i can listen the tower radio by sdr apps. is there any way to make it suitable? thanks.

      Comment


      • #4
        No. It won't tune above about 900Mhz.

        Adsb is 1090Mhz

        Tower is 120-130Mhz
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #5
          Oblivian ok, i will change my stick asap. thank you

          Comment


          • #6
            Oblivian Screen Shot 2020-04-20 at 16.06.31.pngi noticed that i am able to get 1090mhz signals on gqrx app. what you think about that, am i able to feed? why not? thanks..
            Last edited by gox; 2020-04-20, 13:16.

            Comment


            • #7
              It was explained to you already, your SDR won't work.

              What you can see is probably just noise on the center frequency.
              Tune to 1087 MHz and make a screenshot of that....

              Comment


              • #8
                wiedehopf here. has same thing too.

                Screen Shot 2020-04-20 at 16.35.14.png
                Attached Files

                Comment


                • #9
                  and i want to attach that. uplimit is close but still between
                  Screen Shot 2020-04-20 at 16.40.56.png

                  Comment


                  • #10
                    It's in the tuning range, but the reception is extremely poor.

                    And as you see ... on 1087 MHz you see the exact same "signal", but there is no signal there.
                    It's not real.
                    It's an artifact of the SDR.

                    Tune to 1089.5 and you will see there is NO SIGNAL at 1090 Mhz.

                    This isn't the first time someone has tried using such an SDR.
                    Why would we lie to you?

                    Comment


                    • #11
                      wiedehopf yeah saw it. thanks for help. would you suggest me a sdr with high performance/price? it looks like i gonna buy rtl-sdr.com's device.

                      Comment


                      • #12
                        sure, check here: https://github.com/wiedehopf/adsb-wi...-shopping-list

                        Comment

                        Working...
                        X