N0AN reported problems with using tuning with WSPR hopping. I've confirmed
some bad behavior.
First off, he (and I) believe one should tune on Rx-only also. So this small
patch enables that so any band change causes tuning (or should)
Should this be another option?
Index: WSPRBandHopping.cpp
===================================================================
--- WSPRBandHopping.cpp (revision 7185)
+++ WSPRBandHopping.cpp (working copy)
@@ -425,8 +425,8 @@
, frequencies_index
, frequencies_index >= 0 // new band
- && tx_enabled // transmit is allowed
- && !tx_next // not going to Tx anyway
+ //&& tx_enabled // transmit is allowed
+ //&& !tx_next // not going to Tx anyway
&& m_->bands_[4].testBit (band_index) // tune up required
&& !m_->bands_[5].testBit (band_index) // not an Rx only band
Secondy there are times when Tuning and/or band change doesn't occur. In my
setup I notice it regularly when it goes from 160M to 80M. I added some
messages to the window to help see a bit better what's going on. With these
messages enabled I see, for example, that after 160M receive it changes band
but doesn't think tuning is required. It does this every cycle so is very
repeatable.
| 1320 ---------------------- Receiving WSPR ----------------------- 160m |
| Band changed |
| Freq changed |
| tune_required=no |
| 1322 ----------------------- Receiving WSPR ----------------------- 80m |
| Band changed |
| Freq changed |
| tune_required=yes |
| Tune Started |
And here's another which repeats regularly too...20M to 17M thinks no tuning is
required.
| ------------------------------------------------------------------- 30m |
| 1328 -8 0.6 10.140175 -2 WA4KFZ FM18 37 756 |
| 1328 -23 -1.9 10.140214 -3 K3XR FN10 37 745 |
| Band changed |
| Freq changed |
| tune_required=yes |
| Tune Started |
| ------------------------------------------------------------------- 20m |
| 1330 -27 0.1 14.097177 -1 K7GXB DM34 30 1261 |
| Band changed |
| Freq changed |
| tune_required=no |
|
|
Index: mainwindow.cpp
===================================================================
--- mainwindow.cpp (revision 7185)
+++ mainwindow.cpp (working copy)
@@ -4552,6 +4551,9 @@
void MainWindow::band_changed (Frequency f)
{
if (m_bandEdited) {
+ if(m_mode.startsWith ("WSPR")) {
+ ui->decodedTextBrowser->appendText("Band changed");
+ }
if (!m_mode.startsWith ("WSPR")) { // band hopping preserves auto Tx
if (f + m_wideGraph->nStartFreq () > m_freqNominal +
ui->TxFreqSpinBox->value ()
|| f + m_wideGraph->nStartFreq () + m_wideGraph->fSpan () <=
@@ -4578,6 +4580,7 @@
m_freqNominal = f;
m_freqTxNominal = m_freqNominal;
if (m_astroWidget) m_astroWidget->nominal_frequency (m_freqNominal,
m_freqTxNominal);
+ ui->decodedTextBrowser->appendText("Freq changed");
setRig ();
setXIT (ui->TxFreqSpinBox->value ());
}
@@ -5709,8 +5712,12 @@
// Produce a short tuneup signal
m_tuneup = false;
+ QString foobar = "no";
+ if (hop_data.tune_required_) foobar = "yes";
+ ui->decodedTextBrowser->appendText("tune_required="+foobar);
if (hop_data.tune_required_) {
m_tuneup = true;
+ ui->decodedTextBrowser->appendText("Tune Started");
on_tuneButton_clicked (true);
tuneATU_Timer.start (2500);
}
I'm running with this schedule
de Mike W9MDB
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
