[Dx4win] Re: LOTW Import
Jim Reisert AD1C
jjreisert at alum.mit.edu
Fri Feb 1 14:08:20 EST 2008
Hi Marcelo,
You are not the first to have this problem. Something is wrong on the ARRL
server.
Maybe Paul can put in a work-around in the next version.
73 - Jim AD1C
--- marcelo at alternex.com.br wrote:
> I´ve found a unusual behavior in DX4WIN LoTW import.
>
> For some reason, I have some 5.000 QSOs in LoTW that are marked as <PHONE> in
> the mode.
> (They are from a WPX contest my computer went dead, and I logged per hand...
> later on I used a software called cabrillotools to generate the log).
>
> LoTW treats these QSOs normally, and issues credits correctly. The
> lotwreport.adi lines come as follows:
>
> <APP_LoTW_OWNCALL:5>PY1KN
> <STATION_CALLSIGN:5>PY1KN
> <CALL:4>K9DJ
> <BAND:3>15M
> <MODE:5>PHONE
> <QSO_DATE:8>20050326
> <TIME_ON:6>235800
> <QSL_RCVD:1>Y
> <QSLRDATE:8>20080201
> <DXCC:3>291
> <CQZ:1>4
> <ITUZ:1>8
> <GRIDSQUARE:6>EN54wn
> <STATE:2>WI
> <CNTY:8>WI,BROWN
> <eor>
>
> When I import this into DX4WIN, I get the error file:
>
> The following QSOs were not found in the log,
> but they were flagged as confirmed in the imported log.
> K9DJ 26-Mar-2005 23:58 15m CW
> ......
>
> I found out, by making some tests, that <MODE:5>PHONE is somehow translated
> as CW (my default mode in DX4WIN).
>
> I solve this by making a global Search&Replace in the file, 5:>PHONE to
> 3:>SSB every time I import the report back into LOTW.
>
> But maybe others my stumble into the same problems.
>
> Thanks for all the help
>
> Marcelo, PY1KN
--
Jim Reisert AD1C/Ø, <jjreisert at alum.mit.edu>, http://www.ad1c.us
More information about the Dx4win
mailing list