-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RTL-SDR] Support for more than one device #95
Comments
Can you explain your problem a little bit more in detail, please? welle.io runs with the zadig driver, see here: https://www.welle.io/devices/rtl_sdr |
I have a RTL2838 (R820T2, 0BDA 2838 01) stick, not RTL2832 and Zadig is installed, but welle.io say it doesn't exist a device for welle.io. welle.io
Info from Device Manager: In Qt-DAB I must select second entry in list. |
This seems to be the problem:
Could you reset the driver for Interface 0 or even install the old driver in Zadig? Not so for Interface 1, please leave it as it is. |
BTW: There is no RTL2838 at all ... |
I try to reset the driver. Edit 1: after resetting and installation for Interface 0:
Edit 2: after resetting and installation for Interface 1:
It seems, that only Interface 1 is working ☹ Ah, okay, a product name 🙂 |
Is your set up working now or do you still have issues? |
Alternative: use another stick, they are very cheap, 5 Euro should be enough for 2nd hand ones. |
It works only with Interface 1 not 0. I had a stick (RT820T) but I sell it ☹ Hmm, then I can't use this program then I can't choose Interface 1 😢😢😢 |
If you are able to recompile welle.io you can change this line in CRTL_SDR.spp from |
Thanks 🙂 😎 🤠 the stick is working now with Qt Creator 🙂 😎 😇 Is it possible to add a switch parameter to start with interface 1 or similar?
|
I still don't understand why you have two devices listed but I agree that an opportunity to select the device is useful. I added it to the task list. I recommend to start with a command line option first. In a second step some GUI functionality can be added. If you are a developer please take the job and send me a pull request! |
Thank you for your help 🙂 |
Great! I encourage you to learn C++ and than you can add a device index command line option for the rtl-sdr devices. |
One of my Sticks (E4000 tuner) also has two interfaces. |
Does somebody know why one dongle has two interfaces? Is this the case also under Linux? |
I'm very sorry, but C++ is a little to hard for me 😟 C# is a little easier, VB code is nothing for me 😂 I wish I could C++ 😇 I use VS 2017 Community and it's ok for small Windows programs or UWP... I have a "Windows Phone" and I created a simple and not finished app (UWP) and it works on PC and Phone 😂😂😂 Can you build a function to select the interface please? 😇😉 It's a good question why some sticks has two interfaces... |
I have no idea, but the E4000 PDF mentions PWM and i2C interface |
Hi. With Windows 10, one (1) RTL-SDR v3 stick and Zadig 2.3 my laptop also shows interface 0 and 1. SDR# and HDSDR aren't bothered, but Welle-io is. Nevertheless on the same laptop using "rtl_tcp -d 1" (interface 1) and "welle-io -D rtl_tcp" (rtl_tcp interface) it works just fine. The laptop played both French and Swiss stations during my vacation close to Geneva. Good job! |
Good news! The next top priority would be to implement the support of more than one interface. I also think the automatic selection of the interface can simply uses the rtl-sdr interface with the highest interface number. From all reports it seems that the highest interface number is the right one. What bothers me a lot is that I don't understand why the rtl-sdr driver reports two interface even there is only one connected. |
I can not recompile the file. how do you do that? Can not you equal the build of the file that set the same value to 1? |
In the meanwhile use another stick. Nowadays people are selling them for around 5 EUR |
The rtl-sdr driver interfaces are two bulk-in usb interfaces. One is the actual device and the other one is an interface for accessing the IR remote control part of the stick. It's probably a bit adventurous to assume something like "always use i/f 1 if it's rtl2832 based"... |
I think you should try and get in touch with other guys writing sdr utilities, and share knowledge and experience. |
Adimik, I have two different sticks, the RTL-SDR v3 that the guy at rtl-sdr.com sells and an astrometa dvb t2 stick, and both have the same problem with "the wrong interface". (One can't help but think of an Aardman animated film, "The Wrong Trousers"..) |
It seems that SDR# uses a modified librtlsdr library with IR support. Somebody can try to just copy the rtlsdr.dll from SDR# to welle.io. |
Please send me the ready-made file! I'm not a programmer and I do not have Linux.
Verzonden vanuit Mail voor Windows 10
Van: Albrecht Lohofener
Verzonden: vrijdag 4 augustus 2017 21:50
Aan: AlbrechtL/welle.io
CC: L Kuperij; Comment
Onderwerp: Re: [AlbrechtL/welle.io] [RTL-SDR] Support for more than one device(#95)
It seems that SDR# uses a modified librtlsdr library with IR support.
Somebody can try to just copy the rtlsdr.dll from SDR# to welle.io.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
It makes no difference if I use another rtlsdr.dll. It just does not work.
I can customize CRTL_SDR.cpp with notepad ++ but I can not compile it.
Verzonden vanuit Mail voor Windows 10
Van: Albrecht Lohofener
Verzonden: vrijdag 4 augustus 2017 21:50
Aan: AlbrechtL/welle.io
CC: L Kuperij; Comment
Onderwerp: Re: [AlbrechtL/welle.io] [RTL-SDR] Support for more than one device(#95)
It seems that SDR# uses a modified librtlsdr library with IR support.
Somebody can try to just copy the rtlsdr.dll from SDR# to welle.io.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I created a test version of welle.io with an improved auto selecting of rtl-sdr devices. It simply tries to open the first rtl-sdr device if it is not working then welle.io tries the next one and so on.
I tested it with the welle.io version V20170701. |
Thank you very much, now it works well. |
I commited the code (e656145). It will be included in the next official release. |
What is if user has more than one stick on PC? 😂 😉 |
An ideal receiver application should allow selecting the receiver via a
menu.
Hans J. Albertsson
From my Nexus 5
Den 12 aug. 2017 20:25 skrev "PadMan" <notifications@github.com>:
… What is if user has more than one stick on PC? 😂 😉
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#95 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_xuq7x3jeZCadJVjiWKgBKPmtt2MH9ks5sXe4fgaJpZM4OJcI2>
.
|
@HansJA Can you explain in detail the use case to use more than one device, please? |
I usually have two different sticks connected, a commercial dvb-t2 stick
and the rtl-sdr.
In the future I envisage running an Sdrplay rsp2 in parallell with at
least one stick.
The use case is not wanting to connect +disconnect just to try the other
receiver.
Hans J. Albertsson
From my Nexus 5
Den 13 aug. 2017 20:20 skrev "Albrecht Lohofener" <notifications@github.com
…:
@HansJA <https://github.com/hansja> Can you explain in detail the use
case to use more than one device, please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#95 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_xuuyWBrgBa6Y_k5wNU6G7-P7AraaLks5sXz5lgaJpZM4OJcI2>
.
|
welle.io sees only dab sticks with the zadig driver or the airspy driver. I suppose that your DVB-T2 stick and the sdrplay stick uses different drivers and thus it is not a big deal to use it in parallel. |
Hi, is still no device_index parameter available? like in the rtl_sdr tools:
best regards, |
OK guys. I reopen this issue to implement this feature in the future. It is not a really difficult task and with the version 2.0 it is easy to implement. But somebody has to do it. |
As a workaround, maybe you can try by using SoapySDR which, if I remember well, allows you to choose which device you want to use thanks to the ability to define driver arguments in welle.io (soapySDR support got some improvements in welle.io 2.1) BTW, I guess this can be done for now only on linux when using a distribution package (like on debian) with soapySdrRtl Driver installed, since I'm not sure that the windows package ships the soapyRtlSdr driver. |
A workaround is described here: #615 |
Is it possible to run welle.io with installed zadig driver instead original driver?
The text was updated successfully, but these errors were encountered: