It would be useful if the rtlsdr version could select by device number.

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.

action-rs is unmaintained

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!

https://github.com/cross-rs/cross/releases/tag/v0.2.5

Hello

I'm trying to use a RSP2Duo without success 5I'm able to see around 30 planes using an oldest dump1090)

No ioda about the parameter I should use ....

I've not more text than this one ...

[-] read in custom config: /home/pi/config.toml
[-] using soapysdr driver: driver=sdrplay
[INFO] devIdx: 0
[INFO] SerNo: 1708004110
[INFO] hwVer: 2
[INFO] rspDuoMode: 0
[INFO] tuner: 1
[INFO] rspDuoSampleFreq: 0.000000
[-] using config: Sdr {
channel: 0,
driver: "sdrplay",
setting: None,
gain: [
Gain {
key: "LNA",
value: 0.0,
},
Gain {
key: "VGA",
value: 0.0,
},
],
antenna: None,
}
[-] Writing gain: LNA = 0
[-] Writing gain: VGA = 0
[-] frequency: Ok(1090000000.0)
[-] sample rate: Ok(2400000.0)
[INFO] Using format CS16.

PlutoSDR works with uri parameter set correctly for soapySDR (ip:192.168.2.1 is a good default guess). Tested with gain 24, but unsure of ideal default value.

Hi all, the only way to dump1090_rs detect the SDR is running as root. Is there a way to run as a normal user?

this would allows cross-sdr support, for example hackRF.

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?

Hi,

I'm trying to run dump1090_rs on a nuc which has multiple rtlsdr connected. AFAICT it should be possible (after using rtl_eeprom to program a different serial number per rtlsdr) to tell SoapySDR which one should be used by appending ,serial=XXXXXXXX to the driver argument.

SoapySDR seems to open the correct device, but dump1090_rs crashes, probably because it tries to lookup some additional options using the full name instead of only rtlsdr?

root@tv ~/src/dump1090_rs (git)-[master] # RUST_BACKTRACE=full cargo run -- --driver 'rtlsdr,serial=00001000'
    Finished dev [unoptimized + debuginfo] target(s) in 0.04s
     Running `target/debug/dump1090_rs --driver rtlsdr,serial=00001000`
[-] using soapysdr driver: driver=rtlsdr,serial=00001000
Found Rafael Micro R820T tuner
Detached kernel driver
Found Rafael Micro R820T tuner
Reattached kernel driver
[INFO] Opening Generic RTL2832U OEM :: 00001000...
Detached kernel driver
Found Rafael Micro R820T tuner
thread 'main' panicked at dump1090_rs/src/main.rs:119:9:
[-] selected --driver gain values not found in custom or default config
[backtrace removed]

I'd guess changing this line to split the options.driver on , before comparing could solve this. I don't know rust but this change seems to work for me:

    let checkdriver = options.driver.split(",").next().unwrap();

    // check if --driver exists in config, with selected driver
    let channel = if let Some(sdr) = config.sdrs.iter().find(|a| a.driver == checkdriver) {

I put this in the "discussion" section but on second thought maybe I should bring this up as an issue. The Rust version decodes less messages than the "normal" dump1090 (if such a thing exists). It documented this in my comparison write up:
Comparing rust version of dump1090 The traditional dump1090 decodes shorter messages.

Is anything useful not being decoded?

I find the rust version gets more position data which is the objective after all.

Hello, I'm using regular RTL-SDR V3 with a general-use LNA. But I'm not able to enable the bias-t when using dump1090_rs.

Is it supported?

• New Bytes
• CRC correction
• New client add/drop

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.

https://github.com/Swatinem/rust-cache

https://scuba.readthedocs.io/en/latest/