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 t
The desired operation would be that the TX watchdog setting is also used
for Hound mode.
73,
Ton PA0TBR
On Tue, 17 Jan 2023 at 20:37, Laurie, VK3AMA via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Running v2.6.0 in my tests. The defect also confirmed by a JTAlert test
> team member
On 18/01/2023 8:41 am, Ton PA0TBR wrote:
The desired operation would be that the TX watchdog setting is also
used for Hound mode.
73,
Ton PA0TBR
That's correct. I neglected to say that in my original fault report.
The Tx Watchdog being triggered in Hound mode should be setting the
relevant f
The User Manual for FT8 DX-pedition mode, "Detailed Instruction for Hounds"
# 11 at the top of page 5, says:
> You will need to re-activate Enable Tx (or hit
> Enter on the keyboard) at least once every two minutes. (This restriction
> is to
> ensure that an operator is present and paying attentio
On 19/01/2023 1:45 am, Frode Igland wrote:
this tells that the WD timer in Hound mode is deliberately hardcoded
and non-editable
I am not asking that the Hound mode WD timer be editable. I am fine with
it being fixed. I fully support that design.
The problem (defect) is that the status of
Yes, Laurie, but exactly this is (hopefully) being done with the two
test installers I sent you. Please confirm that it works with them.
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
I have nothing against getting WD reporting in the UDP Status message, but
I guess the most important part of the WD in Hound mode is that the "Enable
Tx" button is deactivated, and that the operator must be able to maintain
an attention span of two minutes to reactivate the "Enable Tx" button. Tha
