locked WSJT FT-8 Transmit watchdog unusual behavior


Henry Kiernan
 

Have my transmit watchdog set for 10 minutes, and it normally works that way just fine.
Tonight I was calling 7Q7RU who was using fox/hound, but watchdog was cutting me off after only 2 minute intervals. no idea why this unusual behavior. anyone else have this issue?

Hank  KF2O



Bill, WB6JJJ
 

Normal operation for Fox/Hound...  It’s in the manual.

Bill
WB6JJJ 


On Nov 22, 2020, at 5:55 PM, Henry Kiernan via groups.io <HANKKIER@...> wrote:


Have my transmit watchdog set for 10 minutes, and it normally works that way just fine.
Tonight I was calling 7Q7RU who was using fox/hound, but watchdog was cutting me off after only 2 minute intervals. no idea why this unusual behavior. anyone else have this issue?

Hank  KF2O






JP Tucson, AZ
 

Hi Hank,

Yes, "normal" - one of those very annoying "features" of wsjt-x; supposedly to "prevent it from becoming an automatic QSO machine".  



73 - John - N7GHZ


On Sun, Nov 22, 2020, 6:55 PM Henry Kiernan via groups.io <HANKKIER=aol.com@groups.io> wrote:
Have my transmit watchdog set for 10 minutes, and it normally works that way just fine.
Tonight I was calling 7Q7RU who was using fox/hound, but watchdog was cutting me off after only 2 minute intervals. no idea why this unusual behavior. anyone else have this issue?

Hank  KF2O






David Larrabee
 

I think it is a good idea to check for open spectrum more frequently in F&H, esp as all the calling stations are in a narrower passband than for typical ops....   /K1BZ


Martin G0HDB
 

On Mon, Nov 23, 2020 at 02:08 AM, JP Tucson, AZ wrote:
Hi Hank,
 
Yes, "normal" - one of those very annoying "features" of wsjt-x; supposedly to "prevent it from becoming an automatic QSO machine".  
I don't find the non-adjustable watchdog timer in F & H mode at all annoying; IMO it's a very worthwhile function to have hard-coded in the WSJT-X software because if the timeout period was adjustable, as it is in standard FT8, then you can bet your boots that some inconsiderate Hound ops would set it so that they kept calling the Fox incessantly, whether or not they were in attendance of their system and whether or not they were copying the Fox.  Having the fixed and relatively short-duration watchdog timeout does help eliminate some of the potential QRM from stupid Foxes...  :-)

--
Martin G0HDB


Henry Kiernan
 

understand this point. maybe a compromise is in order. limiting to 2 minutes is indeed annoying. keep in mind that if a station is working F/H mode then he/she is rare and lots of folks will be calling. in most cases it may take many minutes/hours to get through even for entirely legit hounds. how about raising the bar to say 10 minutes, which should defeat the non-attendees but not be overly burdensome to legit callers.

Hank  KF2O


-----Original Message-----
From: Martin G0HDB <marting0hdb@...>
To: main@WSJTX.groups.io
Sent: Mon, Nov 23, 2020 3:09 pm
Subject: Re: [WSJTX] WSJT FT-8 Transmit watchdog unusual behavior

On Mon, Nov 23, 2020 at 02:08 AM, JP Tucson, AZ wrote:

Hi Hank,
 
Yes, "normal" - one of those very annoying "features" of wsjt-x; supposedly to "prevent it from becoming an automatic QSO machine".  
I don't find the non-adjustable watchdog timer in F & H mode at all annoying; IMO it's a very worthwhile function to have hard-coded in the WSJT-X software because if the timeout period was adjustable, as it is in standard FT8, then you can bet your boots that some inconsiderate Hound ops would set it so that they kept calling the Fox incessantly, whether or not they were in attendance of their system and whether or not they were copying the Fox.  Having the fixed and relatively short-duration watchdog timeout does help eliminate some of the potential QRM from stupid Foxes...  :-)

--
Martin G0HDB