Jim,
I can do as you suggest or I can even interface WSJT-X with Log4OM and do it
seamlessly. I chose to do it as described to Murphy-proof things as much as
possible and follow the KISS principle.
Thanks for the comment Jim. Have a great day.
Danny AH6FX/W4 - Virginia
On Friday, May 22, 2020, 4:39:35 PM EDT, Stephen VK3SIR
<vk3...@hotmail.com> wrote:
Hi Michelle,
By far the best way to avoid duplicates in logs is to not set
"Settings\Reporting\ Log automatically..." . If you come back with a RR73, auto
log, and then a station comes back with a R-XX (what I term a "RR/73 Loop")
then both communication and logging can lead to duplicates in logs.
Each logged entry should be manually approved (so do not check "Log
automatically").
Some software loggers and bridges such as JTAlert (that I use and recommend
heavily) also are not perfect. I use JTALert with DXLab's DXKeeper. No matter
what I do sometimes (and erratically) a duplicate is logged to eQSL. These are
issues for their support forums. Despite this forewarning would strongly echo
Jim's post and recommend JTAlert's use to you !
JTAlert can be found at https://hamapps.com. DXLab can be found at
https://dxlabsuite.com . None of these products are viruses if your AV scanner
goes into overdrive and its safe to add these programs (and their destinations)
as AV over-rides.
I personally use DXKeeper as the central logging tool and use its "Export
QSO's" function to "Export standard ADIF" back to the "wsjtx.log" file (found
in the location accessible by "File/Open Log Directory"). DXKeeper has great
tools for managing duplicates. When all duplicates are removed periodically
write them back to WSJT-X over-writing previous "wsjtx.log" instances :-)
More info on how to do this and set up products can be found on each product's
support forums :-)
73
Steve I
VK3VM / VK3SIR
-----Original Message-----
From: Jim Preston <jprest...@cox.net>
Sent: Saturday, 23 May 2020 1:15 AM
To: DX Jami via wsjt-devel <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] exporting from adi
Danny,
Why not just have JTAlert (if you use it) or WSJT-X log directly to Log4OM?
Then you wouldn't have to go through the adif import routine.
73,
Jim N6VH
On 5/20/2020 6:45 PM, DX Jami via wsjt-devel wrote:
> Michelle,
>
> My logging program is Log4OM ver2. I routinely import my WSJT-x adi
> files into Log4OM with no problems. Most logging programs import only
> current loggings. Ensure you click something like “do not import
> duplicates” in your logging program as you download and you should
> have no problems.
>
> Good luck.
>
> Danny
>
> AH6FX/W4 - Virginia
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
> *From: *Michelle Sack via wsjt-devel
> <mailto:wsjt-devel@lists.sourceforge.net>
> *Sent: *Wednesday, May 20, 2020 9:21 PM
> *To: *WSJT software development
> <mailto:wsjt-devel@lists.sourceforge.net>
> *Cc: *Michelle Sack <mailto:ms...@verizon.net>
> *Subject: *Re: [wsjt-devel] exporting from adi
>
> I'm new to FT8 and WSJT software. Is a way to export from the log only
> the recent contacts? This way I don't make duplicates in my logging
> programs but still keep contacts in the WSJT log for notifications of
> new (preventing duplicate contacts in FT8).
>
> Thanks
>
> Michelle N3YRZ
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
