Joe, Eric, Bill,
I can reproduce similar behavior as follows. I am using a TS-480.

Let 0:00 (m:ss) be the beginning of a cycle.
Start the program (i.e. issue the command ./wsjtx) some time after 1:00. 
Some time between 1:00 and 1:30, press Tune, then press Tune again.
Some time after 1:30, do Tx Enable.

PTT will engage, no tones will be emitted. PTT will stay engaged until 2:00. 

I tried this twice just now, following the steps described above, and both 
times it dropped PTT at 2:00. But in earlier revisions I have seen PTT stay 
engaged beyond 2:00. In fact, I believe that I described this behavior in an 
earlier post. 

It seems possible that, for me, the PTT persisting beyond 2:00 behavior might 
have been fixed since my first report, since I was not able to reproduce that 
behavior today.

In any case, this seems like undesirable behavior.  I don’t know if 
user_hardware can be called between 1:50-2:00 but, if it can, then this 
behavior could cause carrier-less (i.e. no-tones present) hot switching.

Steve k9an 

> On Jun 10, 2015, at 8:10 PM, Joe Taylor <j...@princeton.edu> wrote:
> 
> Hi Eric,
> 
> On 6/10/2015 6:49 PM, Eric NO3M wrote:
>> Having problems with WSPR2 TX here.
>> 
>> WSJTX 1.6.0-devel r5578 (same problems with r5567 also before doing SVN
>> update/re-compile)
>> Band: 630m
>> Tx 1575 Hz
>> Tx Pct 33%
>> Upload Spots = true
>> Band Hopping = false
>> 
>> As soon as I click Tx Enable, regardless of how far into a 2-minute
>> period it is clicked, WSJTX immediately starts transmitting the WSPR
>> message.
> 
> Try as I will, I cannot reproduce the behavior you describe.
> 
> When I start WSJT-X in WSPR-2 mode and click Tx Enable, the program 
> politely waits for the start of an even-numbered minute.  It then begins 
> a normal cycle.  This cycle ends at the normally expected time, 54 
> seconds into an odd-numbered minute.
> 
> If I start the program, toggle Tx Next to ON, and then click Tx Enable, 
> the behavior is the same except that the first full 2-minute sequence is 
> Tx rather than Rx.
> 
> I am presently baffled by your report.
> 
>       -- 73, Joe, K1JT
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to