Closed ghost closed 4 years ago
This is an error with the device or the libraries, there's nothing I can do to prevent this. The rtl_connector
simply calls the rtlsdr_set_center_freq()
method. Oddly enough, it doesn't even seem to return an error code to the application, if it did you should see a message "WARNING: setting center_freq failed: " with an error code.
I'll admit there's no other error handling in place, but without any error returned from the library, I'm in no position to address this in any way.
Yeah, no Warning comes back. It's easy enough to work around. Does this only impact rtlsdrs? I think I'm going to step up to an AirSpy Mini in the near term as I like to use openwebrx to "browse" the airwaves and I think I'd like the wider view I could get with an AirSpy. And there's also the whole stuck in the house from the virus thing which means I'm using this more.
I'd guess it's more hardware related. I just tried to setup hi/low profiles on the 2m range that only differ in the frequency like that:
"2mhi": {
"name": "2m oben",
"center_freq": 145500000,
"rf_gain": 30,
"samp_rate": 1000000,
"start_freq": 145725000,
"start_mod": "nfm",
"lfo_offset": 0,
"bias_tee": False,
},
"2mlow": {
"name": "2m unten",
"center_freq": 144500000,
"rf_gain": 30,
"samp_rate": 1000000,
"start_freq": 145725000,
"start_mod": "nfm",
"lfo_offset": 0,
"bias_tee": False,
},
that config works fine for me, no errors on the log either.
It might as well be a failure in librtlsdr. This may be an error that has been adressed in recent versions, I wouldn't know, unfortunately.
Thank you!
I'll close this up and bang on the config a bit more later and see if I can figure out anything with it. It's easy enough to work around for now and I may end up moving to a different SDR in the future anyway.
Good day
So I've found that when I'm changing frequency settings with my rtl-sdr without changing sampling rate or perhaps the direct sampling flag, I get:
This results in openwebrx silently loading the gui of the new frequency, but the sdr and the waterfall are actually still displaying the original frequency. This confused me for example when switching to my local fire department dispatch frequency and hearing the ham bands.
Now if i change the settings to something which uses direct sampling or a different sample rate, this appears to cause the sdr to "reload" properly and then it works fine.
So here is an example of my config (and I have this issue using rtl_sdr or rtl_sdr_soapy). If I go from 2M-High to 2M-Low, I get the error above. If I switch from 2M-High to say, 40M, it re-initalizes properly. If I then go from 40M to 2M-Low it also re-initializes fine. So the work around is basically, flip to 40M, and then flip back to 2M-Low. That works fine. But going from 2M-High to 2-M-Low or to 70cm doesn't change the center frequency.
Here's the SDR section of my config if that helps.
This is the latest docker image, c45e74d85bc0.