Hi Bill,
> Perhaps we should be doing the same as for WSPR with the fast modes i.e.
> turning off split on the rig. It looks like you have already added some
> of the relevant code in r5774 assuming that
> MainWindow::fast_config(true) is being called appropriately.
I had previously thought this would be a good idea, but now when trying
to implement automatic rig control for handling the "CQ nnn ... "
protocol I think we need to keep the split capability, at least in JTMSK
mode.
As of ~r5883 JTMSK has a (largely untested) feature designed to promote
the use of a "calling frequency" for meteor scatter. Transmissions of
the form
CQ 265 K1ABC FN42
signify that K1ABC will listen for replies on 50.265 (or 144.265, or
whatever) and will then complete the QSO with a responder on that
frequency.
I imagine this feature to be used as follows:
1. On startup, select JTMSK mode and 50.280 (the calling frequency) from
the drop-down band menu.
2. Check the unlabeled box just under the Report spinner to activate the
"CQ Rx nnn" spinner. Set this spinner to, say 265.
3. Note that your transceiver dial frequency should now be 50.265. Any
changes to the "CQ Rx nnn" spinner value should immediately be reflected
in the dial frequency and also in Tx message #6, the
"CQ nnn... " message.
4. If you transmit the Tx6 message, the Tx frequency will be set at the
calling frequency. Otherwise (when receiving, or when transmitting any
of the messages Tx1 through Tx5) the offset frequency (e.g. 50.265) will
be used.
5. If you double-click on a received "CQ nnn ..." message on the calling
frequency, your rig will QSY to specified response frequency, e.g.
50.nnn, for both Rx and Tx.
-- Joe
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
