Was working with someone trying the VP8PJ dxpedition and he had a problem that
I think needs fixing.
He was pulled down by Fox to 346 and lost the path so got bumped to 646 and
continued to transmit until timed out. He then went 1000 and continued TX3
which then immediately bumped back down to 646 which he though meant the Fox
saw him.
It's this section of code....
if (m_nSentFoxRrpt==2 and m_ntx==3) { // move off the
original Fox frequency on subsequent tries of Tx3 int
nfreq=m_nFoxFreq + 300; if(m_nFoxFreq>600) nfreq=m_nFoxFreq - 300;
//keep nfreq below 900 Hz ui->TxFreqSpinBox->setValue(nfreq);
}
Maybe we need to add a check for TxFreqSpinBox > 999 and either disallow
anything but TX1 or if we want we to let TX3 continue (will Fox decode that?)
then we need to leave the frequency alone.
On a side note...I fully believe that we need to disable anybody transmitting
to Fox unless they've decoded them at least once (and decoded them recently
too...maybe a 5-minute timeout or less). We're seeing people blind calling and
calling incessantly that don't understand they should not be transmitting until
they see the DXpedition.
de Mike W9MDB_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
