LoTW allows a mismatch of up to 30 minutes.
This issue bit me yesterday during the 6 meter JA opening:
- Called a station, no response.
- Took a 30 minute break, without working another station.
- Called the same station, worked him.
Was very surprised to see the QSO time reported to N1MM+ as the start time, 31
minutes earlier. This is different than every other logging program which
records the QSO time as the end time, not the start time.
73,
Steve, N2IC
On 05/31/2018 10:47 AM, Tom Melvin wrote:
Hi
I much prefer the start time - if it takes me 30 mins to work a station I am
‘on the air’ for 30 mins - a) I need to log this to stay legal and b) it allows
me to see historically how long QSO;s take.
73’s
Tom
GM8MJV
On 31 May 2018, at 16:36, Steve London <[email protected]> wrote:
Version 1.9.0
When making a difficult QSO, many minutes can pass between the time the QSO was initiated and the
QSO was completed. These are identified in the log screen as "Start Time" and "End
Time". Currently, when a QSO is logged, the Start Time is placed in the ADIF file, and sent to
clients such as N1MM+. This is not standard for logging programs, and will lead to non-QSO time
mismatches in LoTW. The End Time should be written to the ADIF file and sent to clients.
73,
Steve, N2IC
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
