There's a possible bug in the Hound moving logic where TX3 gets shifted.
Shouldn't the m_nFoxFreq>600 be n_nFoxFreq>900??
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);
In addition I'd like to propose a new logic for the Fox/Hound slot management
something like this.
Fox Tx on 300Fox managed slots at 360.420,.480,540,600Hound managed slots
660,720,780,840,900
Fox will rotate through slots as calls are worked. So on single slot for
example they work on 360, then 420, then 480, etc.Fox slots could be randomized
too.This minimizes the chance of any collision from Hounds still trying to
transmit on their original offset.
Once the Hound decides to switch offset for Tx3 it randomly picks one of the
Hound managed slots on every transmission.This keeps all the people that keep
on transmitting Tx3 in their own netherworld with a 4/5 chance of not
transmitting over the top of somebody.
de Mike W9MDB
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
