Announcement

Collapse
No announcement yet.

PROBLEM Aircraft Tracked 1 - Aircraft Uploaded: 0

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

  • PROBLEM Aircraft Tracked 1 - Aircraft Uploaded: 0

    3cf3db78250a3c7f4b171a468276b42f.png
    db1652f6cf3a07423148006bab41f40c.png

    7d6bf27a1e2c712a6b3505c6986547ed.png

  • #2
    same here at my raspberry

    Comment


    • #3
      Issue these 2 commands, and post output of second command

      Code:
      sudo systemctl stop fr24feed
      
      fr24feed

      Comment


      • #4
        Originally posted by abcd567 View Post
        Issue these 2 commands, and post output of second command

        Code:
        sudo systemctl stop fr24feed
        
        fr24feed

        Could it be that the problem is that the name of my radar is "T-LELC33" belonging to LELC and it is a nearby airport?

        LELC is permanently closed and has no flights

        If i change the latitude and longitude to another nearby airport than if it were open, could i solve this problem?
        Last edited by d0x1; 2020-08-28, 09:22.

        Comment


        • #5
          No, radar is just a name. It's decided how to allocate on a position near your given details at signup.

          Changing those details run risk of data being modified with wrong data and range etc report wrong.
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment


          • #6
            Originally posted by Oblivian View Post
            No, radar is just a name. It's decided how to allocate on a position near your given details at signup.

            Changing those details run risk of data being modified with wrong data and range etc report wrong.
            Okey, Thanks!

            Comment


            • #7
              Originally posted by abcd567 View Post
              Issue these 2 commands, and post output of second command

              Code:
              sudo systemctl stop fr24feed
              
              fr24feed

              d0x1:
              You did not post output as requested in above post.

              Note:
              (1) After you issue last command, after 10 seconds, press Ctrl and C keys togather to break output, else it will continue giving output.
              (2) Output is too big to be covered by a screen shot. Copy paste it.


              .
              Last edited by abcd567; 2020-08-28, 12:28.

              Comment


              • #8
                Having exactly the same here. Receiving (tracking) somtimes 1 Aircraft, but keeping "Aircraft uploaded: 0"
                Did the fr24feed, as recommended.
                One error Message was to switch to GMT (from Vienna timezone), did this, nothing changed.
                Log - Output:
                ------------------------------
                /dev/shm/decoder.txt: Permission denied
                [main][e]Could not create monitor file!
                Could not open /var/log/fr24feed/fr24feed.log for writing!
                ______ _ _ _ _ _ _____ ___
                | ___|| |(_) | | | | | | / __ \ / |
                | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
                | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
                | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
                \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
                __/ |
                |___/

                [main][i]FR24 Feeder/Decoder
                [main][i]Version: 1.0.26-9/generic
                [main][i]Built on Oct 14 2020 07:35:30 (HEAD-de0814c.git/Linux/static_armel)
                [main][i]Running on: raspbian10
                [main][i]Local IP(s): 192.n.n.n
                [main][i]Copyright 2012-2020 Flightradar24 AB
                [main][i]www. flightradar24. com
                [main][i]DNS mode: PING
                [main][i]Automatic updates are ENABLED
                ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
                info | [httpd]Server started, listening on :::8754
                [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
                [d]TLSConnection::ctor(): Enable verify_peer in production code!
                [main][i]Reader thread started
                [main][i]Socket server started
                [master][i]Starting processing thread
                [reader][i]Initializing reader
                [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability--raw)
                [reader][i]Connected to the receiver, configuring
                [reader][i]Configured, processing messages
                [bs][i]Initializing server
                ---------------------------
                Last edited by hobbyflieger; 2021-01-24, 13:36.

                Comment


                • #9
                  Is here already a solution? I have the same problem. I now, that actual there are not so many airplanes. But my flightradar us uploading realy nothing.

                  Code:
                  21-02-07 20:00:24.822 [E] Local time: 2021-02-07 20:00:24 +0100
                  21-02-07 20:00:24.822 [E] GMT+0 time: 2021-02-07 19:00:24 +0100
                  21-02-07 20:00:24.822 [E] Your machine should be set as GMT+0 time zone!
                  21-02-07 20:00:24.822 [W] Time zone is not set to GMT+0
                  /dev/shm/decoder.txt: Permission denied
                  [main][e]Could not create monitor file!
                  Could not open /var/log/fr24feed/fr24feed.log for writing!
                  ______ _ _ _ _ _ _____ ___
                  | ___|| |(_) | | | | | | / __ \ / |
                  | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
                  | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
                  | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
                  \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
                  __/ |
                  |___/
                  [main][i]FR24 Feeder/Decoder
                  [main][i]Version: 1.0.25-1/generic
                  [main][i]Built on Mar 5 2020 14:41:55 (HEAD-138e2b2.git/Linux/static_armel)
                  [main][i]Running on: pi24-raspbian10
                  [main][i]Local IP(s): 192.168.178.28
                  [main][i]Copyright 2012-2020 Flightradar24 AB
                  [main][i]https://www.flightradar24.com
                  [main][i]DNS mode: PING
                  [main][i]Automatic updates are ENABLED
                  ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
                  info | [httpd]Server started, listening on 0.0.0.0:8754
                  [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
                  [d]TLSConnection::ctor(): Enable verify_peer in production code!
                  [main][i]Reader thread started
                  [master][i]Starting processing thread
                  [reader][i]Initializing reader
                  [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --raw --mlat)
                  [main][i]Socket server started
                  [bs][i]Initializing server
                  [reader][i]Connected to the receiver, configuring
                  [reader][i]Configured, processing messages
                  [bs][i]Starting server on 0.0.0.0:30003
                  [main][i]MLAT data feed started
                  [mlat][i]Waiting for MLAT configuration
                  Sun Feb 7 20:00:25 2021 CET EB_SOURCE EB_VERSION starting up.
                  Using sample converter: UC8, integer/table path
                  Found 1 device(s):
                  0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                  usb_claim_interface error -6
                  Error opening the RTLSDR device: Device or resource busy
                  [reader][i]Connection terminated
                  [main][i]Terminating child process 6153 with SIGTERM
                  [time][i]Synchronizing time via NTP
                  [time][i]Time synchronized correctly, offset +0.011 seconds
                  [feed][i]Downloading configuration
                  [main][i]Feed Network client started
                  [main][i]RAW data server started
                  [raw][i]Initializing server
                  [raw][i]Starting server on 0.0.0.0:30002
                  [feed][d]fetching configuration
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  [feed][i]configuring decoder
                  [feed][c]Max range AIR: 350.0nm
                  [feed][c]Max range GND: 100.0nm
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  [feed][i]configuration changed
                  info | [stats]Stats thread started
                  [feed][i]defined 3 servers
                  [feed][c]Timestamps: optional
                  info | Stopping ReceiverACSender threads for feed
                  info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: EDDW175, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
                  info | Network thread connecting to 185.218.24.22:8099 for feed EDDW175
                  [feed][n]EDDW175@185.218.24.22:8099/UDP
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  [feed][n]connecting
                  [feed][n]connected via UDP (fd 28)
                  [feed][i]Feed connected
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  [feed][n]working
                  error | write - missing monitor file pointer
                  [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --raw --mlat)
                  [reader][i]Connected to the receiver, configuring
                  [reader][i]Configured, processing messages
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  Sun Feb 7 20:00:31 2021 CET EB_SOURCE EB_VERSION starting up.
                  Using sample converter: UC8, integer/table path
                  Found 1 device(s):
                  0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                  usb_claim_interface error -6
                  Error opening the RTLSDR device: Device or resource busy
                  [reader][i]Connection terminated
                  [main][i]Terminating child process 6165 with SIGTERM
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --raw --mlat)
                  [reader][i]Connected to the receiver, configuring
                  [reader][i]Configured, processing messages
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  Sun Feb 7 20:00:36 2021 CET EB_SOURCE EB_VERSION starting up.
                  Using sample converter: UC8, integer/table path
                  Found 1 device(s):
                  0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                  usb_claim_interface error -6
                  Error opening the RTLSDR device: Device or resource busy
                  [reader][i]Connection terminated
                  [main][i]Terminating child process 6170 with SIGTERM
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --gain -10 --raw --mlat)
                  [reader][i]Connected to the receiver, configuring
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer
                  [reader][i]Configured, processing messages
                  error | write - missing monitor file pointer
                  error | write - missing monitor file pointer

                  Comment


                  • #10
                    Open your own thread as this gets too complicated eventually with multiple people having an issue.
                    While the issue might seem similar to you ... it can have a completely different reason.

                    Generally debugging fr24feed is very annoying in my opinion.
                    Just install a standalone decoder: https://github.com/wiedehopf/adsb-sc...ion-for-readsb
                    And install graphs so you know how many messages / aircraft you receive: https://github.com/wiedehopf/graphs1090#graphs1090


                    You both likely have very bad reception.
                    Move the antenna away from all monitors, especially monitors connected with an HDMI cable are very problematic.
                    Place the antenna in a window or the attic.

                    If you have a whip / magnetic base antenna place the antenna on a metal can like this:
                    https://media.discordapp.net/attachm...401&height=436
                    https://media.discordapp.net/attachm...343&height=436

                    Comment


                    • #11
                      Nevermind being 25-1 and abundance of other errors.

                      If you know your don't 'see' many, there's likely little to upload even if above errors we're fixed as fr24 needs constant data. Not bits.

                      Take the signal improvement above as first steps

                      format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).
                      # [1.0.26-9] -
                      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                      Comment


                      • #12
                        Thank you. In my case it is a magnetic based antenna. I already installed it on a radiator. It is next to a window.
                        As in the beginning of this thread is explained, the Radar shows an Aircraft tracked, but will not upload anything. Is there a mistake in the options? And when so, where can i have a look?
                        Perhaps it is much more difficult.

                        Comment


                        • #13
                          It won't upload data for an aircraft unless it is receiving a certain minimum amount of data from it.

                          On the radiator isn't as good as on a can. The can will elevate it also so it doesn't sit at the bottom of the window.
                          And cutting it to length can help a lot.
                          What about proximity to monitors, you checked on that?

                          The number for aircraft uploaded being less than aircraft track is normal.

                          Comment

                          Working...
                          X