Hi Laurence, Thanks for your detailed report. I believe this is enough information for me to be pretty certain about what the bugs are that cause these behaviors. Internally, the code couples the Tx period planning & override-like behavior for Tune/Tx Next through a few different variables and layers.
It would be great if you could exercise a test build with a fix I've prepared. I can contact you off list. 73, David KD0BTO On Wednesday, September 2nd, 2026 at 11:50 PM, hellozerohellozero via wsjt-devel <[email protected]> wrote: > From Laurence Howell - KL7L (and from multiple 475 and 137kHz slow speed 900 > and 1800 secs users worldwide) > > Operating systems - Win 10 and 11 (maybe some are still using WIN7) - Win 11 > users seem to have more issues > Code current w3.0.2 and at least as far back to 3.0.0 maybe further > Mode : FST4W 900 and 1800 maybe issues with 300 secs but not seen here > > Users affected - all that have been canvassed on working groups have these > issues and some say its been going on since the code and fst4w code was > releases > User locations - worldwide users reporting > > Issues - > > > - On selection of ½ or 2/2 tx periods in say 900 or 1800 sec mode, the Tx > will not enable at the time to tx , or miss first one or two or more periods, > or miss a period after a few good tx periods - the clear for some is to set > up mode and band set random 100% and then close wsjt, wait 15 secs and then > restart program with wanted ½ or 2/2 periods - but will occasionally not tx > when it comes to the time to tx - Everyone seems to have a non standard trick > but no one is reporting "mine works all the time" so seems endemic - I cant > get mine to behave here with any trick at 900 sec speed on tx - sometimes it > behaves, sometimes not > > > - On pressing TUNE button - the program misses the first or more > transmission period - the clear for this is to, after tune to restart program > and do not press Tune - this "clear" has been reported by at least 20 users > (and there arent a lot of us globally!) > > > - The Tx Next button at these speeds is funky - sometimes it will tx next > and sometimes not - reported by many > > > > In all cases Enable Tx stays lit ok > > > Appreciate you looking at this for the users of these long wavelengths, and > hope this reached the right target > > Very 73 and thank you for the code and support! > Laurence KL7L and users of 475 and 137kHz globally _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
