[Dx4win] LoTW "notfound"

[Jim Reisert AD1C]

That ADIF code doesn't look right.  Here is the problem:

<APP_LoTW_MODEGROUP:5>PHONE
<APP_LoTW_MODE:5>PHONE

These are application-specific fields to LoTW.  DX4WIN is looking for
a field like this:

<MODE:5>PHONE

In addition, there is no "PHONE" mode in your logbook, it's probably
SSB, so it should really be:

<MODE:3>SSB

How did you sign and upload those QSOs? Did you convert the real mode
(SSB) to PHONE as part of the mode mapping inside the TQSL program?
You should NOT do this if you want things to match when you download
the QSO.

I just downloaded my most recent QSOs from LoTW, and things look OK.
Here is one example, MODE: is properly specified:

<APP_LoTW_OWNCALL:4>AD1C
<STATION_CALLSIGN:4>AD1C
<CALL:5>4A1TD
<BAND:3>15M
<APP_LoTW_MODEGROUP:5>PHONE
<MODE:3>SSB
<QSO_DATE:8>20130330
<TIME_ON:6>222815
<QSL_RCVD:1>Y
<QSLRDATE:8>20130611
<DXCC:2>50
<COUNTRY:6>MEXICO
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:3>4A1
<eor>

Maybe Paul can comment further.

On Wed, Jun 12, 2013 at 5:01 AM, Arunas LY2IJ <ly2ij at qrz.lt> wrote:
> Hi,
>
> I found few "notfound" contacts in my latest report from LoTW.
> Newer saw this before - I do regular uploads/downloads and always check
> "notfound" file. Seems something changed arround 1st June.
>
> Looks like DX4WIN don't take mode right sometimes.
> Here is line from "notfound" file and ADIF record for same QSO from LoTW
> report. Earlier I had problems with "phone" and "ssb" modes - had to
> replace all "phone" to "ssb" with notepad in LoTW report file, but not
> this time.
>
> Any ideas?
>
> 73 Arunas LY2IJ
>
>
> X PY7RP        11-Sep-2005 19:39   20m     CW      6
>
> <APP_LoTW_OWNCALL:5>LY2IJ
> <STATION_CALLSIGN:5>LY2IJ
> <CALL:5>PY7RP
> <BAND:3>20M
> <APP_LoTW_MODEGROUP:5>PHONE
> <APP_LoTW_MODE:5>PHONE
> <QSO_DATE:8>20050911
> <TIME_ON:6>193900
> <QSL_RCVD:1>Y
> <QSLRDATE:8>20130609
> <DXCC:3>108
> <COUNTRY:6>BRAZIL
> <APP_LoTW_DXCC_ENTITY_STATUS:7>Current
> <PFX:3>PY7
> <CQZ:2>11
> <ITUZ:2>13
> <GRIDSQUARE:6>HI22il
> <eor>

--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us