Dave,
When you have the QSO start-time in an ADIF record Dx4win will use that
time. If that field is missing, it will use the end-time. So I’m guessing
some ADIF producer is changing the values of those fields or does not
export the start-time.
That should be easy to verify.
—Paul
On Mon, Jun
@mailman.qth.net
Subject: RE: [Dx4win] QSO time issues when importing
This isn't a perfect solution, but it appears to have worked for me this
weekend:
https://www.rttycontesting.com/tutorials/n1mm/operating-ww-digi-with-n1mm/
This metho opens a second instance of WSJT that keeps its own log and
settings
Rick,
My comments were not directed toward LOTW. That’s not the issue. Thank you
for all your efforts in working to improve LOTW.
73,
Dave, N4QS
From: Rick Murphy
Sent: Monday, June 15, 2020 1:49 PM
To: n...@vci.net
Cc: DX4WIN
Subject: Re: [Dx4win] QSO time issues when
That's one of the great things about "standards" - all you have to do is
assert that there's one.
LoTW only sees the TIME_ON and not the TIME_OFF. So, the time that the QSO
started is what LoTW tracks, not when it ends.
73,
-Rick
On Mon, Jun 15, 2020 at 1:36 PM wrote:
> To Paul and the
Cizek W0VTT
-Original Message-
From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net]
On Behalf Of n...@vci.net
Sent: Monday, June 15, 2020 12:37
To: dx4win@mailman.qth.net
Subject: [Dx4win] QSO time issues when importing
To Paul and the group,
I continue to have
To Paul and the group,
I continue to have problems with dupes being created when importing digital
QSOs from WSJT-X. It appears that DX4WIN uses the QSO Begin time when all
other logging programs, including N1MM, use the QSO End time. The Log4OM2
website states that in the UK amateur
6 matches
Mail list logo
