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

  • What did I do wrong?

    pi@raspberrypi ~ $ sudo service fr24feed status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2015-07-21 23:49:55.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-LDZA19.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!

    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 0.

    Comment


    • The current build for OS X is failed to decoding planet after file system upgrade to 10.10.4 .

      Regard
      T-ZSSS32 F-ZSSS1 force shutdown by local regulation

      Comment


      • I cannot get rtl1090 & VRS to connect to the fr24feed_win32-1.0.11-6.zip dated 2015-01-30 either. I could really use an older stable version that works properly!

        Comment


        • Originally posted by joeuser View Post
          I cannot get rtl1090 & VRS to connect to the fr24feed_win32-1.0.11-6.zip dated 2015-01-30 either. I could really use an older stable version that works properly!
          All good I found an old working copy on an old system that I used to use for my FR24 feed.

          Comment


          • Originally posted by joeuser View Post
            I cannot get rtl1090 & VRS to connect to the fr24feed_win32-1.0.11-6.zip dated 2015-01-30 either. I could really use an older stable version that works properly!
            As per this thread
            I seem to be having a little difficulty with feeding data to FlightRadar24 through the RTL1090 program. I have gotten fr24feed to work while RTL1090 is closed, and I have gotten RTL1090 to work while fr24feed is closed. The problem is that the programs do not share the data from my NESDR Mini USB dongle. I very much prefer the


            RTL will be accessing the hardware directly, And if DVBT chosen FR24feed will also do this - need to pick your running order OR use RTL first with output per my example
            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

            Comment


            • Originally posted by Oblivian View Post
              As per this thread
              {edited out as I am a new user & cannot even quote URLS}

              RTL will be accessing the hardware directly, And if DVBT chosen FR24feed will also do this - need to pick your running order OR use RTL first with output per my example
              Thank you!

              Comment


              • Originally posted by Bloods View Post
                Hi

                A bit confused about the information in the help file regarding the mpx setting.

                I have a SBS-3 outputting on port 10001 and I have the FR24feed software connecting to that ok, as far as I can tell.

                I have enabled the mpx setting and I have BaseStation connecting to FR24feed on port 20072


                The help file, in two different places states the following:-

                --mpx=BOOL - Defaults to “no” and decides whether or not the SBS1/3 compatible data
                stream should be enabled on port 10001. This option is only available when Kinetic
                Avionics receiver is used to enable Basestation connection. For all other receivers this
                options is ignored.

                To enable SBS1 compatible data feed please enable the “MPX” feed either by using the
                WWW configuration form or by adding mpx=”yes” in the fr24feed configuration file. After
                you do that you can start Basestation and configure its data interface to use TCP/IP
                connection where IP = 127.0.0.1 and port = 20072.
                * - This option is only available for those who own a Kinetic Avionics SBS1/3 family
                receiver.

                So am I to understand that FR24feed "generates" an output on port 10001 or port 20072 or both? If it's generating on port 10001 then I would need to change the setting in the SBS-3 from 10001 to something else to avoid conflict would I not?

                Could someone please clarify the correct setup and whether my understanding is correct?

                Thank-you
                When you start Basestation - go to Settings then Hardware settings. On the network tab - change address to 127.0.0.1 and port to 20072.

                This will only work with MPX = "yes".

                I discovered that Planeplotter can get raw data by using the SBS3 direct as your ADSB source, and setting the SBS3 IP address as 127.0.0.1:30006

                Comment


                • Hey there,

                  I am having a weird problem. I am using a GNS5890 USB-dongle for receiving ADS-B messages.
                  Until now I have successfully been using the old feeder (With adsbscope I set up a server for the decoded data on Port 30003, then start the feeder and voila - it just works and aircraft are transmitted).

                  However I cannot seem to get the new feeder to work. I have tried both settings: ModeS Beast (TCP) and AVR (TCP) with Host 127.0.0.1:30003.
                  The connection apparently is set up, however no aircraft are reported according to the feeder status page. The old feeder still works fine .
                  So I must be doing something wrong, but what exactly is it?

                  Any help would be appreciated.

                  Kind regards
                  Jens

                  Comment


                  • Originally posted by JensK View Post

                    However I cannot seem to get the new feeder to work. I have tried both settings: ModeS Beast (TCP) and AVR (TCP) with Host 127.0.0.1:30003.
                    The connection apparently is set up, however no aircraft are reported according to the feeder status page. The old feeder still works fine .
                    So I must be doing something wrong, but what exactly is it?
                    Sorry to have bothered you. I just found out that I did not have to set a server up. So I shut down the server and selected microsadsb (USB) and connected directly to the according COM-port. That worked flawlessly. Anyways, I think for upgraders the documentation might be somewhat clearer.

                    Comment


                    • So now the only thing I still don't get working is running the new feeder and adsbscope simultaneously.

                      As previously described it is now the feeder that accesses the GNS5890-USB-dongle on COM Port 7. So no way to have adsbscope connect to GNS5890 the same way. I have tried to set up a RAW data stream in the Feeder and then have adsbscope connect to it. And while the connection seems to work, there are no aircraft in adsbscope being shown, although the feeder uploads aircraft. Does anyone have any idea how I can get both to work?

                      Comment


                      • fr24feed glitch

                        Hi

                        When terminating fr24feed.exe (pushing the menu "Terminate FR24Feeder") also the called dump1090.exe or mr-dump1090.exe (set in ini file) should be terminated. But as I see here on Win7 only fr24feed.exe is terminated.

                        Bug or feature?
                        Best regards,
                        Rod

                        Comment


                        • What is the last version of Windows feeder?
                          On the website (http://feed.flightradar24.com/#windows) the version listed is 1.0.14-9, but when I execute it says 1.0.13.2.

                          Comment


                          • Originally posted by awg View Post
                            What is the last version of Windows feeder?
                            On the website (http://feed.flightradar24.com/#windows) the version listed is 1.0.14-9, but when I execute it says 1.0.13.2.
                            Sounds like you have not over-written your correct local copy. I just updated from 11-6, definately 14-9 now
                            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                            Comment


                            • Originally posted by Oblivian View Post
                              Sounds like you have not over-written your correct local copy. I just updated from 11-6, definately 14-9 now
                              No, if you see version 14.9 was compiled on Sep 7 2015 14:19:56, just half hour ago

                              Until this morning the last version was 13.2.

                              By the way, is MLAT enabled with 14.9?

                              Comment


                              • 1.0.14-9 persistantly crashing gone back to 1.0.11-6 also crashing

                                Windows 10 laptop, latest FR24feed keeps crashing at irregular intervals. I went back to the old version and this is also experiencing the same crash.
                                This problem is affecting some of my other feeds, MLAT Radar, ADSB-Hub, VRS etc, as they rely on FR24 feeder to suppy the output to them.

                                Just crashed yet again - Last log:-
                                2015-09-09 11:16:40 | [feed][n]syncing stream
                                2015-09-09 11:16:43 | [feed][i]removed 25 of 720 AC
                                2015-09-09 11:16:45 | [feed][i]sent 171 AC in 5 packets
                                2015-09-09 11:16:47 | [feed][i]removed 18 of 732 AC
                                2015-09-09 11:16:50 | [feed][i]sent 182 AC in 5 packets
                                2015-09-09 11:16:51 | [feed][i]removed 17 of 750 AC
                                2015-09-09 11:16:54 | [feed][i]removed 20 of 765 AC
                                2015-09-09 11:16:55 | [feed][i]sent 164 AC in 5 packets
                                2015-09-09 11:16:58 | [feed][i]removed 22 of 785 AC
                                2015-09

                                Why so many AC's? The number of AC just keeps on rising after the "Synching Stream" message:-
                                2015-09-09 11:35:02 | [feed][i]sent 90 AC in 3 packets
                                2015-09-09 11:35:07 | [feed][i]sent 85 AC in 3 packets
                                2015-09-09 11:35:12 | [feed][i]sent 90 AC in 3 packets
                                2015-09-09 11:35:17 | [feed][i]sent 83 AC in 3 packets
                                2015-09-09 11:35:22 | [feed][i]sent 83 AC in 3 packets
                                2015-09-09 11:35:27 | [feed][i]sent 99 AC in 3 packets
                                2015-09-09 11:35:27 | [feed][n]syncing stream
                                2015-09-09 11:35:29 | [feed][i]removed 1 of 195 AC
                                2015-09-09 11:35:32 | [feed][i]sent 103 AC in 3 packets
                                2015-09-09 11:35:33 | [feed][i]removed 5 of 206 AC
                                2015-09-09 11:35:37 | [feed][i]sent 96 AC in 3 packets
                                2015-09-09 11:35:41 | [feed][i]removed 2 of 223 AC
                                2015-09-09 11:35:42 | [feed][i]sent 87 AC in 3 packets
                                2015-09-09 11:35:47 | [feed][i]sent 92 AC in 3 packets
                                2015-09-09 11:35:49 | [feed][i]removed 2 of 237 AC
                                2015-09-09 11:35:52 | [feed][i]sent 99 AC in 3 packets
                                2015-09-09 11:35:53 | [feed][i]removed 1 of 249 AC
                                2015-09-09 11:35:57 | [feed][i]removed 3 of 258 AC
                                2015-09-09 11:35:57 | [feed][i]sent 99 AC in 3 packets

                                Anyone else experiencing this?
                                Is there a link I can re-grab the older version 1.0.11-6 from? I may need to do a completely fresh install.

                                Jerry
                                Last edited by slammer99uk; 2015-09-09, 10:41. Reason: additional info

                                Comment

                                Working...
                                X