Hi all. I have been running a basic Nooelec SDR and mini antenna for ages, not getting much more than about 12 miles of reception. I decided to finally upgrade to something a bit nicer.
I grabbed the rtl-sdr v4 dongle with their wideband LNA, a 1090 saw filter, and a nice AirNav antenna. I did a fresh install of PiAware, running on a good brand-name microSD, on my Pi 3 Model B.
PiAware loads and boots fine. Unfortunately, I am picking up zero signal. Even if I bypass the LNA and filter straight to the antenna, there’s nothing. Bias tee is enabled as far as I can tell. I edited the settings file to tell it the device type but that was all.
Pi shows the SDR connected when using the lsusb command:
pi@piaware:~ $ sudo rtl_test Found 1 device(s): 0: RTLSDRBlog, Blog V4, SN: 00000001 Using device 0: Generic RTL2832U OEM usb_claim_interface error -6 Failed to open rtlsdr device #0.
If I plug my Nooelec back in she fires right up and works fine.
All the articles I can find are for the model 3 SDR not the 4. I assume they’re similar enough, but is there something special I need to do? I’m using a proper power supply, everything boots and runs fine, I just don’t have signal. Any tips are appreciated!
Ok update: got it working. Had to follow this order of operations:
Flash new install of PiAware
Enable SSH on the Pi.
Edit config file by adding “receiver-type rtlsdr” and “rtlsdr-gain 10”. I also disabled WiFi because I’m hardwired and I’m working on the gain optimization procedure here Thoughts on optimizing gain
Put SD card in Pi and let it build
Use PuTTY to log into Pi and run the “Alternative Debian Package Installation Method” detailed here: RTL-SDR Blog V4 Users Guide
Ah - yeah, understand.
When the V4 was released, I compared the two. The V4 was not intended to replace the V3, but rather be a complimentary offering.
I don’t think Piaware is compatible with the RTL-SDR Blog v4, at least I did not see any annoucement saying so.
I have an RTL-SDR Blog v4, and for all the other software that I use it with, I had to install specific v4 add-ons or wait that the software added support for it.
It’s “claim to fame” is providing HF coverage without resorting to using only one of the I/Q branches like in v3. The latter kind of worked but left a lot to be desired performance wise.
It does add a few other things as well, but the “native” HF coverage is the main thing.
Yes, had to load the V4 drivers, in the order I did it in the post above. Works fine. New rig doubled the output I was seeing previously with the old setup.
Thank you for this guide! I didn’t realize I had to go through the “Alternative Debian Package Installation Method”. It immediately worked for me after I went through those steps.