[Dx4win] JT alert and DX4win Version 9.04

[Jim Rhodes]

Of course you have to do that after every log import to keep it up to date.
I know I do anyway as I use laptops for portable sessions and need to
cosolidate logs to one place anyway

Jim Rhodes
K0XU

On Tue, Sep 11, 2018, 14:48 wo2n at att.net <wo2n at att.net> wrote:

> Jim/ AD1F
> RR -Very good info - good workaround I will have to try that.
> Thank you so much for the explanation seems pretty clear.
> We all know those spots on FT8 come through so fast it’s hard to grab them
> manually and scroll back etc... the alert would be a good tool. Thanks for
> taking the time for that In-depth explanation.
> 73, de Bernie/WO2N.>
>
> Sent from my iPhone X
>
> > On Sep 11, 2018, at 2:02 PM, Jim Reisert AD1C <jjreisert at alum.mit.edu>
> wrote:
> >
> > JTAlert can be used with DX4WIN.  It's just not as integrated as with
> > the other platforms.  It requires you to use an ADIF log instead of
> > one of the other logging programs.
> >
> > You can find JTAlert here:    https://hamapps.com/
> >
> > Make sure you have configured JTAlert first, especially your callsign
> > ("Station Callsign").
> >
> > You will need to export part or all of your DX4WIN log to an ADIF
> > file.  In my case, I export only the FT8 QSOs by using F8 and
> > searching for Mode=FT8.   You can alternatively extract all
> > digital-mode QSOs using ALT-F8, then choosing "Digital" from the Mode
> > drop-down list.
> >
> > File | Import/Export => File | Export to save the exported log in ADIF
> > format.  You will need to save the ADIF file in the exact place that
> > JTAlert expects to find it.  In my case, that path is as follows (also
> > see the link to the PNG image below).
> >
> >    C:\Users\jjrei\AppData\Local\HamApps\AD1C\logs\JTAlertX\AD1C_log.adi
> >
> > If you set up filtering using F8, DX4WIN will ask if you want to use
> > the filter during export.  Answer Yes.
> >
> > You will then need to configure JTAlert to use ADIF file logging.  See
> > the image here.  Note path to the ADIF file at the bottom:
> >
> >    http://dx4win.ad1c.us/JTAlertSettings.plugin_2018-09-11_06-38-47.png
> >
> > Finally, request that JTAlert scan the ADIF log to populate your
> > "Needs Lists" using the "Scan Log and Rebuild" function.  New QSOs
> > logged by JTAlert will be added to the existing ADIF log file shown
> > above.
> >
> > Two things to keep in mind:
> >
> > 1.  I do not import the JTAlert ADIF file (AD1C_log.adi above) into
> > DX4WIN after I have made new digital QSOs.  Instead, I import the ADIF
> > log from WSJT-X.  The ADIF file from JTAlert has more stuff in it that
> > I don't necessarily want to import, like perhaps state, grid, city
> > and/or name.  You can decide for yourself.
> >
> > 2.  As you accumulate QSO confirmations in DX4WIN (LoTW, eQSL and/or
> > paper), you may want to refresh the JTAlert ADIF file occasionally.
> > Simply export a new ADIF file from DX4WIN, save it to the same place
> > as shown above, then "Scan Log and Rebuild" again.
> >
> > This is a rough draft of an application note I intend to write
> > someday.  Please post corrections to the DX4WIN reflector.
> >
> > 73 - Jim AD1C
> >
> > --
> > Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us
>
> ______________________________________________________________
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN at mailman.qth.net
> Message delivered to jim at rhodesend.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html