In that case it could be simplified to just the start of Tx 2 or 3. CQ/Tx 1
still not being even close in too many circumstances.
I'd like to see exactly what is being reported as inaccurate and what they are
claiming is the "correct" time since it is rather subjective.
The way I see it is on tx/rx of 1st message.
de Mike W9MDB
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Monday, February 6, 2017 5:44 PM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 06/02/2017 23:36, Black Michael wrote:
At least in my theory the start time of two people in a QSO should be the
same. So... Tx 2 substract 2 time periods which should match the CQ time. Tx 3
subtracts 3 time periods which should match the CQ time.
Hi Mike, I think this is what is being reported as inaccurate. Calling CQ is
not starting a QSO. I know it is subjective but I tend to agree that only when
you reference your QSO partners callsign has a QSO started. With respect to an
extended period when trying to break a pile up, this is pretty much standard in
logging applications. Some take the view that entering your QSO partners signal
report is the start, others take the view that entering the callsign is the
start and you can always adjust the start time when completing the QSO or
logging it. I do not think there is any requirement for both parties to log the
same times, band, mode and time within a 15 or 30 minute windows is usually
considered a match.
73
Bill
G4WJS.
------------------------------------------------------------------------------
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