Running v2.6.0 in my tests. The defect also confirmed by a JTAlert test team member running v2.6.1

Testing here with a WD time of 4 minutes, which I know is much longer that the hard-coded Hound WD time, When in Hound mode and the WD is triggered and Tx is disabled there is no UDP status for the WD triggered sent. The WD count down in the bottom right of the WSJTX window continues to count down after TX has stopped but when it reaches 0 the WD UDP Status is not sent which to me seems correct as WSJTX was not TX enabled at the time because of the earlier disabling of TX by the Hound mode WD triggering.

Looks to me like there are at least 2 WD timers in the WSJTX code. One for normal operation that uses the user-settable the WD time setting, The second WD timer is when in Hound mode and this is a hard-coded value and does not appear to be setting the UDP Status TX Watchdog flag when the WD is triggered.

de Laurie VK3AMA
(JTAlert author)
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to