On 2nd thought I think this line#1834 may have been hosed and is the cause..
double tx2=txDuration + + icw[0]*2560.0/48000.0; //Full length
including CW ID
>From the wsjtx tree
double tx2=1.0 + 85.0*m_nsps/12000.0 + icw[0]*2560.0/48000.0;
73
Mike W9MDB
From: Michael Black [mailto:[email protected]]
Sent: Saturday, May 23, 2015 9:13 AM
To: [email protected]
Subject: 1.6.1 transmit start time
I've noticed the 25-second limit on when one can start a transmit and has
been removed?
I actually found it convenient at times to queue up a transmit.
I think this line may be causing it..
m_bTxTime = (t2p >= tx1) and (t2p < tx2); // For all modes other than
WSPR
Sets it to true and the time check a few lines later doesn't matter.
Perhaps that should just be
m_bTxTime = false;
Since it appears all other modes do their own checking later on.
Or.you need an else clause on subsequent checks to set it to false.
Mike W9MDB
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
