I just tested this and Fox tried 3 times to respond to a blind call.
I can guarantee that the majority of calls were blind and thus causing all 
sorts of time wasting at the DXPedition.
We really need to block blind calling so enforce the CQ-every-5 and prevent 
transmitting until you see CQ from the DX station.  Require the DX station to 
be put in the Advanced tab too and disable the DXCall box from being used too.
I know this sounds like a lot of hand holding but there are far too many 
abusing the FT8 protocol this way and not realizing the problem they are 
causing.  It shouldn't be up to the DXpedition to figure out who to 
block...they're busy enough....

de Mike W9MDB




 

    On Saturday, June 30, 2018, 11:08:17 AM CDT, Black Michael via wsjt-devel 
<wsjt-devel@lists.sourceforge.net> wrote:  
 
 But what about them receiving all these calls in the blind?  Isn't that going 
to interfere when they try to respond to people who can't hear them?
Mike


 

    On Saturday, June 30, 2018, 11:04:11 AM CDT, Bill Somerville 
<g4...@classdesign.com> wrote:  
 
  On 30/06/2018 16:57, Black Michael via wsjt-devel wrote:
  
  OK...so it appears the CQ every 5 trasnmissions is NOT enforced unless Fox 
clicks the "More CQs" box. We'd be a lot better off if this was always forced 
and Hounds were restricted to only answer CQ's. This explains why we don't see 
the CQ's and calling blind is normally necessary (as long as you can see KH7Z 
that is).
  
   if(m_tFoxTxSinceCQ >= m_foxCQtime and ui->cbMoreCQs->isChecked()) {
  
  de Mike W9MDB
  
   
    
 
Hi Mike,
 
it should be reasonable to assume that if the Baker Is. operators are not 
enforcing regular CQ calls then they have plenty of callers to keep the 
to-be-worked queue populated with more stations than Tx slots and a QSO rate 
that is high.
 

73
 Bill
 G4WJS.
  ------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to