Dick,
Agree with you Dick.  It is a big pain to log an "abbreviated" FT8 QSO which 
omits the grid square.  I used to use 
http://www.levinecentral.com/ham/grid_square.php to look up  missing grids.  
With the grid square competition now history ... grids to some are less 
important.  Altho I am not a grid square collector - I always looked up the 
missing grid square because my "logs" required them.  Of course we can not log 
an FT8 contact into the grid square database without a valid grid square.  
However, we can log an FT8 exchange into our "FT8 contact" log without a grid.  
It simply has no entry for the grid square data element.  This is not a big 
show stopper because my logging program updates certain missing fields when I 
import the WSJT-X log.adi file.  

But fundamentally Dick, when working as a DX station, I simply ignore stations 
which do not go thru the entire FT8 exchange sequence because many of them are 
QRMing my in-progress QSO and simply being rude, like I said previously.  I 
hear several people talk about speeding up FT8 exchanges by eliminating certain 
parts of the FT8 sequences.  For the most part, I reject that argument.  Maybe 
we all have a lot of time on our hands even if we are working FT8, and working 
one more redundant DXCC entity is perhaps no big deal.

Have a good day.
        Danny        W4/AH6FX - Virignia
    On Friday, April 12, 2019, 5:38:40 PM EDT, Richard Solomon 
<w1...@outlook.com> wrote:  
 
 As fast as FT8 is, there are folks who want a QSO completed faster.
It's a real pain, especially if I have to look up the guys call to get his 
Grid Square. And, if it's a portable operation, it's even more difficult. 

73, Dick, W1KSZ

Sent from OutlookFrom: Timothy Hickman <timothyhick...@comcast.net>
Sent: Friday, April 12, 2019 11:44 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] FT8 calling CQ I have noticed lately that when I send CQ 
on FT8 A few stations start
their respond with the signal report not their grid square.

Is there something here I do not understand?

Tim

N3JON



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to