Courtney,

You might be referring to the article I wrote about using a key mapper to
import from WSJT-X directly into DX4WIN.  That works great, but is a bit
more involved to setup.

For basic importing between WSJT-X and DX4WIN, this is what I recommend:

1.      You do not have to run WSJT-X and DX4WIN at the same time.  You can
keep DX4WIN closed until you finish with WSJT-X.  You can then close WSJT-X
and open DX4WIN anytime you want to import QSOS.  Another way is to keep
DX4WIN open but turn off the radio connection by clicking on Radio, Stop
Radio.  Then start WSJT-X -- but only WSJT-X will be connected to the radio.
After making a few QSOs in WSJT-X, you can import directly from WSJT-X into
DX4WIN while it is not connected to the radio.  See steps 3 and 4 below.
You can reconnect DX4WIN to the radio any time by first closing WSJT-X and
then clicking on Radio, Start Radio in DX4WIN.  A bit awkward, but workable.

2.      A better solution is to install Win4K3Suite so that you can have
WSJT-X and DX4WIN connected to the radio at the same time.   Win4K3Suite
costs about $50, but it is worth the investment.  Once you install it, you
also have to create some virtual com ports using com-0-com.  This takes a
little doing, but is not too hard.  Actually, very simple once you get
familiar with it.  By using Win4K3Suite, I keep WSJT-X and DX4WIN up and
running all day with both connected to my K3.  There is now a WinK4Suite if
you have a K4 and it is also available for the other major radio brands.
Well worth the time and investment.

3.      Importing the ADIF file from WSJT-X into DX4WIN is rather simple.
The only catch is remembering where the ADIF file is stored in Windows.  I
solve this by mapping a drive to the folder that stores the file.  I just go
into Windows Explorer, click on Computer at the top, and then Map Drive.
Windows will automatically assigned a letter for the new mapped drive like X
or Y or Z.  You then have to select the folder where the ADIF file for
WSJT-X is stored.  It is normally found by clicking on Local Disk (C:),
Users, then click on the user you are normally logged in as, App Data,
Local, WSJT-X.  Once you have found and selected the WSJT-X folder, click OK
to finishing setting up the mapped drive.  It will tell you what letter you
are using for the new WSJT-X drive.

4.      Once you have a mapped drive setup to the WSJT-X log folder, you can
then go into DX4WIN, click on File, Import, ADIF will be highlighted at the
top, click on File again, Import again, then select This PC on the left, and
the mapped drive that you setup will be shown at the top, double click to
open, and then select wsjtx_log.adi.  The new import window will be
displayed showing  Options for duplicate QSOs.  You always want to select
the top choice -- Imported QSO is ignored.  There will be a few more Oks to
select and the import will complete.  DX4WIN will only import new QSOs from
the WSJT-X log file and dupes will be ignored.

I have used the manual import process thousands of times over the last seven
plus years.  I have ten of thousands of QSOs stored in my WSJT-X log file,
and DX4WIN just ignores all the dupes and again only imports the new ones.
The import is virtually instantaneous.

A couple of additional hints:

1.      DX4WIN will automatically remember the location of the last file
that you imported.  Until you import some other file (like a download from
LOTW), it will always go back to the mapped drive folder that you specified.
When it does not, just go back and select MY PC and reselect the mapped
drive as described above.

2.      It seems that after a Windows update, DX4WIN will lose the mapped
drive entirely.  That is easily fixable by closing DX4WIN, opening Windows
Explorer.  The mapped drive for WSJT-X should be displayed at the bottom of
the small window.  I double click on the mapped drive to open it, and then
close Window Explorer.  I then restart DX4WIN and the mapped drive shows up
again.  This only happens about once a month so is not a big deal.

3.      After you master all the above, the next big step is to automate all
of the above with an automatic key mapper.  I use a little app called Macro
Recorder.  It has the ability to capture all of your keys strokes from when
you click okay to log a QSO in WSJT-X and then all of the manual keystrokes
that you normally have to make to import the WSJT-X log into DX4WIN.  So
after I log a QSO in WSJT-X, I just hit the Insert key (my choice) and the
key mapper takes over and completes the import of the QSO that I just logged
into DX4WIN.  Takes about 3 to 4 seconds.  Works like a champ.  I also use
the key mapper to import QSOs automatically from JTDX.  I have a second
drive mapped for the JTDX log folder.

This isn't really to hard once you get the hang of it.  Of course, we all
would love to have Paul implement an truly automatic way to import QSOs from
WSJT-X into DX4WIN.  This can easily be done by using the UDP broadcast
function built into WSJT-X and many other leading logging programs, but not
DX4WIN!

Good luck!

73,

Dave, N4QS

-----Original Message-----
From: dx4win-boun...@mailman.qth.net <dx4win-boun...@mailman.qth.net> On
Behalf Of Courtney Judd
Sent: Friday, March 24, 2023 10:06 AM
To: dx4win@mailman.qth.net
Subject: [Dx4win] wsjt

Hey all, just got FT8 up and running here in the shack now and wondering on
how best to get the logs from WSJT to DX4WIN ver 9.09. I googled it and
found an interesting article by Dave N4QS but not sure if I am capable of
setting this up. I struggle with Win 10 and my ham software .... just
keeping it running smoothly is a on-going battle. So any help/ideas on how
to set this up would be appreciated. I tried to have DX4WIN open at the same
time with WSJT but ended up with rig control conflict so starting off bad
already lol! Thanks, 73's Cort K4WI

Sent from Postbox <https://www.postbox-inc.com>
______________________________________________________________
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

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

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

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

Reply via email to