I'm unable to select a remote device using SoapySDR's driver syntax, even thought SoapySDRUtil can find it:

$ SoapySDRUtil --find="driver=remote, remote=192.168.1.184, remote:driver=rtlsdr"
######################################################
##     Soapy SDR -- the SDR abstraction library     ##
######################################################

Found device 0
  available = Yes
  driver = remote
  label = Generic RTL2832U OEM :: 
  manufacturer = Realtek
  product = RTL2838UHIDIR
  remote = tcp://192.168.1.184:55132
  remote:driver = rtlsdr
  rtl = 0
  serial = 
  tuner = Elonics E4000


$ dump1090 --driver "driver=remote, remote=192.168.1.184, remote:driver=rtlsdr"
[-] using driver: driver=remote, remote=192.168.1.184, remote:driver=rtlsdr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { code: Other, message: "SoapySDR::Device::make() no match" }', dump1090_rs/src/main.rs:81:75
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

There aren't any examples, really for doing this type of connectivity with the code, but it seems like it should work as other applications (CubicSDR, for example) can use the same remote sdr source just fine. It's most likely something to do with the driver selection in the command line, but without any good docks here, i'm just trying various combinations and still getting nowhere.

Hi,

Thanks for the project! I am using dump1090_rs with my USRP B210 which has two antennas per frontend. Right now it does not appear to be possible to select which antenna to use, which is a bit annoying for my use case.

It appears it might be settable using soapysdr::Device::set_antenna.

Would you consider adding support for setting the antenna via e.g. command line options?

• Add support for building aarm64-unknown-linux-gnu for supporting the Raspberry Pi 64-bit
• Add new CI images that are pushed to docker hub
• update cargo/cross base images -> 0.2.2

Add ability to change settings for an sdr device. This is achieved by using [[sdr.setting]] in a config.toml file. This uses write_setting and read_setting provided by soapysdr.

Updated --help text to show string without newlines all over

Patch soapysdr-rs to my own branch until this is published or in soapysdr-rs master.

Use key/value for all Args.

Closes #16

running dump1090 as myself I get

usb_open error -3
Please fix the device permissions, e.g. by installing the udev rules file rtl-sdr.rules
Error: "Expected result code of zero"

Though running sudo dump1090 works fine, it'd be good to play by the rules. Google cannot point me to a definitive answer. Please consider an example .rules file and a sentence or two on how to install it.

I'm enjoying this project as a fellow rustacean who lives under the flightpath from LHR. I can now put my SDR to useful work. Kudos!

CPU's love him, with these 3 commits.

This mostly just make the slices used by calculate_bit and check_preamble limited by the biggest len needed by the function instead of boundless.

I'm working on getting dump190_rs and radar running using SoapySDR remote with an Airspy. It seems to be running, but I'm not actually seeing any airplanes in radar and using netcat to connect to port 30002 shows no output. Airspy has three gain controls: LNA gain range: [0, 15] dB MIX gain range: [0, 15] dB VGA gain range: [0, 15] dB

My questions:

1. Ignore this question - I see now in the config.toml how each of the gains can be set - sorry It seems I can only specify one gain key in the custom-config file unless I'm missing something?
2. While dump1090_rs is running, it prints a steady stream of characters (mostly 'S', some '0') to stdout. Is that expected? Do the characters mean anything?

Thanks for these projects - I was very happy to find an ads-b project that supports remote hw as my sdr and antenna are located in a barn away from the e noise of my house.