Re: [Dx4win] Format for FT8 mode Input in ADIF file for TQSL?

2017-08-14 Thread Steve Lund
VTT > > -Original Message- > From: dx4win-boun...@mailman.qth.net [mailto:dx4win-bounces@ > mailman.qth.net] > On Behalf Of Paul Ferguson > Sent: Monday, 14 August, 2017 17:22 > To: dx4win@mailman.qth.net > Subject: [Dx4win] Format for FT8 mode Input in ADIF file for T

Re: [Dx4win] Format for FT8 mode Input in ADIF file for TQSL?

2017-08-14 Thread Mike Cizek W0VTT
-boun...@mailman.qth.net] On Behalf Of Paul Ferguson Sent: Monday, 14 August, 2017 17:22 To: dx4win@mailman.qth.net Subject: [Dx4win] Format for FT8 mode Input in ADIF file for TQSL? I used DX4WIN LOTW > Export to LOTW. Most of the QSOs in this batch were FT8 mode. I then edited the LOTW ADIF formatted file to

Re: [Dx4win] Format for FT8 mode Input in ADIF file for TQSL?

2017-08-14 Thread Bud Semon
Hi Paul, Yes, "MODE:4" is incorrect. In the ADIF format, the number indicates the number of characters in the mode name. So JT65 was 4 and FT8 should be 3, as in "MODE:3>FT8". 73, Bud N7CW On Mon, Aug 14, 2017 at 3:21 PM, Paul Ferguson wrote: > I used DX4WIN LOTW > Export to LOTW. Most of t

[Dx4win] Format for FT8 mode Input in ADIF file for TQSL?

2017-08-14 Thread Paul Ferguson
I used DX4WIN LOTW > Export to LOTW. Most of the QSOs in this batch were FT8 mode. I then edited the LOTW ADIF formatted file to indicate FT8 mode on all FT8 QSOs. I noticed the file entry for a JT65 QSO mode was "JT65" so I tried "FT8" on FT8 QSOs. When I use the TQSL V2.3.1 with Configurati