[Dx4win] Uploading FT8 QSO's to LOTW

[Mike Cizek W0VTT]

Hello Tom,

There is an easier way.  For FT8, log them as TOR, a mode supported by
dx4win but not by LoTW.  In TQSL, under File > Display or Modify
Preferences... > ADIF Modes > Add...   Type TOR in the ADIF Mode window,
select FT8 for the Resulting TQSL mode, and select OK.  Now, all of the FT8
QSOs that you logged as TOR will be converted to FT8 when they are signed
and uploaded to LoTW.   Unfortunately, you cannot do the same with FSK441 to
MSK144 because both modes are supported by LoTW.

OR - you can simply upload your WSJT-X adif log to LoTW through TQSL.

Note that in LoTW, ANY mode in the Data mode group will provide a match with
any other mode.  For example, if you log your FT8 QSO as TOR and upload it
as either TOR or FT8, and the other guy uploads his as RTTY or simply as the
generic DATA mode, it will generate a match.  DXCC does not care which
digital mode you use.

Rest assured that dx4win version 9 DOES include all of the new modes.  

73,
Mike W0VTT

-----Original Message-----
From: dx4win-bounces at mailman.qth.net [mailto:dx4win-bounces at mailman.qth.net]
On Behalf Of Tom Hammond
Sent: Wednesday, 23 August, 2017 13:20
To: DX4WIN at mailman.qth.net
Subject: [Dx4win] Uploading FT8 QSO's to LOTW

Greetings folks. Thought I'd share an experience that might help you, or,
someone might point out how to do this differently. 

 

I've made a handful of FT8 QSO's. Since DX4WIN doesn't have an FT8 mode
(YET!) I was selecting a similar mode of JT65. When the ARRL announced that
FT8 was now a supported mode on LOTW, I decided to export my FT8 QSO's and
upload to LOTW. 

 

So, in DX4WIN, I exported my QSOs creating an .adi file. I then edited this
file and changed all occurrences of JT65 to FT8. I saved the file and then
used TQSL to sign and upload my .adi file. However, TQSL said the "FT8 " was
an invalid mode. Wait, what? Maybe you already know where I went wrong. 

 

In the .adi file there are XML-like field names. My .adi file had
<MODE:4>FT8. Well, it turns out that "4" after MODE means that the mode is
4-characters long, BECAUSE, I had originally chosen JT65 as the mode which
IS 4-characters long. Once I figured this out, I changed the field heading
to <MODE:3>FT8 and saved the file. This time my file was signed and uploaded
with no errors. 

 

I've done similar search and replace from FSK441 to MSK144 but both of those
mode strings are 6 characters, so I didn't have to change the <MODE:6> field
heading. 

 

So, lesson to be learned here is, when selecting an alternative mode for
your FT8 QSO's, try to find a 3-character mode so that when you perform a
search and replace of your adi file, you also won't have to change each
occurrence of the <MODE:X> length character. 

 

There's got to be an easier way..

 

73, Tom

K8BKM

 

______________________________________________________________
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN at mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html