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

  • Originally posted by piopawlu View Post
    Yeah,, sed replace must have stripped "r" rather than "\r" which I was going for. Even if I don't understand why the LF/CRLF would make any difference for JS/HTML code... I will make yet another build tomorrow.. but it's difficult to fix the crash problem not being able to reproduce it in any way...

    Thanks for your feedback.. I will read it more throughly tomorrow at work.
    Yep, the JSs are built-up somewhat "tricky" - for what reason I don't know. However, they work fine when they (and the hmtl and the css) are in the UNIX format. You will surely see when you run them on your Windows platform.

    Meanwhile I've performed - just for testing purposes - a fallback to fr24feed_win32-1.0.9-3.

    In detail I used the release fr24feed_win32-1.0.11-7 as a base. Then I just replaced the file "fr24feed.exe" with the "fr24feed.exe" from release fr24feed_win32-1.0.9-3. All other files are from fr24feed_win32-1.0.11-7 (except those in "public_html" and "coolclock", where I currently use "my" UNIX-format files).

    Results (up to now after performing some run-and-terminate feeder sessions):
    -> absolutely no crashes
    -> no difference in behaviour concerning "first run after boot" and "second/subsequent run after boot"
    If the current release would behave like that (looking on termination behaviour and toggle-window behaviour), this would be great.

    Conclusion:
    I perceive some incorrect programming in the releases after fr24feed_win32-1.0.9-3, maybe some incorrect memory allocation or something like that (just speculation)?

    I could, if you like, test a later release (eg. a 1.0.10.xxx) for termination/toggling behaviour. Please tell me, if I should do so.

    Regards, -Wolli-
    Last edited by Wolli; 2015-02-02, 09:44. Reason: minor corrections

    Comment


    • The difference is capturing application output to save it in log files and add timestamps. It works on all other platforms without any problems, and it works on my Win8 test virtual machine.. I will try to find out why it crashes but having no way to reproduce it is not very helpful.

      Comment


      • Originally posted by piopawlu View Post
        The difference is capturing application output to save it in log files and add timestamps. It works on all other platforms without any problems, and it works on my Win8 test virtual machine.. I will try to find out why it crashes but having no way to reproduce it is not very helpful.
        Strange seems, that the termination sequence does not always proceeed in the same manner. Sometimes so, sometimes so. Please look e.g. at the following screenshot. It contains the console window's output of two termination sequences (fr24feed_win32-1.0.11-7).
        TERM.gif
        Note that the lower one contains the line
        -> [master][i]Terminating on request
        while the upper one does not contain this line. May this help? Regards, -Wolli-

        BTW: For more easy bug tracking/fixing you might consider to place additional console message outputs into the code which only appear when a "debug mode" is activated (e.g. in the ini file)?
        Last edited by Wolli; 2015-02-02, 12:25. Reason: added "BTW"

        Comment


        • We'll move this to email from now on, and I will delete all these posts as nobody else reported Windows trouble and this thread is heavily dominated by them. I will contact you using the email provided here soon.

          Comment


          • Originally posted by piopawlu View Post
            ...I will delete all these posts as nobody else reported Windows trouble...
            This is not correct, see postings #401 and #403. In my posting #402 I stated already that this bug - for me on my machine - is not critical. I will definitely not invest much time in a bug that is relatively harmless for me on my machine, when I'm the only one who has trouble.
            Last edited by Wolli; 2015-02-02, 13:42.

            Comment


            • Hi,

              I've been through the documentation and all this forum pages (eyeballs are aching now).
              I still have a doubt.
              I'm using latest release on Windows XP.
              Radio is RTL-SDR dongle.

              With this set-up, is it possible to connect to a RAW or BS feed from Virtual Radar (or ADSBscope) ?
              I know about the --net rtl1090 and fr24feed conflict, but I don't know if the RAW stream is available somewhere...

              Thanks for your help.
              Regards,
              Yan.

              Comment


              • Hi Yan,

                you can find some information about this in the "fr24feed-manual.pdf - 2015-01-08" (downloadable on webpage http://feed.flightradar24.com/windows/ ) at the very end of section 3.2 ("In case of the DVBT stick...")

                Going into detail I assume that you already sucessfully installed the Zadig driver.

                To use the FR24-feeder (downloaded from the webpage above) together with ADSBscope I do here as follows:

                1) Open a DOS box and start the dump1090 utility as follows:
                -> mr-dump1090.exe --net --interactive --net-beast --net-ro-port 31001
                Some aircraft data should now be displayed in the DOS box.

                2) The configuration site of the FR24 feeder (browser http://localhost:8754/settings.html ) needs these parameters:
                Receiver: AVR (TCP)
                Host/IP: localhost:30002

                3) Configuration of ADSBscope:
                a) Menu: other->Network->Network setup: (please see screenshot)
                NWS.gif
                b) Menu: decoder: "beast" is selected
                c) To start ADSBscope watching for aircraft data click the button "start RAW-data client" in the button line just below the menu.

                This configuration works in this way on my side. Maybe some other slightly different configs work also, I don't know. Good luck and kind regards, -Wolli-
                Last edited by Wolli; 2015-02-04, 13:50. Reason: added 3)c)

                Comment


                • I tried the new version today but it doesn't work... any tips?
                  the old version didn't like my Flightfeeder (it appears you are usingn too old version of Basestation etc...)
                  This one connects but doesn't get any data. When i open virtual radar it gets 1000-1500 msgs/Sec.

                  ini file:
                  receiver="beast-tcp"

                  fr24key=""

                  host="192.168.0.247:30003"

                  bs="no"

                  raw="no"

                  logmode="2"

                  fr24 website:
                  Your feeds
                  Radar: T-EBAW15 Status: Offline Last upload (~5min): 2014-09-17 19:42:04 More info

                  log:
                  2015-02-04 21:30:53 | [main][i]Version: 1.0.11-6/generic
                  2015-02-04 21:30:53 | [main][i]Built on Jan 29 2015 15:59:23 (r:284/Windows/i386)
                  2015-02-04 21:30:53 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
                  2015-02-04 21:30:53 | [main][i]Flightradar24 AB(http://flightradar24.com)
                  2015-02-04 21:30:53 | [main][i]Reader 0 started
                  2015-02-04 21:30:53 | [time][i]Synchronizing time via NTP
                  2015-02-04 21:30:53 | [master][i]Starting processing thread
                  2015-02-04 21:30:53 | [reader][i][0]Initializing reader
                  2015-02-04 21:30:53 | [reader][i][0]Connecting to Generic receiver via (tcp://192.168.0.247:30003)
                  2015-02-04 21:30:53 | [httpd][i]Server started, listening on 0.0.0.0:8754
                  2015-02-04 21:30:53 | [reader][i][0]Connected to the receiver, authenticating
                  2015-02-04 21:30:53 | [reader][i][0]Authenticated, processing messages
                  2015-02-04 21:30:57 | [time][i]Time synchronized correctly, offset +0.0009 seconds
                  2015-02-04 21:30:57 | [main][i]Feed Network client started
                  2015-02-04 21:30:57 | [feed][i]Downloading configuration
                  2015-02-04 21:30:57 | [feed][c]Interval: 5s
                  2015-02-04 21:30:57 | [feed][c]Latitude: 51.2200
                  2015-02-04 21:30:57 | [feed][c]Longitude: 4.2870
                  2015-02-04 21:30:57 | [feed][c]GND: YES
                  2015-02-04 21:30:57 | [feed][c]NonADSB: YES
                  2015-02-04 21:30:57 | [feed][c]Timestamps: optional
                  2015-02-04 21:30:57 | [feed][c]Max range AIR: 350.0nm
                  2015-02-04 21:30:57 | [feed][c]Max range GND: 100.0nm
                  2015-02-04 21:30:57 | [feed][i]defined 1 server
                  2015-02-04 21:30:57 | [feed][n]EBAW15@83.140.21.66:8099/UDP
                  2015-02-04 21:30:57 | [feed][n]connecting
                  2015-02-04 21:30:57 | [stats][i]Stats thread started
                  2015-02-04 21:30:57 | [feed][n]connected
                  2015-02-04 21:30:57 | [feed][n]switching to UDP
                  2015-02-04 21:30:57 | [feed][n]working
                  2015-02-04 21:31:27 | [feed][n]ping 1
                  2015-02-04 21:31:57 | [feed][n]ping 2

                  edit: some more copy/paste stuff
                  ac_map_size="1600"
                  build_arch="i386"
                  build_flavour="generic"
                  build_os="Windows"
                  build_revision="284"
                  build_timetamp="Jan 29 2015 15:59:23"
                  build_version="1.0.11-6"
                  cfg_baudrate=""
                  cfg_bs="no"
                  cfg_host="192.168.0.247:30003"
                  cfg_mpx=""
                  cfg_path=""
                  cfg_raw="no"
                  cfg_receiver="beast-tcp"
                  cfg_windowmode="0"
                  d11_map_size="0"
                  feed_alias="T-EBAW15"
                  feed_current_mode="UDP"
                  feed_current_server="83.140.21.66"
                  feed_last_attempt_time="1423081857"
                  feed_last_config_attempt="1423081857"
                  feed_last_config_info=""
                  feed_last_config_result="success"
                  feed_last_connected_time="1423081857"
                  feed_status="connected"
                  feed_status_message=""
                  fr24key="private"
                  last_json_utc="1423083057"
                  last_rx_connect_status="OK"
                  last_rx_connect_time="1423082329"
                  last_rx_connect_time_s="2015-02-04 20:38:49"
                  msg_ring_full="0"
                  msg_ring_length="0"
                  rx_connected="1"
                  shutdown="no"
                  time_update_utc="1423083104"
                  time_update_utc_s="2015-02-04 20:51:44"
                  timing_is_valid="1"
                  timing_last_drift="+0.0007"
                  timing_last_offset="+0.0012"
                  timing_last_result="success"
                  timing_time_last_attempt="1423083064"
                  timing_time_last_success="1423083064"
                  timing_time_since_last_success="603"
                  Last edited by Franzke; 2015-02-04, 20:55.

                  Comment


                  • Hi Wolli,

                    Thanks for your very exhaustive answer.
                    What I was actually missing was the "--net-beast --net-ro-port 31001" parameters.
                    Now everything is working perfectly! Virtual Radar sees the RAW stream and FR24 feeds it to the website.

                    Next step will be to make this run on a CubieBoard 2 I will borrow from a friend.

                    Then I will try to improve my antenna installation (cheap coaxial collinear) to improve the coverage in the northern directions.
                    This will not be easy as my antenna pole is a bit crowded and interactions are not easy to avoid.

                    Thanks again.
                    Regards,
                    Yan.

                    Originally posted by Wolli View Post
                    Hi Yan,

                    1) Open a DOS box and start the dump1090 utility as follows:
                    -> mr-dump1090.exe --net --interactive --net-beast --net-ro-port 31001
                    Some aircraft data should now be displayed in the DOS box.

                    Comment


                    • @piopawlu

                      I am now feeding with the raspberry pi feeder. But I can go back to OSX-feeder on request for beta testing.

                      See how it goes with the pi...
                      Last edited by StDt; 2015-02-06, 10:27. Reason: double correction

                      Comment


                      • Hi Wolli,

                        I think I answered you yesterday but my post has disappeared...
                        I was missing the --net-beast and --net-ro-port parameters.
                        Now everything is working perfectly.
                        I am currently improving my antenna (coaxial collinear).
                        I will also soon try a standalone decoder/feeder using a Cubieboard I will borrow from a friend.

                        Thanks again for your very detailed answer.
                        Regards,
                        Yan.
                        Originally posted by Wolli View Post
                        Hi Yan,

                        you can find some information about this in the "fr24feed-manual.pdf - 2015-01-08" (downloadable on webpage http://feed.flightradar24.com/windows/ ) at the very end of section 3.2 ("In case of the DVBT stick...")

                        Going into detail I assume that you already sucessfully installed the Zadig driver.

                        To use the FR24-feeder (downloaded from the webpage above) together with ADSBscope I do here as follows:

                        1) Open a DOS box and start the dump1090 utility as follows:
                        -> mr-dump1090.exe --net --interactive --net-beast --net-ro-port 31001
                        Some aircraft data should now be displayed in the DOS box.

                        2) The configuration site of the FR24 feeder (browser http://localhost:8754/settings.html ) needs these parameters:
                        Receiver: AVR (TCP)
                        Host/IP: localhost:30002

                        3) Configuration of ADSBscope:
                        a) Menu: other->Network->Network setup: (please see screenshot)
                        [ATTACH=CONFIG]5625[/ATTACH]
                        b) Menu: decoder: "beast" is selected
                        c) To start ADSBscope watching for aircraft data click the button "start RAW-data client" in the button line just below the menu.

                        This configuration works in this way on my side. Maybe some other slightly different configs work also, I don't know. Good luck and kind regards, -Wolli-

                        Comment


                        • Originally posted by xv4y View Post
                          Hi Wolli,

                          I think I answered you yesterday but my post has disappeared...
                          I was missing the --net-beast and --net-ro-port parameters.
                          Now everything is working perfectly.
                          I am currently improving my antenna (coaxial collinear).
                          I will also soon try a standalone decoder/feeder using a Cubieboard I will borrow from a friend.

                          Thanks again for your very detailed answer.
                          Regards,
                          Yan.
                          Hi Yan, glad I could help. Good luck for your attempts improving antenna and station, -Wolli-

                          Comment


                          • The raspberry pi feeder seems to be much more reliable than the osx feeder.

                            Just guess when I started using the pi:

                            fr24-availability.jpg

                            Comment


                            • I just tried the feeder, not working..

                              EDIT: Never mind.. my bad entering the fr24auth key ....


                              The only problem I have now is that my VRS can't connect to it... I've tried several settings but none seem to take effect.. none of the ports (30002, 30002, 30334) seem to work..
                              Last edited by t-kclt2; 2015-02-08, 21:40.

                              Comment


                              • since i got no answer i tried other stuff and now it works
                                if you have a flightfeeder select 4-raw and port 30002. then it works.... basestation and port 30003 do not work.

                                Comment

                                Working...
                                X