[wsjt-devel] "Tune" prevents "Tx Next" from transmitting in next cycle

[Gene H <gh...@gm...>]

*
*
*Re: [wsjt-devel] "Tune" prevents "Tx Next" from transmitting in next 
cycle <https://sourceforge.net/p/wsjt/mailman/message/37125357/>*
From: Gene <ghinkle@gm...> - 2020-10-09 13:37:19

In my message referenced above, I noted the lack of transmit during the 
next transmit cycle after a Tune was made.

Today, I realized that this only occurs if the *Tune *button is toggled, 
meaning click once to put transmitter in tune state and then click again 
to take the transmitter out of tune state. If I were to then put WSJT -X 
FT8 in*Enable Tx* button the next cycle is always skipped for either 
making a call or calling someone from their CQ.

However, today I realized if instead of clicking *Tune *button to tune 
and the *Tune *to stop tuning _but instead_ click *Tune *button to tune 
and then *Halt Tx* to stop tuning all works as I would expect!

I assume clicking *Tune *twice should be okay and result in proper 
operation which it does not. However, my work around is to click *Tune 
*once then*Halt Tx* so all is well.

_Question_, is this being addressed in the upcoming v2.3.0-rc2 release?

Hope this helps,

73, Gene, K5PA

WSJT-X Version: v2.3.0-rc1,

64-bit, Windows-10 O/S

----------------------------

On 10/9/2020 8:36 AM, Gene wrote:
> Thanks to Wernli's message 2020-10-08 I was able to better document a 
> bug in the way WSJT-X in FT8 inhibits the next cycle transmission 
> including the *CQ* message *Tx 6* (*Next *or *Now *buttons). I noticed 
> many times when calling a station, my transmitter would not transmit 
> on the next cycle. I have now related it to the use of the *TUNE 
> *button prior to selecting a station to call. This also happens when 
> using *TUNE *and then Calling CQ via the*Tx 6* message, both *NEXT 
> *and *NOW* buttons.
>
> I regularly use the TUNE button when changing bands to tune a remote 
> tuner and have found it is not related to changing the bands in WSJT-X 
> but rather using the TUNE button.
>
> To reproduce:
> - Select FT8 mode
> - Press and release "Tune"
> - Activate *Tx 6* message that displays "*CQ* *callsign grid*" and 
> then click either "*Next*" *or* "*Now*"
> -> It will not transmit in the immediate transmit cycle and has to 
> wait a cycle prior to initiating the CQ.
>
> I am using WSJT-X v2.3.0-rc1, Windows 10, 64-bit O/S.
>
> Hope this helps and can be fixed in the next -rc release.
>
> Thank you,
> Gene, K5PA
>
> On Thu, Oct 8, 2020 at 5:06 PM Stefan Wernli <hb...@gm... 
> <mailto:hb...@gm...>> wrote:
>
>     Hi,
>
>     Albrecht pointed earlier to the behavior that "Tx Next" doesn't always
>     transmit in the next cycle.
>
>     I noticed that this reproducibly happens, if the "Tune" button was
>     used;
>     Using the "Tune" button in WSPR- or FST4W-modes prevents from
>     transmitting in the follwing cylcle, even if "Tx Next" is activated.
>
>     To reproduce:
>     - Select WSPR or FST4W-mode
>     - Press and release "Tune"
>     - Activate "Enable Tx" and "Tx Next"
>     -> It will not transmit in the next cycle
>
>
>     It would be good if this could be fixed.
>
>     Thanks and 73
>     Stefan
>
>
>     _______________________________________________
>     wsjt-devel mailing list
>     wsj...@li...
>     <mailto:wsj...@li...>
>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>     <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
>
>
>
> -- 
> Gene Hinkle
>
-- 
Gene Hinkle
2209 Pow Wow, Leander, TX 78641
e-mail to Gene:  gh...@gm...
cell phone or text messaging:  (512) 413-9251
--