GPS frequency correction not being applied if only kiwirecorder.py connections present
As part of investigations into the use of FST4W on the HF bands, in conjunction with WsprDaemon, we have come across an issue.
If kiwirecorder.py connections are the only ones to a KiwiSDR (tested with versions v1.498 and v1.554) then the GPS derived frequency corrections do not take place. Rather, the frequency drifts. The issue and a workaround are described in detail in the attached pdf.
Immediately on opening a browser connection to the Kiwi - it can be admin or a receiver channel - the GPS corrections resume. GPS corrections continue so long as the browser window is active. If it suspends then the corrections do not happen until it is reloaded.
This provides a workaround - keep a browser connection open to the Kiwi.
With this knowledge, we are reevaluating our previous measurements of spectral spread as they may have been influenced by unnoticed drift.