On 11/09/2015 17:57, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
...
>> That probably requires m_bSimplex to be true, perhaps not the best name
>> for that variable and Configuration::transceiver_tx_frequency() to be
>> signalled when Configuration::transceiver_frequency() has been signalled
>> to set a new Rx frequency so that the Tx frequency is either the calling
>> frequency or the working frequency (zero could be used for the working
>> frequency as that will turn off SPLIT on the rig).
> So I guess I should set m_bSimplex = true for all fast modes and for
> WSPR, and false for all other slow modes? Or are there special cases to
> consider?
That sounds right so long as Doppler correction is not needed -
m_bSimplex also disables that.
You may have this correct already but when setting a split Tx frequency
the following sequence or an equivalent is necessary:
if (m_monitoring || m_transmitting) {
if (m_config.transceiver_online ()) {
if (m_config.split_mode ()) {
// All conditions are met, reset the transceiver dial frequency:
Q_EMIT m_config.transceiver_tx_frequency (desired_frequency);
}
}
}
otherwise an attempt to set split when it has been disabled may occur. I
assume that also means that you cannot enable the whole QSY from calling
frequency to working frequency facility unless
Configuration::split_mode() returns true. Of course "Fake" split mode is
Ok too but again the user must have configured it. The above checks
cover that.
>
> -- Joe, K1JT
73
Bill
G4WJS.
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
