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 Keithj
    What a friendly place this is! I don't know everything, which is why I came here looking for help. It seems no help is to be had, only insults, so I'll go away again.

    I did read the tutorial, but like I said it's written for those who already know the answer. I didn't download VRS because the FR24 search engine didn't know what "VRS" was (you see what I mean about "for those who already know the answer") but I most certainly DID download and try ADSBscope, as I mentioned above - you know, where I said "I get either "No decoder detected" or "BEAST comm. failure: 0"."

    Since you don't know the answer to my question above, I'll go away and Google in the hope of finding someone who does.
    Have a look here Keith http://www.virtualradarserver.co.uk/ it does all that I need. I know exactly how you feel about the hostility on this forum, the main reason I do not post often.

    Comment


    • Thank you, Milliam. I downloaded virtualradarserver and installed it. It can't see any data on any of the port numbers that have been suggested as I've gone through (30002, 30003, 31011). I think there must be a "switch" in the latest FR24feed.exe to tell it to output data in some format, but I can't find that in the instructions.

      There is a forum at virtualradarserver, so I'll go and enquire there in the hope there's someone friendly who knows the answer.

      Comment


      • Try port 30334 with AVR or Beast raw feed selected.

        Comment


        • Thank you. No aircraft are appearing yet in VRS

          If I try port 30002 and then "Test Connection", it says "A connection can be made with these settings". The Feed Status shows "connected", but nothing appears in the Messages/Aircraft tracked columns.

          I tried ports 30003, 31011 and 30334, all with AVR or Beast Raw Feed, and all trigger the response "No connection could be made because the target machine actively refused it". I tried to run VRS "as administrator" but that box was greyed out. I tried the Wizard, which suggested 30005 but that also was actively refused.

          I modified the FR24feed.ini file to remove the mpx="no" line, which allowed the FR24feed panel to open the Web status/config (it wouldn't do that with mpx="no").

          I'll see what happens if I run VRS with FR24feed turned off, and point it straight at the dongle. Maybe FR24feed can take the output from VRS.

          Comment


          • First of all, you are writing in two different topics about same thing.
            Second of all, I nicely told you that you can have what you need with those two programs. You said NO that is not it, and you didn't even connect it to your receiver.
            Third of all, I already told you that in that FR24 feeder you need to have raw and bs options enabled for this to work.

            I'm trying to help you from the beginning and your comments are: NO

            Now, go to Fr24 feeder folder. there si .conf file, edit it with notepad or something, copy your sharing key (or if you have it in e-mail, even better). DELETE the file. Start your feeder and configure it again.
            During configuration Enable RAW and BS Ports
            Then in VRS set your receiver in basestation format port 30003 or whatever it is .
            Done

            Bold is just in case of problems with e-mail
            Last edited by Amper; 2015-04-18, 17:13.
            For official support use Contact Form

            Comment


            • Yes, I did connect it to my receiver (or tried to). That didn't work. That's why I asked the further questions.

              There was no .conf file in the FR24 feeder folder. There were a .ini file and a .key file.
              I removed both of those. Reconfiguring, it wanted to know the receiver type. I told it DVBT stick, because that's what I have.
              Then it asked for additional dump1090 commands (or leave empty). I don't know any, so left it empty.
              I told it yes to the raw and BS questions.
              It wrote me a new .ini file that looks like this:
              receiver="dvbt"
              fr24key="################"
              path="mr-dump1090.exe"
              bs="yes"
              raw="yes"
              logmode="2"

              That works as far as feeding data to FR24, just as it did before.

              Then I reinstalled and started VRS. It's set to Basestation/Network/127.0.0.1:30002. It says it's connected, but sees nothing.
              I tried port 30003 and got the message "No connection could be made because the target machine actively refused it".

              If I turn off FR24feed and run RTL1090, then VRS sees aircraft (and RTL1090 also shows that there is a connection). However, I don't need VRS if I'm running RTL1090.

              The other problem with VRS is that it doesn't stick to the folder it's told to use, but starts creating its own folders elsewhere on the PC - in C:\Users. For reasons nothing to do with FR24, creating data folders on drive C is not acceptable. If I use VRS, I will have to set up a redirect to send it back to its own folder.

              Anyway, that's enough for one day. Supper calls.

              Comment


              • I read the thread to search a solution to my problem, but, probably, I missed something...
                Mac OS X Yosemite 10.10.3, latest FR24feedOSX, DVTB USB Dongle: dump1090 detects transponders but upload to FR24 fail.

                Here is my .fr24feed.ini:

                receiver="dvbt"
                fr24key=“xxxxxxxxxxxxxxxx”
                path="./dump1090"
                bs="no"
                raw="yes"
                logmode="2"
                Here is a log abstract:

                2015-04-19 12:32:21 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
                2015-04-19 12:32:21 | [main][i]Flightradar24 AB(http://flightradar24.com)
                2015-04-19 12:32:21 | [main][i]Reader 0 started
                2015-04-19 12:32:21 | [time][i]Synchronizing time via NTP
                2015-04-19 12:32:21 | [master][i]Starting processing thread
                2015-04-19 12:32:21 | [reader][i][0]Initializing reader
                2015-04-19 12:32:21 | [reader][i][0]Connecting to Generic receiver via (exe:///Applications/FR24FeedOSX.app/Contents/Resources/dump1090 --raw)
                2015-04-19 12:32:21 | [reader][i][0]Connected to the receiver, authenticating
                2015-04-19 12:32:21 | [reader][i][0]Authenticated, processing messages
                2015-04-19 12:32:21 | [httpd][i]Server started, listening on 0.0.0.0:8754
                2015-04-19 12:33:12 | [time][i]Time synchronized correctly, offset -54.0070 seconds
                2015-04-19 12:33:12 | [main][i]Feed Network client started
                2015-04-19 12:33:12 | [main][i]RAW data server started
                2015-04-19 12:33:12 | [feed][i]Downloading configuration
                2015-04-19 12:33:12 | [raw][i]Initializing server
                2015-04-19 12:33:12 | [raw][i]Starting server on 0.0.0.0:30002
                2015-04-19 12:33:12 | [feed][c]Interval: 5s
                2015-04-19 12:33:12 | [feed][c]Latitude: 45.9500
                2015-04-19 12:33:12 | [feed][c]Longitude: 13.1700
                2015-04-19 12:33:12 | [feed][c]GND: YES
                2015-04-19 12:33:12 | [feed][c]NonADSB: YES
                2015-04-19 12:33:12 | [feed][c]Timestamps: optional
                2015-04-19 12:33:12 | [feed][c]Max range AIR: 350.0nm
                2015-04-19 12:33:12 | [feed][c]Max range GND: 100.0nm
                2015-04-19 12:33:12 | [feed][i]defined 1 server
                2015-04-19 12:33:12 | [feed][n]LIPD2@83.140.21.66:8099/UDP
                2015-04-19 12:33:12 | [feed][n]connecting
                2015-04-19 12:33:12 | [stats][i]Stats thread started
                2015-04-19 12:33:12 | [feed][n]connected
                2015-04-19 12:33:12 | [feed][n]switching to UDP
                2015-04-19 12:33:12 | [feed][n]working
                2015-04-19 12:33:50 | [feed][n]ping 1
                2015-04-19 12:34:20 | [feed][n]ping 2
                2015-04-19 12:34:32 | [feed][n]syncing stream
                2015-04-19 12:35:03 | [feed][n]ping 1
                2015-04-19 12:35:53 | [feed][n]ping 1
                2015-04-19 12:36:04 | [feed][i]removed 2 of 4 AC
                2015-04-19 12:36:04 | [feed][n]syncing stream
                2015-04-19 12:36:28 | [feed][i]removed 1 of 3 AC
                Thanks.

                LIPD2

                Comment


                • Jeepers guys.

                  Cool the jets.

                  For one, these are posted in the wrong thread. This is for the official simple non-beta FR24 feed app - I'll move them momentarily and clear out the personal abuse.

                  Secondly, people appear to trying to setup a lot of functions at once and need to slow things down a bit. We are all aware there is no all-in-1 solution. And as such often need a few apps running inline to get the desired results to ones preference while others are content to see the data online only.

                  Thus to that, it is my suggestion to anyone following along/new to this to ensure you understand the advanced beta feeder is not for the faint hearted if you have little or no networking or data flow mapping/knowledge.
                  The best place is to start with core basic sharing and work on local graphical lists etc from there given there are a number of configurations.

                  You have to be aware of the limitations. All of these can only access _1_ piece of physical hardware at a time (yes, I am aware of some go-between apps which can double the output but that is next level)
                  VRS, FR24feed (BETA!!!) and Dump1090 can ALL directly connect to Dongles/USB AND output the data in various formats to flow down to other apps. But need to be carefully configured to do so. (I have 6 in line!)

                  If you enable the server on every one of these, you run into such issues as mentioned here where the connecting app cannot receive data as there are no connections left, or using the same port.

                  Starting at the top of the tree, you need to decide what app you want to connect to the physical device and configure it as such.
                  For other apps to use the data, you also need to enable any inbuilt servers within the app to start the chain and make special note of their ports.

                  In this case, if you want all data passed along to other apps such as VRS, you need to configure fr24feed beta with an onboard RAW server (passes the same data it receives) and AVR server. These can only handle ~5 simultaneous connections

                  From the fr24feed download locations there are readmes where this is clarified
                  dvbt - DVBT USB dongle connected directly via USB. Only one DVBT dongle can
                  be used at a time. When using with stand alone dump1090 instance or another
                  software defined radio demodulator please use the “avr-tcp” receiver type instead
                  The above essentially will capture the data from Dump1090, and become 2nd inline and send it also to FR24.

                  --raw=BOOL - Defaults to “no” and decides whether or not the RAW data stream should be
                  available on port 30334 for all receivers but DVBT which uses port 30002 instead. When
                  using dump1090 with “--net” please disable as that feed is already provided and otherwise
                  it will cause conflicts.
                  As you can see above, if you use FR24feed as the primary program to attach to the USB device, you need to turn OFF the Dump1090 listening server.
                  With this option on the FR24 software then sends and 'listens' for connections - you then configure other software to connect to either 30002 for RAW received data (some software can use RAW data) or AVR/BS data on 30003 - again, requires an adjustment if using dump90 separately.

                  From there, you configure downstream apps to connect to a 'server' on the corresponding ports/data types.

                  My suggestion. Blank bit of paper. Write down the data flow, including port listen/connect numbers remembering it is best practice to have 1 server, and attach other applications to that
                  (VRS has a re-broadcast server of it's own to re-send the same data!) Start with 1, add another and so on to confirm you do not have multiple servers setup.

                  And if you don't want the fancy web stats on FR24 and just want to feed them, stick with the standard feed app - which doesn't connect to hardware, but is made to be 2nd in line+ and attaches to data on port 30003 (configurable as Dump1090 has raw output on 30002 and BS on 30003)
                  Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                  Comment


                  • On same hardware, but Parallels + Windows CP Pro, all goes good.
                    Have someone an idea?

                    Cheers

                    Pierluigi LIPD2
                    Originally posted by snapovaz View Post
                    I read the thread to search a solution to my problem, but, probably, I missed something...
                    Mac OS X Yosemite 10.10.3, latest FR24feedOSX, DVTB USB Dongle: dump1090 detects transponders but upload to FR24 fail.

                    Here is my .fr24feed.ini:



                    Here is a log abstract:



                    Thanks.

                    LIPD2

                    Comment


                    • Following the advice and recommendations above, I've had a week's experience running version 1.0.11.7 with no other SSR software. Since I couldn't get VRS or any of the other stuff to work alongside it, I just stop it and run RTL1090 when I want to see what's happening in the non-ADS-B world. Then I restart 1.0.11.7.

                      There is only one problem. About once a day - often when I'm not here - fr24feed.exe triggers a crash alert with an Event 1000 error message on the PC screen. As far as I can see, it carries on working and sending information to FR24 despite the error message. If I stop and restart it after the crash, it says it's working but sends no data. It sits there pinging something (it doesn't say what). If I restart the PC, it works normally again. As far as I can tell, nothing else on the PC has a problem.

                      There is no message in the fr24feed.log, but the Windows Event Viewer shows this:

                      Faulting application name: fr24feed.exe, version: 1.0.11.7, time stamp: 0x54cb9e7b
                      Faulting module name: ntdll.dll, version: 6.1.7601.18798, time stamp: 0x5507b3e0
                      Exception code: 0xc0000005
                      Fault offset: 0x00032ef6
                      Faulting process id: 0x1d54
                      Faulting application start time: 0x01d07ea7681f44cf
                      Faulting application path: H:\SDR\FR24 feed\fr24feed.exe
                      Faulting module path: C:\Windows\SysWOW64\ntdll.dll
                      Report Id: d264d8a4-ea9a-11e4-8779-0030678f962e

                      Can anyone suggest what might be causing this or how to cure it?

                      Comment


                      • Further to the above...

                        After the most recent crash (and after the above), 1.0.11.7 can't see the dongle at all. Unplugging and replugging made no difference. RTL1090 sees it fine, and 1.2.3.2 connects to that and feeds OK.
                        I unplugged the usual dongle and connected a spare, whereupon 1.0.11.7 worked again - for about an hour, before it crashed again. Error message:
                        Faulting application name: fr24feed.exe, version: 1.0.11.7, time stamp: 0x54cb9e7b
                        Faulting module name: ntdll.dll, version: 6.1.7601.18798, time stamp: 0x5507b3e0
                        Exception code: 0xc0000264
                        Fault offset: 0x000a2785
                        Faulting process id: 0x1a30
                        Faulting application start time: 0x01d07f61d1b606ca
                        Faulting application path: H:\SDR\FR24 feed\fr24feed.exe
                        Faulting module path: C:\Windows\SysWOW64\ntdll.dll
                        Report Id: 3f83b6c6-eb56-11e4-bde3-0030678f962e

                        Comment


                        • I've tried a different dongle, on a different USB port (direct on the PC). 1.0.11.7 still crashes after a few hours. Same error each time, as above. RTL1090 plus 1.2.3.2 remains stable with no problems. Am I the only person with this problem? It's a pretty standard Win 7 64-bit PC.

                          Comment


                          • I'm also getting the same crash, several times a day, from the time I started using this latest version. If I remember right, I also got it with the previous version.
                            F-LLBG3, T-LLBG17

                            Comment


                            • Error 1000 is a general application failure.

                              It could be caused by a number of things, Power save mode on the USB (thinking it is not in use). Overloading of the server ports etc etc. Issue with the way it calls the DLLs to directly talk to the hardware, or MR-Dump1090 crashing

                              Just the ping is a sign of no-incoming data from receiver, which is normal if you have no planes, or the input data is kaput. It keeps comms open with FR servers with a heartbeat.
                              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                              Comment


                              • Indeed. But RTL1090 just carries on working day-in and day-out, and the feed to FR 1.2.3.2 keeps working. The details don't show on the FR Your Account / Feeds page, but that does report that it's working.
                                I have no more diagnostic information than shown above, so I can't suggest anything else. If I'm the only one with the problem, then it's not important. If it's a common problem, then it might be worth fixing.

                                Comment

                                Working...
                                X