Announcement

Collapse
No announcement yet.

Help Setting Up Flightradar24 Software

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

  • #61
    Many thanks to all here in the forum.

    Now my Raspberry is feeding.

    Comment


    • #62
      Hello everybody,

      Can anyone help me since last night my feeding software is not working anymore.

      I get the following error message.

      [ ok ] FR24 Feeder/Decoder Process: running.
      [ ok ] FR24 Stats Timestamp: 2019-10-10 06:08:56.
      [ ok ] FR24 Link: connected [UDP].
      [ ok ] FR24 Radar: T-EDDB165.
      [ ok ] FR24 Tracked AC:.
      [ ok ] Receiver: connected (0 MSGS/0 SYNC).
      [FAIL] FR24 MLAT: not running ... failed!

      Comment


      • #63
        Give following 2 commands

        sudo systemctl stop fr24feed

        fr24feed

        What do you see?
        After 30 seconds, stop output by pressing Ctrl+c keys.

        sudo killall fr24feed
        sudo systemctl restart fr24feed

        Comment


        • #64
          Hallo Berliner,
          ich hatte das selbe Problem!

          Hi to all,
          I had the same Problem, that with update 1.0.24-2 this week feeding the data has not worked anymore.
          But: they did a quick fix yesterdy in the evening to version 1.0.24-4 and now feeding is working correct again.

          So please have a look for the new version 1.0.24-4

          Regards
          ra_br

          Comment


          • #65
            Thank you all,

            I get the following as an answer.

            Should I play a new software version now?





            2019-10-10 09:34:00 | [feed][n]EDDB165@185.218.24.22:8099/UDP
            2019-10-10 09:34:00 | [feed][n]connecting
            2019-10-10 09:34:00 | [feed][n]connected via UDP (fd 25)
            2019-10-10 09:34:00 | [feed][i]Feed connected
            2019-10-10 09:34:00 | [feed][n]working
            2019-10-10 09:34:30 | [feed][n]ping 1
            2019-10-10 09:34:31 | [feed][n]syncing stream result: 1
            2019-10-10 09:35:00 | [feed][n]ping 2
            2019-10-10 09:35:30 | [feed][i]Feed disconnected
            2019-10-10 09:35:30 | [feed][n]disconnected
            2019-10-10 09:35:30 | info | [feed][n]waiting 8 seconds
            2019-10-10 09:34:00 | [feed][n]EDDB165@185.218.24.22:8099/UDP
            2019-10-10 09:34:00 | [feed][n]connecting
            2019-10-10 09:34:00 | [feed][n]connected via UDP (fd 25)
            2019-10-10 09:34:00 | [feed][i]Feed connected
            2019-10-10 09:34:00 | [feed][n]working
            2019-10-10 09:34:30 | [feed][n]ping 1
            2019-10-10 09:34:31 | [feed][n]syncing stream result: 1
            2019-10-10 09:35:00 | [feed][n]ping 2
            2019-10-10 09:35:30 | [feed][i]Feed disconnected
            2019-10-10 09:35:30 | [feed][n]disconnected
            2019-10-10 09:35:30 | info | [feed][n]waiting 8 seconds
            2019-10-10 09:35:38 | [feed][n]EDDB165@185.218.24.23:8099/UDP
            2019-10-10 09:35:38 | info | Network thread connecting to 185.218.24.23:8099 for feed EDDB165
            2019-10-10 09:35:38 | [feed][n]connecting
            2019-10-10 09:35:38 | [feed][n]connected via UDP (fd 25)
            2019-10-10 09:35:38 | [feed][i]Feed connected
            2019-10-10 09:35:38 | [feed][n]working

            Comment


            • #66
              Originally posted by wildthing01 View Post
              Thank you all,

              I get the following as an answer.

              Should I play a new software version now?





              2019-10-10 09:34:00 | [feed][n]EDDB165@185.218.24.22:8099/UDP
              2019-10-10 09:34:00 | [feed][n]connecting
              2019-10-10 09:34:00 | [feed][n]connected via UDP (fd 25)
              2019-10-10 09:34:00 | [feed][i]Feed connected
              2019-10-10 09:34:00 | [feed][n]working
              2019-10-10 09:34:30 | [feed][n]ping 1
              2019-10-10 09:34:31 | [feed][n]syncing stream result: 1
              2019-10-10 09:35:00 | [feed][n]ping 2
              2019-10-10 09:35:30 | [feed][i]Feed disconnected
              2019-10-10 09:35:30 | [feed][n]disconnected
              2019-10-10 09:35:30 | info | [feed][n]waiting 8 seconds
              2019-10-10 09:34:00 | [feed][n]EDDB165@185.218.24.22:8099/UDP
              2019-10-10 09:34:00 | [feed][n]connecting
              2019-10-10 09:34:00 | [feed][n]connected via UDP (fd 25)
              2019-10-10 09:34:00 | [feed][i]Feed connected
              2019-10-10 09:34:00 | [feed][n]working
              2019-10-10 09:34:30 | [feed][n]ping 1
              2019-10-10 09:34:31 | [feed][n]syncing stream result: 1
              2019-10-10 09:35:00 | [feed][n]ping 2
              2019-10-10 09:35:30 | [feed][i]Feed disconnected
              2019-10-10 09:35:30 | [feed][n]disconnected
              2019-10-10 09:35:30 | info | [feed][n]waiting 8 seconds
              2019-10-10 09:35:38 | [feed][n]EDDB165@185.218.24.23:8099/UDP
              2019-10-10 09:35:38 | info | Network thread connecting to 185.218.24.23:8099 for feed EDDB165
              2019-10-10 09:35:38 | [feed][n]connecting
              2019-10-10 09:35:38 | [feed][n]connected via UDP (fd 25)
              2019-10-10 09:35:38 | [feed][i]Feed connected
              2019-10-10 09:35:38 | [feed][n]working
              apt-cache policy fr24feed

              if output is not 24-4, then yes.
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


              • #67
                wildthing01, please post the output of:

                cat /etc/fr24feed.ini

                Also elaborate which image you are using.

                Comment


                • #68
                  Hello Wiedehopf,

                  I do not understand exactly, what should I do now)
                  post cat /etc/fr24feed.ini. Could you write me more exactly what I should do now to start the feeding software su.

                  Thanks in advance

                  Comment


                  • #69
                    It's a command, you put it on the console to execute.
                    Then you show the output.

                    Comment


                    • #70
                      Okay Thanks Wiedehopf

                      pi@raspberrypi:~ $ cat /etc/fr24feed.ini
                      receiver="avr-tcp"
                      fr24key="24325b69be02a584"
                      host="127.0.0.1:30002"
                      bs="no"
                      raw="no"
                      logmode="0"
                      logpath="/var/log"
                      mlat="yes"
                      mlat-without-gps="yes"

                      Comment


                      • #71
                        wildthing01

                        Method-1
                        Issue this command
                        sudo nano /etc/fr24feed.ini

                        Above command will open the file fr24feed.ini. In this file make following 2 changes:
                        (1) change
                        receiver="avr-tcp"
                        to
                        receiver="beast-tcp"

                        (2) change
                        host="127.0.0.1:30002"
                        to
                        host="127.0.0.1:30005"


                        After changes are done, press Ctrl+o keys to save, then Ctrl+x keys to close.

                        Now restart fr24feed
                        sudo systemctl restart fr24feed

                        ALTERNATIVE Method
                        In your browser go to following address:

                        IP-of-Pi:8754/settings.html

                        Change settings to make them as in the screenshot below.
                        After changes are done, click Save button, then Restart button.
                        Both these buttons are at bottom-right of settings page.

                        fr24feed setting BEAST-TCP using dump1090-fa or dump1090-mut v1.15.png
                        Last edited by abcd567; 2019-10-10, 10:00.

                        Comment


                        • #72
                          Yeah beast-tcp has less issues.
                          Do as described above.

                          Also update fr24feed:

                          sudo apt update
                          sudo apt upgrade
                          sudo reboot

                          Comment


                          • #73
                            Now I dont have latest version in Armbian Repo

                            pi@orangepipc:~$ sudo apt update

                            pi@orangepipc:~$ apt-cache policy fr24feed
                            fr24feed:
                            Installed: 1.0.23-8
                            Candidate: 1.0.23-8

                            I think I should do this:

                            sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"

                            EDIT:
                            Instead of bash command, used this:

                            Code:
                            pi@orangepipc:~$ wget http://repo.feed.flightradar24.com/rpi_binaries/fr24feed_1.0.24-4_armhf.deb
                            
                            pi@orangepipc:~$ sudo dpkg -i fr24feed_1.0.24-4_armhf.deb
                            
                            
                            pi@orangepipc:~$ apt-cache policy fr24feed                  fr24feed:                                                     
                              Installed: 1.0.24-4
                              Candidate: 1.0.24-4
                              Version table:
                             *** 1.0.24-4 100
                                    100 /var/lib/dpkg/status
                            
                            pi@orangepipc:~$ sudo systemctl restart fr24feed
                            pi@orangepipc:~$ fr24feed-status
                            [ ok ] FR24 Feeder/Decoder Process: running.
                            [ ok ] FR24 Stats Timestamp: 2019-10-10 10:46:50.
                            [ ok ] FR24 Link: connected [UDP].
                            [ ok ] FR24 Radar: T-CYYZ30.
                            [ ok ] FR24 Tracked AC: 66.
                            [ ok ] Receiver: connected (2929 MSGS/0 SYNC).
                            [ ok ] FR24 MLAT: ok [UDP].
                            [ ok ] FR24 MLAT AC seen: 64.
                            Last edited by abcd567; 2019-10-10, 10:54.

                            Comment


                            • #74
                              Hello Captain,

                              Receiver can not be changed to Mode S Best (TCP)

                              Comment


                              • #75
                                What version are you at:

                                fr24feed --version

                                Also which receiver are you using that can't do beast-tcp?
                                Aren't you using dump1090?

                                Comment

                                Working...
                                X