Thanks. I understand that the actual RF bandwidth is a driver setting.

However, I think exposing it as an optional setting in an OpenWebRX SDR profile would still be useful. OpenWebRX already changes parameters such as sample rate when switching profiles, and could simply call the driver's setBandwidth() as part of the profile setup.

Automatically coupling RF bandwidth to sample rate inside the driver would be one possible solution, but it would be less flexible, since RF bandwidth does not necessarily have to equal the sample rate.

Hello,

is this the right place to post feature requests?

I have a new PlutoSky R2 (AD9361) and noticed that when switching between OpenWebRX profiles with different sample rates, the AD9361 rf_bandwidth setting does not change.

It would be useful to have an RF bandwidth setting per profile, similar to the sample rate setting.

For example:

• 1 MS/s profile → 1 MHz RF bandwidth
• 4 MS/s profile → 4 MHz RF bandwidth
• 10 MS/s profile → 10 MHz RF bandwidth

Currently, if rf_bandwidth is set to 1 MHz and I switch to a 4 MS/s profile, it remains at 1 MHz, so the analog RX bandwidth is much narrower than the sampled spectrum.

Ideally, the profile could contain a configurable rf_bandwidth value which is passed to SoapySDR using setBandwidth().

For example, on the AD9361 the current RX RF bandwidth can be read with:

iio_attr -u ip:192.168.20.70 -i -c ad9361-phy voltage0 rf_bandwidth

and it can be changed independently of the sample rate, for example:

iio_attr -u ip:192.168.20.70 -i -c ad9361-phy voltage0 rf_bandwidth 4000000

This would set the RF bandwidth to 4 MHz, which would be useful for an OpenWebRX profile using a 4 MS/s sample rate.

The AD9361 in my PlutoSky R2 supports RX RF bandwidth values up to 56 MHz.

Thanks!