gqrx-sdr / gqrx

Software defined radio receiver powered by GNU Radio and Qt.
http://gqrx.dk
GNU General Public License v3.0
3.12k stars 546 forks source link

Crash when using bladeRF #177

Closed andrepuschmann closed 10 years ago

andrepuschmann commented 10 years ago

Hi, I just discovered that the current git version crashed when connected to a bladeRF. During initialization gqrx tries to set the "IF" gain which is not supported by gr-osmosdr/bladerf. There is probably something going wrong when requesting the available gain stages from the device/lib.

Thanks Andre

./gqrx gr-osmosdr v0.1.1-9-gc65d205d (0.1.2git) gnuradio v3.7.4git-97-ge235ed3e built-in source types: file fcd rtl rtl_tcp bladerf rfspace Using Volk machine: sse4_a_64 Could not resolve property : pattern10600 Could not resolve property : pattern10600 Could not resolve property : pattern10600 Could not resolve property : pattern10600 Could not resolve property : pattern10600 Could not resolve property : pattern10600 Could not resolve property : pattern10600 Could not resolve property : pattern10600 gr-osmosdr v0.1.1-9-gc65d205d (0.1.2git) gnuradio v3.7.4git-97-ge235ed3e built-in source types: file fcd rtl rtl_tcp bladerf rfspace [bladeRF source] Using nuand LLC bladeRF #0 SN 4e4f...5000 FW v1.6.1 FPGA v0.0.3 [INFO] Clamping bandwidth to 1500000 Hz terminate called after throwing an instance of 'std::runtime_error' what(): set_gain requested to set the gain of an unknown gain element IF Aborted

csete commented 10 years ago

Does this happen with a new configuration or a configuration originally created for another device that has IF gain?

andrepuschmann commented 10 years ago

I've used a rtl-sdr before. So the config was with IF gain, yes. After deleting ~/.config/gqrx everything worked fine with the bladerf too. So the problem seems to occur when a non IF-gain device is used after an IF-gain device. The other way around seems to work, i.e. using the rtl after the blade.

csete commented 10 years ago

Yes, however, it applies to any gain setting, not just IF. It is a known issue, see: #125 I'm closing this as duplicate.