My ONLY message that I was sending was "E44OM AF8C EN81" with
unsuccessful contacts using 3.0.0. I had a successful contact with E44OM
on 10m with 2.7.0. So I was NOT criticizing SuperHound as defective,
only the timer display in the right-hand corner.
My point was that the watchdog timer readout should not start at 30
minutes, then in the middle suddenly decrement to 2 minutes, and have
glitches (29,26) and so forth. The numbers should decrement smoothly
from 5 or whatever is first, end up at 0 like it does, and without
converting from "WD" to "HWD" (which I interpret to mean "Hound Watch
Dog"). This leads me to worry about things like buffer sizes being
wrong or pointer problems in the code. Code design should never have
issues like that.
Also, other than all that readout glitching, the actual watchdog timing
out and stopping transmissions worked fine. Also I did not test with
plain Hound or non-Hound operation. Maybe I should do that! I will let
you know.
--Glenn, AF8C
On 9/22/2025 1:37 AM, Reino Talarmo via wsjt-devel wrote:
Hi Glenn,
This is just educated guesswork about how the SuperHound
may work.
First, I assume that the same principle is applied to
the SuperFox as in F/H protocol:
'Fox will respond to such "R+rpt" messages by sending
"RR73" up to three times.'
Secord, that should mean the Hound at maximum sends the
"R+rpt" only three times and automatically stop after
that. The change in the WD: may indicate an
implementation of that feature. I have no idea which
messages you were sending in your test as it may affect
to the behavior.
73, Reino OH3mA
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
