Announcement

Collapse
No announcement yet.

Aircraft tracked reads zero

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

  • Aircraft tracked reads zero

    HI
    In the last 24 hours my Flightradar24 is playing up.
    After a reboot, all works great for about 5 minutes tracking and sending, then aircraft tracked drops to zero, but sent does not.
    Its running from a PI, i have updated to the latest software versions.


    FR24 Link: Connected via UDP
    FR24 Radar Code: T-XXXXXXXXX
    Local IP(s): 192.XXX.X.XX
    Aircraft Tracked:
    (ModeS & ADS-B) 0
    Aircraft Uploaded: 36
    Receiver: dvbt, Connected
    MLAT running: YES

    Thanks

  • #2
    Most likely a defective power supply.

    If possible use the "Official RPi power supply".

    Comment


    • #3
      Not changed the way the power is setup, i do have a USB extension cable in the power supply.

      Comment


      • #4
        Power supplies can go bad.

        Reception stopping after some time is typical of power issues.

        Comment


        • #5
          ok, will check it out, thanks for replying

          Comment


          • #6
            I also had my feed stop on May 23, 2019.
            I have the FlightAware piaware image installed and running well, so I know there is no hardware problem.

            sudo systemctl stop fr24feed
            sudo systemctl start fr24feed
            No change. Maybe I should have used the restart clickie from piaware.local:8754
            Rebooted the pi.
            Back to working.

            I had many
            2019-05-29 10:32:44 | [reader][e]Could not connect to tcp://localhost:30005
            even after the manual restart of fr24feed.

            Since this is a shared piaware feed, with dump109-fa being the primary, maybe this has something to do with a piaware update.
            There was a listener on 30005, but I actually don't see that ESTABLISHED while the feed is successful, after the reboot.

            $ sudo netstat -pan | grep 3000
            tcp 0 0 0.0.0.0:30002 0.0.0.0:* LISTEN 539/dump1090-fa
            tcp 0 0 0.0.0.0:30003 0.0.0.0:* LISTEN 539/dump1090-fa
            tcp 0 0 0.0.0.0:30004 0.0.0.0:* LISTEN 539/dump1090-fa
            tcp 0 0 0.0.0.0:30005 0.0.0.0:* LISTEN 539/dump1090-fa
            tcp 0 0 127.0.0.1:37540 127.0.0.1:30002 ESTABLISHED 623/fr24feed
            tcp 0 0 127.0.0.1:30002 127.0.0.1:37540 ESTABLISHED 539/dump1090-fa
            tcp6 0 0 :::30002 :::* LISTEN 539/dump1090-fa
            tcp6 0 0 :::30003 :::* LISTEN 539/dump1090-fa
            tcp6 0 0 :::30004 :::* LISTEN 539/dump1090-fa
            tcp6 0 0 :::30005 :::* LISTEN 539/dump1090-fa
            tcp6 0 0 ::1:30005 ::1:35982 ESTABLISHED 539/dump1090-fa
            tcp6 0 0 ::1:30005 ::1:35984 ESTABLISHED 539/dump1090-fa
            tcp6 0 0 ::1:35984 ::1:30005 ESTABLISHED 859/fa-mlat-client
            tcp6 0 0 ::1:35982 ::1:30005 ESTABLISHED 871/faup1090

            Comment


            • #7
              Clardold:

              Change your configuration: edit /etc/fr24feed.ini

              Change receiver and host so it reads like this:
              Code:
              receiver="beast-tcp"
              fr24key="xxxxxxxxxxxxxxxx"
              host="127.0.0.1:30005"
              bs="no"
              raw="no"
              restart fr24feed

              Comment


              • #8
                Originally posted by ClarDold View Post
                There was a listener on 30005, but I actually don't see that ESTABLISHED while the feed is successful, after the reboot.

                $ sudo netstat -pan | grep 3000
                tcp 0 0 0.0.0.0:30002 0.0.0.0:* LISTEN 539/dump1090-fa
                tcp 0 0 127.0.0.1:37540 127.0.0.1:30002 ESTABLISHED 623/fr24feed
                tcp 0 0 127.0.0.1:30002 127.0.0.1:37540 ESTABLISHED 539/dump1090-fa
                Seems it's connecting via 30002.
                Anyway do what i describe in my post above.

                avr-tcp protocol is unreliable in current fr24feed version.

                Comment


                • #9
                  All power appears to be ok

                  Comment


                  • #10
                    KevinG: did you try another power supply?
                    power appears to be ok does not mean there is enough voltage available to the dongle.
                    If you have a powered USB hub, try using the dongle via that.


                    You can do this:

                    sudo systemctl stop fr24feed
                    sudo fr24feed

                    This will give you the log on the console, hopefully you can copy the log when the problem occurs?

                    Comment


                    • #11
                      Yes i have changed the power supply, does make any difference, sadly

                      Comment


                      • #12
                        Yes, i have tried another power supply.
                        Thanks for the code suggestion, see below

                        2019-05-29 20:07:30 | [main][i]FR24 Feeder/Decoder
                        2019-05-29 20:07:30 | [main][i]Version: 1.0.23-8/generic
                        2019-05-29 20:07:30 | [main][i]Built on Oct 11 2018 18:27:28 (HEAD-3c696a7.git/L inux/static_armel)
                        2019-05-29 20:07:30 | [main][i]Running on: pi24-raspbian9
                        2019-05-29 20:07:30 | [main][i]Local IP(s): 192.168.0.13
                        2019-05-29 20:07:30 | [main][i]Copyright 2012-2018 Flightradar24 AB
                        2019-05-29 20:07:30 | [main][i]https://www.flightradar24.com
                        2019-05-29 20:07:30 | [main][i]DNS mode: PING
                        2019-05-29 20:07:30 | [main][i]Automatic updates are ENABLED
                        2019-05-29 20:07:30 | OK
                        2019-05-29 20:07:30 | [main][i]Reader thread started
                        2019-05-29 20:07:30 | [main][i]MLAT data feed started
                        2019-05-29 20:07:30 | [reader][i]Initializing reader
                        2019-05-29 20:07:30 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin /dump1090-mutability --raw --mlat)
                        2019-05-29 20:07:30 | [mlat][i]Waiting for MLAT configuration
                        2019-05-29 20:07:30 | [master][i]Starting processing thread
                        2019-05-29 20:07:30 | [httpd][i]Server started, listening on 0.0.0.0:8754
                        2019-05-29 20:07:30 | [reader][i]Connected to the receiver, configuring
                        2019-05-29 20:07:30 | [reader][i]Configured, processing messages
                        Wed May 29 20:07:30 2019 BST dump1090-mutability v1.14 starting up.
                        Found 1 device(s):
                        0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                        Found Rafael Micro R820T tuner
                        Max available gain is: 49.60 dB
                        Setting gain to: 49.60 dB
                        Exact sample rate is: 2000000.052982 Hz
                        2019-05-29 20:07:31 | [time][i]Synchronizing time via NTP
                        Gain reported by device: 49.60 dB
                        2019-05-29 20:07:31 | [reader][w]Setting new UTC offset: 0!
                        cb transfer status: 1, canceling...
                        Wed May 29 20:07:34 2019 BST Warning: lost the connection to the RTLSDR device.
                        Wed May 29 20:07:39 2019 BST Trying to reconnect to the RTLSDR device..
                        Found 1 device(s):
                        0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                        Detached kernel driver
                        Found Rafael Micro R820T tuner
                        Setting gain to: 49.60 dB
                        Exact sample rate is: 2000000.052982 Hz
                        Gain reported by device: 49.60 dB
                        cb transfer status: 1, canceling...
                        Wed May 29 20:08:02 2019 BST Warning: lost the connection to the RTLSDR device.
                        Reattaching kernel driver failed!
                        Wed May 29 20:08:07 2019 BST Trying to reconnect to the RTLSDR device..
                        Found 1 device(s):
                        0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                        Detached kernel driver
                        Found Rafael Micro R820T tuner
                        Setting gain to: 49.60 dB
                        Exact sample rate is: 2000000.052982 Hz
                        Gain reported by device: 49.60 dB
                        2019-05-29 20:08:25 | [time][i]Time synchronized correctly, offset +0.0006 seconds
                        2019-05-29 20:08:25 | [main][i]Feed Network client started
                        2019-05-29 20:08:25 | [feed][i]Downloading configuration
                        2019-05-29 20:08:25 | [feed][d]fetching configuration
                        2019-05-29 20:08:26 | [feed][i]configuring decoder
                        2019-05-29 20:08:26 | [feed][c]Max range AIR: 350.0nm
                        2019-05-29 20:08:26 | [feed][c]Max range GND: 100.0nm
                        2019-05-29 20:08:26 | [feed][i]configuration changed
                        2019-05-29 20:08:26 | [feed][i]defined 3 servers
                        2019-05-29 20:08:26 | [feed][c]Timestamps: optional
                        2019-05-29 20:08:26 | [stats][i]Stats thread started
                        2019-05-29 20:08:26 | [feed][n]EGHI121@185.218.24.22:8099/UDP
                        2019-05-29 20:08:26 | [feed][n]connecting
                        2019-05-29 20:08:26 | [feed][n]connected via UDP (fd 15)
                        2019-05-29 20:08:26 | [feed][i]Feed connected
                        2019-05-29 20:08:26 | [feed][n]working
                        2019-05-29 20:08:26 | [feed][i]sent 1,0 AC
                        2019-05-29 20:08:26 | info | Stopping ReceiverACSender threads for feed
                        2019-05-29 20:08:26 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: EGHI121, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
                        2019-05-29 20:08:26 | info | Network thread connecting to 185.218.24.22:8099 for feed EGHI121
                        2019-05-29 20:08:26 | [mlat][i]MLAT configuration received, service ENABLED
                        2019-05-29 20:08:26 | [mlat][i]Starting MLAT with preconfigured position: 50.98,-1.45,151.0
                        2019-05-29 20:08:26 | [mlat][i]MLAT bandwidth reduction active, level 1
                        2019-05-29 20:08:26 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                        2019-05-29 20:08:30 | [feed][i]removed 1 of 15 AC
                        2019-05-29 20:08:31 | [feed][i]sent 15,0 AC
                        2019-05-29 20:08:36 | [feed][i]sent 17,0 AC
                        2019-05-29 20:08:36 | [mlat][i]Registering MLAT station
                        2019-05-29 20:08:36 | [mlat][i]Registering MLAT station: SUCCESS
                        2019-05-29 20:08:38 | [mlat][i]Received ADS-B time references AC:
                        2019-05-29 20:08:38 | [mlat][i] 3451D5
                        2019-05-29 20:08:38 | [mlat][i] 40705E
                        2019-05-29 20:08:38 | [mlat][i] 43E88B
                        2019-05-29 20:08:38 | [mlat][i] 4CA7E6
                        2019-05-29 20:08:38 | [mlat][i] 4CA988
                        2019-05-29 20:08:38 | [mlat][i] 4D20F8
                        2019-05-29 20:08:38 | [mlat][i] A14700
                        2019-05-29 20:08:38 | [mlat][i]Pinging the server
                        2019-05-29 20:08:38 | [mlat][i]Stats 3122839/3122839
                        2019-05-29 20:08:58 | [mlat][i]Pinging the server
                        2019-05-29 20:08:58 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:09:06 | [feed][n]ping 1
                        2019-05-29 20:09:07 | [feed][n]syncing stream result: 1
                        2019-05-29 20:09:18 | [mlat][i]Pinging the server
                        2019-05-29 20:09:18 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:09:36 | [feed][n]ping 2
                        2019-05-29 20:09:37 | [feed][n]syncing stream result: 1
                        2019-05-29 20:09:38 | [mlat][i]Pinging the server
                        2019-05-29 20:09:38 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:09:58 | [mlat][i]Pinging the server
                        2019-05-29 20:09:59 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:10:06 | [feed][n]ping 3
                        2019-05-29 20:10:07 | [feed][n]syncing stream result: 1
                        2019-05-29 20:10:18 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:10:18 | [mlat][i]Pinging the server
                        2019-05-29 20:10:18 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:10:28 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:10:36 | [feed][n]ping 4
                        2019-05-29 20:10:37 | [feed][n]syncing stream result: 1
                        2019-05-29 20:10:38 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:10:38 | [mlat][i]Pinging the server
                        2019-05-29 20:10:38 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:10:48 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:10:59 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:10:59 | [mlat][i]Pinging the server
                        2019-05-29 20:10:59 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:11:06 | [feed][n]ping 5
                        2019-05-29 20:11:07 | [feed][n]syncing stream result: 1
                        2019-05-29 20:11:08 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:11:18 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:11:18 | [mlat][i]Pinging the server
                        2019-05-29 20:11:18 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:11:28 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:11:36 | [feed][n]ping 6
                        2019-05-29 20:11:37 | [feed][n]syncing stream result: 1
                        2019-05-29 20:11:48 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:11:48 | [mlat][i]Pinging the server
                        2019-05-29 20:11:48 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:11:50 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:11:57 | [mlat][i]Pinging the server
                        2019-05-29 20:11:57 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:12:00 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:12:06 | [feed][n]ping 7
                        2019-05-29 20:12:07 | [feed][n]syncing stream result: 1
                        2019-05-29 20:12:10 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:12:17 | [mlat][i]Pinging the server
                        2019-05-29 20:12:17 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:12:20 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:12:30 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:12:36 | [feed][n]ping 8
                        2019-05-29 20:12:37 | [feed][n]syncing stream result: 1
                        2019-05-29 20:12:37 | [mlat][i]Pinging the server
                        2019-05-29 20:12:37 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:12:40 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:12:50 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:12:57 | [mlat][i]Pinging the server
                        2019-05-29 20:12:57 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:13:00 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:13:06 | [feed][n]ping 9
                        2019-05-29 20:13:07 | [feed][n]syncing stream result: 1
                        2019-05-29 20:13:10 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:13:17 | [mlat][i]Pinging the server
                        2019-05-29 20:13:17 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:13:20 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:13:30 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:13:36 | [feed][n]ping 10
                        2019-05-29 20:13:37 | [feed][n]syncing stream result: 1
                        2019-05-29 20:13:37 | [mlat][i]Pinging the server
                        2019-05-29 20:13:38 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:13:40 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:13:50 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:13:57 | [mlat][i]Pinging the server
                        2019-05-29 20:13:57 | [mlat][i]Stats 3122839/0
                        2019-05-29 20:14:00 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:14:06 | [feed][n]ping 11
                        2019-05-29 20:14:07 | [feed][n]syncing stream result: 1
                        2019-05-29 20:14:17 | [mlat][i]No ADS-B time reference available (0/0)
                        2019-05-29 20:14:18 | [mlat][i]Pinging the server
                        2019-05-29 20:14:18 | [mlat][i]Stats 3122839/0

                        Comment


                        • #13
                          cb transfer status: 1, canceling...

                          Wed May 29 20:08:02 2019 BST Warning: lost the connection to the RTLSDR device.

                          Reattaching kernel driver failed!


                          There's your answer.

                          Stick is still going offline

                          Sent from my EML-L09 using Tapatalk
                          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                          Comment


                          • #14
                            Thanks Oblivian, i will replace the stick and see if it fixes the problem

                            Comment


                            • #15
                              If it's on an extension lead, connect directly for testing too. You get power loss over non active cables

                              Sent from my EML-L09 using Tapatalk
                              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                              Comment

                              Working...
                              X