Announcement

Collapse
No announcement yet.

Please advice me. Im going mad

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

  • Please advice me. Im going mad

    Hi All,

    I have a Windows 10 x64 pc which I want to use as a dedicated feeder machine for FR24.

    I purchased a DVBT stick which is Realtek 2832u device.

    I keep getting a connection terminated on the feeder program.

    I have even tried changing drivers using Zadig.

    Please can someone advise me. Ive played with this now for days and followed endless manuals for this.

    BELOW IS WHAT I GET



    [main][i]FR24 Feeder/Decoder
    [main][i]Version: 1.0.18-9/generic
    [main][i]Built on Apr 21 2017 14:51:08 (???/Windows/i386)
    [main][i]Copyright 2012-2017 Flightradar24 AB
    [main][i] the link which I cant post as I'm new.com
    [main][i]Reader thread started
    [reader][i]Initializing reader
    [master][i]Starting processing thread
    [httpd][i]Server started, listening on 0.0.0.0:8754
    [time][i]Synchronizing time via NTP
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [time][i]Time synchronized correctly, offset +0.0500 seconds
    [main][i]Feed Network client started
    [feed][i]Downloading configuration
    [feed][c]Interval: 5s
    [feed][c]Latitude: 51.8747
    [feed][c]Longitude: -0.3683
    [feed][c]GND: YES
    [feed][c]NonADSB: YES
    [feed][c]Timestamps: optional
    [feed][c]Max range AIR: 350.0nm
    [feed][c]Max range GND: 100.0nm
    [feed][i]defined 5 servers
    [stats][i]Stats thread started
    [feed][n]EGGW127@83.140.21.112:28099/UDP
    [feed][n]connecting
    [feed][n]connected via UDP (fd 1040)
    [feed][n]working
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [feed][n]ping 1
    [feed][n]syncing stream result: 1
    [reader][i]Connecting to DVBT receiver via (mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe:/ /mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe:/ /mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe:/ /mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated

  • #2
    Close it, restart PC and only run dump1090-mr itself and look for messages.

    Either wrong tuner (chipset right can have wrong tuner)

    Or wrong USB device selected which needs additional commands to setup page added to select usb2 or similar

    Sent from my XT1092 using Tapatalk
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      this is what I got back

      Found 2 device(s):
      0: ■, ┤■, SN: (currently selected)
      1: , , SN:
      usb_open error -12
      Error opening the RTLSDR device: No error

      Comment


      • #4
        See here

        https://forum.flightradar24.com/showthread.php?p=96119

        Sent from my XT1092 using Tapatalk
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #5
          Which file do I modify to make the new command work in fr24 please? I think the new command works

          mr-dump1090.exe --raw --device-index 1

          How do I make fr24 use the command?

          Comment


          • #6
            [main][i]FR24 Feeder/Decoder
            [main][i]Version: 1.0.18-9/generic
            [main][i]Built on Apr 21 2017 14:51:08 (???/Windows/i386)
            [main][i]Copyright 2012-2017 Flightradar24 AB
            [main][i]THE LINK I CANNOT POST
            [main][i]Reader thread started
            [reader][i]Initializing reader
            [time][i]Synchronizing time via NTP
            [httpd][i]Server started, listening on 0.0.0.0:8754
            [master][i]Starting processing thread
            [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw --device-index 1 --raw)
            [reader][i]Connected to the receiver, configuring
            [reader][i]Configured, processing messages
            [time][i]Time synchronized correctly, offset +1.0433 seconds
            [main][i]Feed Network client started
            [feed][i]Downloading configuration
            [feed][c]Interval: 5s
            [feed][c]Latitude: 51.8747
            [feed][c]Longitude: -0.3683
            [feed][c]GND: YES
            [feed][c]NonADSB: YES
            [feed][c]Timestamps: optional
            [feed][c]Max range AIR: 350.0nm
            [feed][c]Max range GND: 100.0nm
            [feed][i]defined 5 servers
            [feed][n]EGGW127@83.140.21.85:8099/UDP
            [feed][n]connecting
            [stats][i]Stats thread started
            [feed][n]connected via UDP (fd 1564)
            [feed][n]working
            [feed][n]ping 1
            [feed][n]syncing stream result: 1
            [feed][n]ping 2
            [feed][n]syncing stream result: 1
            [feed][n]ping 3

            Comment


            • #7
              that is now a sign of no aircraft. either none near, bad reception, or not tuned

              if starting dump1090-mr does not say "rafael tuner detected" but rather "ft0013" or similar. it is not a suitable stick

              Sent from my GT-I9300 using Tapatalk
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


              • #8
                Originally posted by Oblivian View Post
                that is now a sign of no aircraft. either none near, bad reception, or not tuned

                if starting dump1090-mr does not say "rafael tuner detected" but rather "ft0013" or similar. it is not a suitable stick

                Sent from my GT-I9300 using Tapatalk
                To elaborate on instructions by Oblivian, see image below:

                NOTE:
                If you run mr-dump1090.exe with antenna and pigtail connected, received ADS-B messages will make the screen to scroll so rapidly, you wont be able to read initial few lines where necessary information about DVB-T is displayed. Some times even leaving pigtail connected to DVB-T can catch enough ADS-B signal to make screen scroll. Better disconnect even the pigtail from DVB-T.

                Last edited by abcd567; 2017-09-26, 17:04.

                Comment


                • #9
                  example.jpg

                  This is what I get now - AFTER I modded the .ini file to say mr-dump1090.exe --raw --device-index 1
                  Last edited by jonnybobs; 2017-09-26, 19:09.

                  Comment


                  • #10
                    Restart Windows with DVB-T plugged-in.
                    Run fr24feed.exe only ONCE, and check again.
                    Last edited by abcd567; 2017-09-26, 21:32.

                    Comment


                    • #11
                      You cannot run both together like that. (run task manager and kill all instances)

                      Forget FR24feed for now. The need is to confirm the USB is correct first. And then setup FR24feed with the working setup afterward.

                      FR24 launches Dump1090-mr as part of its startup sequence - this is the USB connector - one instance at a time
                      And does not display all the info in the FR24 window when it does so.

                      Running it on its own confirmed the next step - the need to change USB device

                      Which later need to add the same --device-index 1 into the additional commands in FR24feed config web-page or .ini to select USB 2 instead.

                      The same has to be put into commandline for running dump1090-mr to see full details of the tuner for above suggestion - your screenshot shows it is still using 0 not 1


                      You could see stuff appear if it has, and signal is OK (with planes in area)

                      THen the same working commands get added to the web-config page of fr24feed. The only difference when running fr24feed is you don't see above happen in the background.

                      So you need a CMD window in the same location as fr24feed. And run dump1090-mr --device-index 1 and report back the tuner found once correct USB selected.

                      https://forum.flightradar24.com/thre...ll=1#post94712

                      it is not clear if this is a Windows10, or newer USB stick causing the issue. But it has only recently arisen that it is not auto detected for you.
                      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                      Comment


                      • #12
                        For test, only ONE instance of mr-dump1090.exe should run. NO instance of fr24feed.exe should be running.

                        First disconnect antenna and pigtail from DVB-T. Keep the DVB-T plugged into computer.

                        Now kill all instances of fr24feed.exe and mr-dump1090.exe by Restarting Windows10.

                        After Windows10 has restarted, double-click mr-dump1090.exe. Do NOT double click more than once, else a second instance may start, and the test will fail. Also DO NOT start fr24feed.exe, else test will fail.

                        Now check what console window displays.

                        Comment


                        • #13
                          Originally posted by abcd567 View Post
                          For test, only ONE instance of mr-dump1090.exe should run. NO instance of fr24feed.exe should be running.

                          First disconnect antenna and pigtail from DVB-T. Keep the DVB-T plugged into computer.

                          Now kill all instances of fr24feed.exe and mr-dump1090.exe by Restarting Windows10.

                          After Windows10 has restarted, double-click mr-dump1090.exe. Do NOT double click more than once, else a second instance may start, and the test will fail. Also DO NOT start fr24feed.exe, else test will fail.

                          Now check what console window displays.
                          We've already found it auto selects wrong device, so needs to run via CMD and confirm the chipsets after selecting device 1 v 0
                          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                          Comment


                          • #14
                            Originally posted by Oblivian View Post
                            We've already found it auto selects wrong device, so needs to run via CMD and confirm the chipsets after selecting device 1 v 0
                            Oh, ok. I have missed to realize this. Thanks for clarifying.

                            Comment

                            Working...
                            X