ppm still not working

[hb9eue]

I have read #7
Also using my fcdpp with OpenWebRX+

But setting a frequency offset is not the same as setting the ppm correction which is passed to soapy_connector with the -P parameter.

At the moment, I work around by setting a different offset on each profile, which is not always working as expected, especially if a user enters a frequency manually and the offset of the previous frequency is still set.

I hope that by setting a ppm oscillator correction the error would be compensated over the whole frequency range.

[phlash]

Hi @hb9eue, I have just read through the OpenWebRx current codebase to assure myself that setting a ppm correction should get passed through to the SoapyFCDPP driver from OpenWebRx, via the soapy_connector tool and it's -P option as you mention.

You can check that the SoapyFCDPP driver is receiving the ppm option by running soapy_connector manually with the SoapySDR debug enabled, eg:

% SOAPY_SDR_LOG_LEVEL=DEBUG soapy_connector -d driver=fcdpp -s 192000 -f 100000000 -P 333

which should show:

[DEBUG] setFreqCorrection 333

amongst other messages. If that doesn't appear, try again at TRACE log level (SOAPY_SDR_LOG_LEVEL=TRACE) and let us know what you are seeing..