Michal Krenek (Mikos)

Hmm, maybe there is some incompatibility with latest PotosSDR bundle. I will try it and release new version if this is the cause.

@jfitter I should have finally time to work on QSpectrumAnalyzer again. I will try to look at it on weekend and release new version which should hopefully work on Windows...

Hello, what does `soapy_power --detect` and `soapy_power -d driver=rtlsdr --info` show? If CubicSDR works, soapy_power should work too (both use SoapySDR driver framework). Can you also try running `soapy_power -d...

Also make sure that you have specified `driver=rtlsdr` in QSpectrumAnalyzer settings (if not specified, audio driver is used by default on Windows).

You should not add `driver=rtlsdr` to *Additional parameters* box, but to *Device* box. If you click on **?** button besides *Device* box, it will show you all detected devices (same...

Btw. how did you installed QSpectrumAnalyzer / soapy_power? With installer or manually with `pip`?

@gioreva it is still the same, dBm unit has been changed to dB because it could be misleading (without calibration, you can't be sure about the absolute value in dBm).

It has been HackRF people who changed dBm label to dB label, see commit https://github.com/xmikos/qspectrumanalyzer/commit/70b921992764ca8988564001d49041bf2f5e1594: > **Changed labels from dBm to dB.** > hackrf_sweep outputs dBFS, but rtl_power outputs dB...

I am sorry, I do not understand what you mean by "menage Output"? I can describe you what exactly is soapy_power backend doing: 1. tune to center frequency for given...

In general, you can look at `soapy_power --help` to see what each option does. Or click to **?** button besides *Additional parameters* box in QSpectrumAnalyzer settings (it will also show...