This issue is opened from a request received to implement frequency tracking for QO-100 based on its BPSK beacon similarly to what has been implemented in SDR Console.
In SDRangel things wotk a bit differently. Firstly I don't think I will implement something specific to QO-100 BPSK beacon. In the Channel Analyzer there is already a FLL and PLL lock for BPSK, QPSK, 8-PSK etc... (any "2^n-ary" PSK) that can be reused. Secondly I will not implement a direct control of the center frequency but rather use an external control program via REST API.
The Frequency Tracker channel plugin will simply adjust its own center frequency by locking it to a CW or FM carrier (FLL) or m-ary PSK (PLL). Then its center frequency (its shift and the device center frequency) can be communicated via reverse API to the control program that feeds back its control to registered channels. The channels controlled by the external program are just the ones that contact it via reverse API. Thus when the user sets the channel center frequency (shift) this takes precedence on the drift control.
f4exb
commented
5 years ago
This issue is opened from a request received to implement frequency tracking for QO-100 based on its BPSK beacon similarly to what has been implemented in SDR Console.
In SDRangel things wotk a bit differently. Firstly I don't think I will implement something specific to QO-100 BPSK beacon. In the Channel Analyzer there is already a FLL and PLL lock for BPSK, QPSK, 8-PSK etc... (any "2^n-ary" PSK) that can be reused. Secondly I will not implement a direct control of the center frequency but rather use an external control program via REST API.
The Frequency Tracker channel plugin will simply adjust its own center frequency by locking it to a CW or FM carrier (FLL) or m-ary PSK (PLL). Then its center frequency (its shift and the device center frequency) can be communicated via reverse API to the control program that feeds back its control to registered channels. The channels controlled by the external program are just the ones that contact it via reverse API. Thus when the user sets the channel center frequency (shift) this takes precedence on the drift control.