Announcement

Collapse
No announcement yet.

Windows 10 DVB-T device is not recognized properly.

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Windows 10 DVB-T device is not recognized properly.

    Hello everyone,

    Sorry if the same problem is posted again but I've been looking at numerous posts and can't find something to work for me.

    So, I have shared my data some years ago with the same PC and usb stick running windows 7 and everything worked fine. The dvb-t dongle works and it can receive 1090mhz signals. My problem is that mr-dump1090.exe cannot find the device (or so I think). When I open fr24feed.exe, the connection gets terminated:

    [main][i]FR24 Feeder/Decoder
    [main][i]Version: 1.0.19-15/generic
    [main][i]Built on Feb 6 2018 10:20:41 (???/Windows/i386)
    [main][i]Running on: Windows10.0
    [main][i]Local IP(s):
    [main][i]Copyright 2012-2018 Flightradar24 AB
    [main][i]htt...flightradar24com
    [main][i]Reader thread started
    [time][i]Synchronizing time via NTP
    [master][i]Starting processing thread
    [reader][i]Initializing reader
    [httpd][i]Server started, listening on 0.0.0.0:8754
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --net --deviceindex 1 --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [time][i]Time synchronized correctly, offset -2.0430 seconds
    [main][i]Feed Network client started
    [feed][i]Downloading configuration
    [feed][c]Interval: 5s
    [feed][c]Latitude: **.****
    [feed][c]Longitude: **.****
    [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 4 servers
    [stats][i]Stats thread started
    [feed][n]LGIO4@***.***.***.***:****/UDP
    [feed][n]connecting
    [feed][n]connected via UDP (fd 972)
    [feed][n]working
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --net --deviceindex 1 --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 --net --deviceindex 1 --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated


    When I open mr-dump1090.exe, it closes instantly so i open it via powershell:

    PS E:\Program Files (x86)\Flightradar24Feeder\fr24feed_win32> ./mr-dump1090
    -----------------------------------------------------------------------------
    | dump1090 ModeS Receiver Ver : 1.10.3010.14 |
    -----------------------------------------------------------------------------

    Copyright (C) 2012 by Salvatore Sanfilippo <antirm>
    Copyright (C) 2014 by Malcolm Robb <suppcom>

    All rights reserved.

    THIS SOFTWARE ... SUCH DAMAGE.

    For further details refer to <https...dump1090>

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


    What I understand is that there should be Realtelk instead of ROOF1 but I don't know what to do to fix it. I have installed WinUSB drivers through zadig at Bulk-In Interface 0 and 1. Can anybody help me?

    Thanks.
    Tags: None
  • #2
    This:

    exe://mr-dump1090.exe --net --deviceindex 1 --raw

    Relates to this:

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

    If you run Dump1090 on its own to test. You need to run the same deviceindex command at the end the same to select the right 'roof roof' device to see if it is actually a USB SDR stick being detected.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment

    • #3
      Originally posted by Oblivian View Post
      This:

      exe://mr-dump1090.exe --net --deviceindex 1 --raw

      Relates to this:

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

      If you run Dump1090 on its own to test. You need to run the same deviceindex command at the end the same to select the right 'roof roof' device to see if it is actually a USB SDR stick being detected.
      Thanks for the answer Oblivian. I also tested this but forgot to mention. It looks like it detects it but now it gives another error:

      PS E:\Program Files (x86)\Flightradar24Feeder\fr24feed_win32> ./mr-dump1090 --net --device-index 1 --raw
      Found 2 device(s):
      0: , , SN: <=>?∙
      1: ROOF1, ROOF1, SN:

      Using device 1: Generic RTL2832U OEM
      -----------------------------------------------------------------------------
      | dump1090 ModeS Receiver Ver : 1.10.3010.14 |
      -----------------------------------------------------------------------------

      Copyright (C) 2012 by Salvatore Sanfilippo <antirez@gmail.com>
      Copyright (C) 2014 by Malcolm Robb <support@attavionics.com>

      All rights reserved.

      THIS SOFTWARE... SUCH DAMAGE.

      For further details refer to <https...dump1090>

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

      Comment

      • #4
        Have exactly the same problem after updating Windows 7 to Windows 10.

        Have read probably all the article on the web regarding W10 installing down level drivers for DVB-T RTL2832U devices clearly there is a real issue for some dongles.

        PLEASE can someone recommend a dongle / ADS-B dedicated device that is GUARANTEED to serve FR24 from/on Windows 10.

        Comment

        • #5
          The 2nd portion of the driver (tuner) has probably been overwritten too now with an update

          W10 does driver updates regularly.

          Likely need to go into device manager and force the Zadig drivers on both branches that appear for tv sticks

          Or use the show all devices in zadig

          If it has given a driver to the tuner by w10. It won't appear to be able to update with zadig

          Zadig
          https://github.com/pbatard/libwdi/wiki/Zadig
          Windows Driver Installer library for USB devices . Contribute to pbatard/libwdi development by creating an account on GitHub.

          Sent from my EML-L09 using Tapatalk
          Last edited by Oblivian; 2018-12-08, 21:39.
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment

          • #6
            And this from 2017 tends to agree.

            Just a moment...
            https://www.rtl-sdr.com/forum/viewtopic.php?t=1797


            Remove both. Start the installer in manual

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

            Comment

            • #7
              Thanks - Zadig worked a treat.

              Had tried that before but maybe I screwed up somewhere?

              Will be interesting to see if W10 wants to overwrite the changes made by Zadig in the future.

              Comment

              • #8
                Bound to. This would be about the third time if effecting a few people all of a sudden.

                The last time overwhelmed the support desk that they made a 'fr24 and w10' sticky

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

                Comment

                • #9
                  "I removed the device and drivers from my desktop (with SDR plugged in...Device Manager, right-click device, Uninstall, check box to remove drivers). I then ran the Zadig installer, checked the entry for "List All Devices", then cleared the check for "Ignore Hubs or Composite Devices". I then located the RTLSDR???? (Composite) entry and installed the driver for this device only. Zadig installer prompted me that I was replacing a system driver, I accepted and closed the Zadig installer."

                  Thank you very much for sharing the information! This was indeed the solution. Looking forward to setup the antenna and have some better coverage.

                  Comment

                  Previous template Next
                  Working...
                  X

                  We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                  By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                  I Agree