Announcement

Collapse
No announcement yet.

Flightradar24 decoder/feeder BETA testing (Win/RPi/Linux/OSX)

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • I have been feeding data to FR24 since 2013, using my Windows Desktop & DVB-T Receiver.

    Couple of days ago I purchased Raspberry Pi B+, and installed on it PiAware (A package consisting of Raspbian OS+Dump1090+Flightaware Data feeder).

    Today I installed FR24 Data feeder software fr24feed_1.0.11-3_armhf.deb on my RPi B+.
    After completing the installations as per FR24 instruction manual, I gave command "service fr24feed status". Following is displayed

    Code:
    pi@piaware ~ $ service fr24feed status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2015-01-21 08:43:56.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-CYYZ9.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    I checked Dump1090's display on my Desktop's web browser by typing "http://<IP address of RPI on LAN DHCP/NAT>:8080", and it started displaying Google Map & Planes. The receiver is NOT down but FR24 feeder is showing it down!!!
    Last edited by abcd567; 2015-01-21, 09:37.

    Comment


    • Please post your config file (without the sharing key),, or send it to support@fr24.com, otherwise it's a matter of guessing. All I can say is that the receiver type/configuration is incorrect.

      Comment


      • Originally posted by piopawlu View Post
        How about using Remote Desktop Access?
        This happens when i close the feeder window with the X. I suppose is the same when i try to power off.
        Clipboard01.png

        Comment


        • Yes, but on my test machine that app dies after 10 seconds even when I don't click the OK button. The reason for this is that if somebody clicks the "[x]" of the console window it will kill the feeder, but the dump1090 will be left running in background. While it doesn't matter on shutdown,, it does when someone is closing it manually.

          I will check if I get the SHUTDOWN even before the close event and then disable the popup.

          Comment


          • The time sync issue I tried to explain in post #339 doesn't seem to be fixed in 1.0.11-3.
            I still need to restart fr24feed around 30 minutes after the box startup for the feeder to 'realize' sync is ok.

            Comment


            • Sent you an email.

              Comment


              • I am continuing to have the same problem as before - but I'm not certain it is a time-sync problem as it says in the log (see below):

                Time synchronized correctly, offset +0.0005 seconds

                I'm wondering if the key I'm using is still valid.

                Is there anyway to determine if the key I have is valid or not?

                Blort

                >>>>>> fr24feed Feeder version = 1.0.11-3 <<<<<<
                2015-01-21 05:54:07 | [main][i]FR24 Feeder/Decoder [0x02117000]
                2015-01-21 05:54:07 | [main][i]Version: 1.0.11-3/generic
                2015-01-21 05:54:07 | [main][i]Built on 20150120-1413 (r:master-a7f7edf.git/Linux/armv7l)
                2015-01-21 05:54:07 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
                2015-01-21 05:54:07 | [main][i]Flightradar24 AB(http://flightradar24.com)
                2015-01-21 05:54:07 | [httpd][i]Server started, listening on 0.0.0.0:8754
                2015-01-21 05:54:07 | [main][i]Reader 0 started
                2015-01-21 05:54:07 | [main][i]Waiting for GPS time
                2015-01-21 05:54:07 | [master][i]Starting processing thread
                2015-01-21 05:54:07 | [reader][i][0]Initializing reader
                2015-01-21 05:54:07 | [reader][i][0]Connecting to Generic receiver via (tcp://127.0.0.1:45105)
                2015-01-21 05:54:07 | [reader][i][0]Connected to the receiver, authenticating
                2015-01-21 05:54:07 | [reader][i][0]Authenticated, processing messages
                2015-01-21 05:54:12 | [main][i]Waiting for GPS time
                2015-01-21 05:54:17 | [main][i]Waiting for GPS time
                2015-01-21 05:54:22 | [main][i]Waiting for GPS time
                2015-01-21 05:54:27 | [main][i]Waiting for GPS time
                2015-01-21 05:54:32 | [time][i]Synchronizing time via NTP
                2015-01-21 05:54:36 | [time][i]Time synchronized correctly, offset +0.0005 seconds
                2015-01-21 05:54:36 | [main][i]Feed Network client started
                2015-01-21 05:54:36 | [feed][i]Downloading configuration
                2015-01-21 05:54:37 | [e]HTTP Response: [HTTP/1.1 404 Not Found]
                2015-01-21 05:54:37 | [feed][i]Failed on start, Sleeping 120 seconds

                Comment


                • Sorry, the ARMV7L version seems to be built for GPS enabled boxes,, I took it down and will replace it with a fixed one.

                  Comment


                  • I have a few questions with RPi... I have it running and feeding to FR all ok. But...

                    For RPi... In my /etc/fr24feed.ini ::
                    PHP Code:
                    receiver="dvbt"
                    fr24key="*******"
                    path="/usr/lib/fr24/dump1090"
                    bs="yes"
                    raw="yes"
                    logmode="3" 
                    1:
                    If I wish to use the 'Malcolm Robb's fork' version - do I just change 'dvbt' to 'dvbt-mr'?

                    2.
                    Is there any difference with MR's version other than the web interface? I.e. is one better at receiving? Or does one use less resources?

                    3.
                    I'm confused as to which services use 'raw' 30002 and 'basestation' 30003 feeds.
                    Could someone explain which each is for, and if it's ok to disable any of them?
                    I enjoy using http://radarview.flightradar24.com/ as well with local data so I don't want to disrupt this. But I'm not sure which feed that would be attached to?

                    4.
                    Step 4.3 - Enter your additional dump1090 arguments or leave empty
                    $:
                    I left this empty... If I use the '--interactive --net --net-http-port 8080' that I see people talking about. Will I have to disable bs and raw as above?


                    Thanks for any help! And sorry for all the questions, but after trying to read through the topic I'm still left a bit confused with a few bits...
                    toString - London, UK
                    FR24 - T-EGLC55 / PiAware - toString / PlaneFinder - 9008
                    Raspberry Pi B+ | Keedox DVB-T USB RTL-SDR [RTL2832U+R820T] | Stock Antenna

                    Comment


                    • I have been feeding data to FR24 since 2013, using my Windows Desktop & DVB-T Receiver.

                      Couple of days ago I purchased Raspberry Pi B+, and installed on it PiAware img, a package consisting of Raspbian OS+Dump1090 (or some other decoder)+Flightaware Data feeder.

                      Today I installed FR24 Data feeder software fr24feed_1.0.11-3_armhf.deb on my RPi B+.
                      After completing the installations as per FR24 instruction manual, I gave command "service fr24feed status". Following is displayed

                      Code:
                      pi@piaware ~ $ service fr24feed status
                      [ ok ] FR24 Feeder/Decoder Process: running.
                      [ ok ] FR24 Stats Timestamp: 2015-01-21 17:46:02.
                      [ ok ] FR24 Link: connected [UDP].
                      [ ok ] FR24 Radar: T-CYYZ9.
                      [ ok ] FR24 Tracked AC:.
                      [FAIL] Receiver: down ... failed!
                      I checked Dump1090's display on my Desktop's web browser by typing "http://<IP address of RPI on LAN DHCP/NAT>:8080", and it started displaying Google Map & Planes. The receiver is NOT down but FR24 feeder is showing it down!!!

                      Piaware Dump1090.PNG
                      Last edited by abcd567; 2015-01-21, 18:05.

                      Comment


                      • Originally posted by abcd567 View Post
                        I checked Dump1090's display on my Desktop's web browser by typing "http://<IP address of RPI on LAN DHCP/NAT>:8080", and it started displaying Google Map & Planes. The receiver is NOT down but FR24 feeder is showing it down!!!
                        I asked for your config and didn't get it yet. Red colour is not necessary to get attention here either and if it shows it as down it means the connection to it is down. Decoder works with multiple receivers and in most cases it's connected directly to the device.

                        If you are running it together with PiAware you need to set the receiver type to avr-tcp and set the host to localhost:30002. You cannot have two decoders attaching to one USB device. It is mentioned in the FAQ section of the PDF file.

                        Comment


                        • Originally posted by piopawlu View Post
                          I asked for your config and didn't get it yet. Red colour is not necessary to get attention here either and if it shows it as down it means the connection to it is down. Decoder works with multiple receivers and in most cases it's connected directly to the device.

                          If you are running it together with PiAware you need to set the receiver type to avr-tcp and set the host to localhost:30002. You cannot have two decoders attaching to one USB device. It is mentioned in the FAQ section of the PDF file.
                          Thanks for advising to see FAQ section of PDF Guide.
                          Followed instructions in FAQ, and problem was solved. Please see three screenshots below. All action was taken from my Windows Desktop using SSH through PuTTY.

                          FR24 setup on PiAware-1.PNG . FR24 setup on PiAware-2.PNG . FR24 setup on PiAware-3.PNG

                          Comment


                          • All good now,, the next build will detect PiAware and try to prevent conflicts automatically.

                            Comment


                            • I'm on day 2 now of using RPi with my usb tuner..
                              It's very very quiet around here at Heathrow at night (as it closes!) and my range is extremely limited, so I basically assume I won't receive any aircraft between 00:00 and 05:00.

                              So at around 01:00 my logs show:

                              PHP Code:
                              2015-01-22 01:44:33 | [feed][n]ping 161
                              2015
                              -01-22 01:44:55 | [reader][w][0]Global timeout exceeded0 msgs0 resyncsreconnecting
                              2015
                              -01-22 01:44:55 | [reader][i][0]Connection terminated
                              2015
                              -01-22 01:44:55 | [main][i]Terminating child process 3642 with SIGETERM
                              2015
                              -01-22 01:45:00 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 01:45:00 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 01:45:00 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 01:45:03 | [feed][n]ping 162
                              2015
                              -01-22 01:45:33 | [feed][n]ping 163
                              2015
                              -01-22 01:46:03 | [feed][n]ping 164
                              2015
                              -01-22 01:46:33 | [feed][n]ping 165
                              2015
                              -01-22 01:47:00 | [stats][i]sent 16 bytes
                              2015
                              -01-22 01:47:03 | [feed][n]ping 166
                              2015
                              -01-22 01:47:33 | [feed][n]ping 167
                              2015
                              -01-22 01:48:03 | [feed][n]ping 168
                              2015
                              -01-22 01:48:33 | [feed][n]ping 169
                              2015
                              -01-22 01:49:04 | [feed][n]ping 170
                              2015
                              -01-22 01:49:34 | [feed][n]ping 171
                              2015
                              -01-22 01:50:04 | [feed][n]ping 172
                              2015
                              -01-22 01:50:34 | [feed][n]ping 173
                              2015
                              -01-22 01:51:04 | [feed][n]ping 174
                              2015
                              -01-22 01:51:06 | [time][i]Synchronizing time via NTP
                              2015
                              -01-22 01:51:08 | [time][i]Time synchronized correctlyoffset -0.0016 secondsdrift 0.0000 seconds/minute
                              2015
                              -01-22 01:51:34 | [feed][n]ping 175
                              2015
                              -01-22 01:52:04 | [feed][n]ping 176
                              2015
                              -01-22 01:52:34 | [feed][n]ping 177
                              2015
                              -01-22 01:53:04 | [feed][n]ping 178
                              2015
                              -01-22 01:53:34 | [feed][n]ping 179
                              2015
                              -01-22 01:54:04 | [feed][n]ping 180
                              2015
                              -01-22 01:54:34 | [feed][n]ping 181
                              2015
                              -01-22 01:55:04 | [feed][n]ping 182
                              2015
                              -01-22 01:55:16 | [reader][w][0]Global timeout exceeded0 msgs0 resyncsreconnecting
                              2015
                              -01-22 01:55:16 | [reader][i][0]Connection terminated
                              2015
                              -01-22 01:55:16 | [main][i]Terminating child process 3644 with SIGETERM
                              2015
                              -01-22 01:55:21 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 01:55:21 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 01:55:21 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 01:55:34 | [feed][n]ping 183 
                              And I can interpret that every 10mins the process reconnects to my dvbt stick. (The 600 secs for global timeout (--gt=600). This continues to happen between 01:00 and 02:00. This appears normal to me.

                              However at 02:05 it starts doing this continuously (maybe 6 times in 1 minute):

                              PHP Code:
                              2015-01-22 02:05:35 | [feed][n]ping 203
                              2015
                              -01-22 02:05:37 | [reader][w][0]Global timeout exceeded0 msgs0 resyncsreconnecting
                              2015
                              -01-22 02:05:37 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:05:37 | [main][i]Terminating child process 3647 with SIGETERM
                              2015
                              -01-22 02:05:42 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:05:42 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:05:42 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:05:42 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:05:42 | [main][i]Terminating child process 3662 with SIGETERM
                              2015
                              -01-22 02:05:48 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:05:48 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:05:48 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:05:48 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:05:48 | [main][i]Terminating child process 3663 with SIGETERM
                              2015
                              -01-22 02:05:54 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:05:54 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:05:54 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:05:54 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:05:54 | [main][i]Terminating child process 3664 with SIGETERM
                              2015
                              -01-22 02:05:59 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:05:59 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:05:59 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:05:59 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:05:59 | [main][i]Terminating child process 3665 with SIGETERM
                              2015
                              -01-22 02:06:05 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:06:05 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:06:05 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:06:05 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:06:05 | [main][i]Terminating child process 3666 with SIGETERM
                              2015
                              -01-22 02:06:05 | [feed][n]ping 204
                              2015
                              -01-22 02:06:10 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:06:10 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:06:10 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:06:10 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:06:10 | [main][i]Terminating child process 3667 with SIGETERM
                              2015
                              -01-22 02:06:16 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:06:16 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:06:16 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:06:16 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:06:16 | [main][i]Terminating child process 3668 with SIGETERM
                              2015
                              -01-22 02:06:21 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:06:21 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:06:21 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:06:21 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:06:21 | [main][i]Terminating child process 3669 with SIGETERM
                              2015
                              -01-22 02:06:27 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:06:27 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:06:27 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:06:27 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:06:27 | [main][i]Terminating child process 3670 with SIGETERM
                              2015
                              -01-22 02:06:33 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090  --raw)
                              2015-01-22 02:06:33 | [reader][i][0]Connected to the receiverauthenticating
                              2015
                              -01-22 02:06:33 | [reader][i][0]Authenticatedprocessing messages
                              2015
                              -01-22 02:06:33 | [reader][i][0]Connection terminated
                              2015
                              -01-22 02:06:33 | [main][i]Terminating child process 3671 with SIGETERM
                              2015
                              -01-22 02:06:35 | [feed][n]ping 205 
                              It then goes on to do this constantly for the next 6 or so hours (you can imagine how much log space that took up!) Until I wake up and noticed it reporting offline to FR24 website. I had to restart the service manually and then everything was back to normal...


                              What could be the cause of this?
                              toString - London, UK
                              FR24 - T-EGLC55 / PiAware - toString / PlaneFinder - 9008
                              Raspberry Pi B+ | Keedox DVB-T USB RTL-SDR [RTL2832U+R820T] | Stock Antenna

                              Comment


                              • The cause is a dump1090 process that's stuck in background,, and therefore a new app dies instantly (can't open USB). I will try to make a fix and kill solution for that when using dump1090 directly from fr24feed.

                                Comment

                                Working...
                                X