[Dx4win] Writelog to DX4WIN log conversion
Jim Reisert AD1C
jjreisert at alum.mit.edu
Thu Oct 2 17:34:26 EDT 2008
For a few years now, I have been working on a tool to convert Writelog
logs to DX4WIN. More on the features later. The main reason I wrote it
was that I don't like the way DX4WIN imports ADIF files:
- it puts "Freq=" in the "Notes for this QSO" field, which makes the
QSOs look "different" than non-contest QSOs (i.e. when you have Contest
Mode enabled in DX4WIN)
- it puts the sent serial number into that same field (even when the
contest doesn't have serial numbers, like ARRL FD)
- it doesn't put some data in the Recvd field which you might put there
if you were using DX4WIN to log the contest, like Class (2A, 1D, etc.)
in ARRL Field Day.
I mostly use Writelog for RTTY contests, but plan to use it more for
other CW/SSB contests.
Now onto the program features:
- it's Windows GUI based. It's just a .EXE file, it does not use the
Windows installer
- it inputs the ADIF file that you export from Writelog
- it outputs a .DXQ file which DX4WIN can import in DX4WIN6 format
- it supports (converts) these contests:
BARTG
BARTG_SPRINT
CAQP
CQWW
FD (ARRL Field Day)
JARTS
NAQP
NA_SPRINT
RU (ARRL RTTY Round-up)
SS (ARRL Sweepstakes)
WAE
WPX
Notice these are mostly RTTY contests. If the rules are exactly the
same for non-RTTY, then that conversion should work.
- CAQP is the only contest so far that automatically converts the CA
county abbreviations to actual county names compatible with DX4WIN. I
plan to use Writelog this weekend in the contest.
Caveats:
- I've only tested with Writelog 10.68. I don't know if the
APP_WRITELOG fields in the Writelog ADIF file are the same for all
versions of Writelog. They also might be different if a contest has
different modes, i.e. CQWW CW/SSB and CQWW RTTY.
- If the contest has names (like NAQP), importing the converted log may
duplicate the name in the "Notes for this Call" field, i.e. Jim/Jim.
This might be true any time you import a log into DX4WIN.
- There may be a program like this already out there that I'm unaware of.
If there's interest, I can make this program publicly available on an
"as-is" basis. I'll fix bugs and take feature requests, but
implementing them will be at my whim.
73 - Jim AD1C
--
Jim Reisert AD1C/Ø, <jjreisert at alum.mit.edu>, http://www.ad1c.us
More information about the Dx4win
mailing list