Announcement

Collapse
No announcement yet.

Connection terminated NooElec NESDR Mini 2+

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

  • Connection terminated NooElec NESDR Mini 2+

    I have a problem while feeding data the FlightRadar24. I have this problem on screen and my status is "offline"

    I have a NooElec NESDR Mini 2+ USB Dongle with an RTL2832U chipset
    I'm running Windows at the moment but I've tried Linux and same results
    My fr24feed version is 1.0.18-9
    I run the feeder on a virtual machine on Proxmox but I tried several VMs and even on the server itself and unfortunately didn't work.
    My VM was just installed for this setup (only zadig and the f24feed software)
    Tried the same procedures on different VMs and on bare metal

    Config page:
    receiver="dvbt"
    fr24key="(secret)"
    path="mr-dump1090.exe"
    bs="yes"
    raw="yes"
    logmode="1"
    mlat="no"
    mlat-without-gps="no"

    Logs:
    ______ _ _ _ _ _ _____ ___
    | ___|| |(_) | | | | | | / __ \ / |
    | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
    | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
    | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
    \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
    __/ |
    |___/
    [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]FR24 website
    [main][i]Reader thread started
    [master][i]Starting processing thread
    [httpd][i]Server started, listening on 0.0.0.0:8754
    [reader][i]Initializing reader
    [main][i]Socket server started
    [bs][i]Initializing server
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [time][i]Synchronizing time via NTP
    [bs][i]Starting server on 0.0.0.0:30003
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [time][i]Time synchronized correctly, offset +0.0022 seconds
    [main][i]Feed Network client started
    [feed][i]Downloading configuration
    [main][i]RAW data server started
    [raw][i]Initializing server
    [raw][i]Starting server on 0.0.0.0:30002
    [feed][c]Interval: 5s
    [feed][c]Latitude: (secret)
    [feed][c]Longitude: (secret)
    [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]ELLX69@83.140.21.85:8099/UDP
    [feed][n]connecting
    [feed][n]connected via UDP (fd 984)
    [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 (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

    I really hope you could help me please...
    Last edited by FaZeBasescu; 2017-07-11, 18:33. Reason: Added all logs

  • #2
    Need to see a lot more of the log than just the error lines.

    The start up process shoes if the device has the right tuner, can be changed to correct frequency, or not there at all

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

    Comment


    • #3
      Oh sorry. Here are my logs

      ______ _ _ _ _ _ _____ ___
      | ___|| |(_) | | | | | | / __ \ / |
      | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
      | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
      | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
      \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
      __/ |
      |___/
      [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]Flightradar24 Link
      [main][i]Reader thread started
      [master][i]Starting processing thread
      [httpd][i]Server started, listening on 0.0.0.0:8754
      [reader][i]Initializing reader
      [main][i]Socket server started
      [bs][i]Initializing server
      [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
      [time][i]Synchronizing time via NTP
      [bs][i]Starting server on 0.0.0.0:30003
      [reader][i]Connected to the receiver, configuring
      [reader][i]Configured, processing messages
      [reader][i]Connection terminated
      [time][i]Time synchronized correctly, offset +0.0057 seconds
      [main][i]Feed Network client started
      [feed][i]Downloading configuration
      [main][i]RAW data server started
      [raw][i]Initializing server
      [raw][i]Starting server on 0.0.0.0:30002
      [feed][c]Interval: 5s
      [feed][c]Latitude: xx.xxxx
      [feed][c]Longitude: xx.xxxx
      [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]ELLX69@83.140.21.87:8099/UDP
      [feed][n]connecting
      [feed][n]connected via UDP (fd 968)
      [feed][n]working
      [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)
      [feed][n]ping 1
      [reader][i]Connected to the receiver, configuring
      [reader][i]Configured, processing messages
      [feed][n]syncing stream result: 1
      [reader][i]Connection terminated
      Last edited by FaZeBasescu; 2017-07-13, 14:39.

      Comment


      • #4
        To replicate the situation, I downloaded and ran "fr24feed_win32_1.0.18-9" from my Windows 8.1 Desktop.
        I faced "Connection Terminated"

        I closed fr24feed.exe console, tried to Eject RTL2838 (i.e. DVB-T), but got message:
        "Windows cannot stop your 'RTL2838UHIDIR' device because a program is still using it. Close any programs that might be using the device, and try again later."

        Even seeing this warning, I plugged-out DVB-T from USB port of Desktop, and after 1 minute, plugged-in and started fr24feed.exe. It started working ok.

        To recheck, I again closed fr24.exe console, then after 1 minute restarted fe24feed.exe, and again got "Connection Terminated".

        I now tried another method. First tried to Eject RTL2838, and on getting warnning "Windows cannot stop your device RTL2838UHIDIR", I left the DVB-T plugged-in and restarted the windows. After windows restarted, I ran fr24feed.exe, and it started working OK.

        Comment


        • #5
          Found the reason of problem.
          When fr24feed.exe cosole is closed, it closes only the console, rest of software is still running in background and keeping DVB-T engaged. Starting fr24feed.exe again fails as it cannot connect to DVB-T , hence "Connection Dropped". Plugging-out and then Plugging-in DVB-T, or restarting windows disengages dvbt from old instance.

          I have now found correct method to stop fr24feed for windows, as shown in 3 green steps in sketch below. This method completely closes all components of fr24feed, and next start is trouble free.






          The

          Comment


          • #6
            Thank you guys for your sugestions but it still doesn't work for me

            Comment


            • #7
              (1) Which version of Windows you have (XP, Vista, 7, 8, or 10)?
              (2) Did you install dvb-t driver "zadig"?
              Download from http://zadig.akeo.ie/

              Comment


              • #8
                I have windows 10 and I installed zadig with success

                Comment


                • #9
                  Do you have another DVB-T?
                  If you have another one, change the DVB-T, and try.

                  Comment


                  • #10
                    There appears to be no sign in the logs of a DVBT device being found.

                    I would check device manager as it doesn't look like the correct mode/zadig has installed properly
                    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                    Comment


                    • #11
                      I've tried running dump1090 by itself and got this
                      Found 2 device(s):
                      0: T■, ╕■, SN: (currently selected)
                      1: Realtek, RTL2838UHIDIR, SN: 00000001
                      usb_open error -12
                      Error opening the RTLSDR device: No error

                      And i've tried with rtl1090 without any problems. Can i give rtl1090's data to the feeder if dump1090 doesn't work ?

                      Comment


                      • #12
                        When you say dump1090 by itself you mean the MR version with the FR24 install?

                        If that is the case, being a new device its possible the SDR libs don't recognise the stick where RTL1090 calls can.

                        Be sure to check all the RTL-SDR libs are up to date. Or try the standalone dump1090 releases.


                        You can pass RTL to it, but not recommended as I believe RTL does its own optimizations on data (long timeouts and such) which can produce funky data that FR24 doesn't like.

                        /edit removed raspberry pi bits once realised this is windows.
                        Last edited by Oblivian; 2017-07-13, 06:36.
                        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                        Comment


                        • #13
                          Do I update the libraries by putting the rtl1090 dlls into the feeder folder ?

                          If so, I tried that as well and didn't work and tried the other version of dump1090 and still didn't work

                          Got dump1090 working after putting this into the .bat file
                          --device-index 1
                          Put this into the "Process arguments" settings

                          Thank you guys for your help
                          Last edited by FaZeBasescu; 2017-07-13, 15:09. Reason: dump1090 fixed + argument on feeder

                          Comment

                          Working...
                          X