Hi All,
I am looking at the code for setting the start and end times of QSOs
because I've had reports of it not being as accurate as it should be. It
does seem a bit overcomplicated.
I don't see why it should not be that the start time is when the DX call
box gets changed and the end time is w
e
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.
de Mike W9MDB
From: Bill Somerville
To: WSJT software development
Sent: Monday, February 6, 2017 5:06 PM
Subject: [wsjt-devel] WSJT-X: QSO start and
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 re
"I don't see why it should not be that the start time is when the DX call
box gets changed and the end time is when the QSO is logged."
I frequently double click a call of interest so I can track the station in the
Rx frequency pane. It could be hours before I make the first transmission in
I see it is on tx/rx of 1st message.
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
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 st
On 07/02/2017 04:10, ANDY DURBIN wrote:
"I don't see why it should not be that the start time is when the DX call
box gets changed and the end time is when the QSO is logged."
I frequently double click a call of interest so I can track the
station in the Rx frequency pane. It could be hour
Hi Mike,
On 07/02/2017 04:45, Black Michael wrote:
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.
Why is Tx 1 not the start of a QSO?
I'd like to see exactly what is being reported as inaccurate and what
they
ille
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 5:57 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 04:10, ANDY DURBIN wrote:
"I don't see why it should not be that the start time is when the DX call
box gets changed and the end time is
ect".
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 6:04 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
Hi Mike,
On 07/02/2017 04:45, Black Michael wrote:
In that case it could be simplified to just the start of Tx
"I also wonder if the ones complaining are using the older version of JTAlert
which tries to "guess" the TIME_ON from the 1st observation of the callsign
which works on a normal QSO but not when you're waiting for them at all"
I have not complained to anyone but I have had to track down multipl
I do believe it's JTAlert 2.9.0 that has the TIME_ON fix and you have to be
using r7430 or greater.
de Mike W9MDB
From: ANDY DURBIN
To: "wsjt-devel@lists.sourceforge.net"
Sent: Tuesday, February 7, 2017 8:16 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end tim
On 07/02/2017 14:16, ANDY DURBIN wrote:
Any code that attempts to derive a QSO start time should also include
a reasonableness test on QSO duration.
HI Andy,
what could that reasonable test be?
For example a pair EME operators with marginal conditions and mid level
equipment might expect to
On 07/02/2017 13:50, Black Michael wrote:
> Where are the examples of it being wrong? I'm a bit pedantic about
> time and would like to fix it to be what everybody agrees is "correct".
Hi Mike,
TBH I am struggling to get the current version of WSJT-X to record any
reasonable QSO start time whe
wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 9:36 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 13:50, Black Michael wrote:
> Where are the examples of it being wrong? I'm a bit pedantic about
> time and would like to fix it to be
On 07/02/2017 15:40, Black Michael wrote:
How do you do the simulation?
The TIME_ON defaults to the logging time only when it hasn't been set
yet. Currently only done when Tx 2 or 3 is clicked by either Next or Now.
Are you simulating without clicking? That might 'splain it.
Hi Mike,
two
xample that shows that's not working? de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 9:50 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 15:40, Black Michael wrote:
How do you do the simul
Give me the ALL.TXT entries from the test and the times you saw on logging and
I'll figure out what's going on.
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 9:50 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and
"I do believe it's JTAlert 2.9.0 that has the TIME_ON fix and you have to be
using r7430 or greater.
de Mike W9MDB"
I browsed the JTAlert change log:
JTAlert Ver 2.5.0 13 Nov 2014
- QSO Start time field in Log Fields area. Populated with the utc time when
a new QSO partner Callsign is
DB
From: ANDY DURBIN
To: "wsjt-devel@lists.sourceforge.net"
Sent: Tuesday, February 7, 2017 10:04 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
"I do believe it's
JTAlert 2.9.0 that has the TIME_ON fix and you have to be using r7430 or
greater.
de Mike W9MDB&
On 07/02/2017 16:16, Bill Somerville wrote:
> 1534 Transmitting 14.076 MHz JT65: G4WJS G0FUN 73
> 1535 -1 0.1 1500 # G0FUN G4WJS 73
...
Sorry prematurely sent e-mail.
I believe Station A (G4WJS) had a log window showing time on and off as
15:31 and Station B (G0FUN) was offered time on an
On 07/02/2017 16:04, Black Michael wrote:
Give me the ALL.TXT entries from the test and the times you saw on
logging and I'll figure out what's going on.
Hi Mike,
Station A ALL.TXT:
1509 Transmitting 14.076 MHz JT65: G0FUN G4WJS IO91
1511 Transmitting 14.076 MHz JT65: G0FUN G4WJS IO91
1
example. Probably has to do with when time_on is reset.
Did you perhaps click on another message then on R-01 again like one might do
for queuing up the next message?
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 10:21 AM
Subject
"what could that reasonable test be?"
It could be a test that the time span between the derived QSO start time and
the derived QSO end time did not exceed a user specified maximum QSO duration.
I would set it to 30 minutes. You could set it to whatever time was
appropriate for your fishing
@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 10:21 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 16:16, Bill Somerville wrote:
> 1534 Transmitting 14.076 MHz JT65: G4WJS G0FUN 73
> 1535 -1 0.1 1500 # G0FUN G4WJS 73
...
Sorry prematurely sent e-mail.
I b
@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 10:21 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 16:16, Bill Somerville wrote:
> 1534 Transmitting 14.076 MHz JT65: G4WJS G0FUN 73
> 1535 -1 0.1 1500 # G0FUN G4WJS 73
...
Sorry prematurely sent
On 07/02/2017 16:40, ANDY DURBIN wrote:
"what could that reasonable test be?"
It could be a test that the time span between the derived QSO start
time and the derived QSO end time did not exceed a user specified
maximum QSO duration. I would set it to 30 minutes. You could set
it to what
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 7, 2017 10:21 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 16:16, Bill Somerville wrote:
> 1534 Transmitting 14.076 MHz JT65: G4WJS G0FUN 73
> 1535 -1 0.
ary 7, 2017 12:09 PM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 16:40, ANDY DURBIN wrote:
"what could that reasonable test be?"
It could be a test that the time span between the derived QSO start time and
the derived QSO end time did not exceed a
My Comments inline...
On 8/02/2017 1:16 AM, ANDY DURBIN wrote:
"I also wonder if the ones complaining are using the older version of
JTAlert which tries to "guess" the TIME_ON from the 1st observation of
the callsign which works on a normal QSO but not when you're waiting
for them at all"
On 8/02/2017 5:09 AM, Bill Somerville wrote:
Added to all this you have the ALL.TXT file for reference so if in the
rare event you forget that the start time is too early due to an
extended call that is not heard and, say, if an LotW confirmation is
not forthcoming; you can review the QSO,
On 8/02/2017 3:04 AM, ANDY DURBIN wrote:
- QSO Start time field in Log Fields area. Populated with the utc time
when
a new QSO partner Callsign is detected. If it contains a value
it will
override the time provided by WSJT-X and JT65-HF logging event.
I could find no record th
Agreed, Laurie - and considering systems like LoTW or QRZ etc allow for +/-30
minutes for award tracking, it would seem this isn't a massive issue to the end
user anyway, especially if they're paying attention to what they're actually
logging (I know those extra few key strokes may be difficult
alls VK3FM
vk...@wallsy.com.au<mailto:vk...@wallsy.com.au>
Mobile 0418 301 483
From: Laurie, VK3AMA [mailto:_vk3a...@vkdxer.net]
Sent: Wednesday, 8 February 2017 5:45 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 8/02/2017 5:09 AM, Bill
"There is also the option that the *user take some responsibility* over
what they are logging and spend a few seconds during a lengthy JT65/9
QSO to ensure that the Start time (if they are using JTAlert) is
correct. If they are not using JTAlert, the Time_on field is available
for editing prior to
That will be in 1.7.1.
de Mike W9MDB
From: ANDY DURBIN
To: "wsjt-devel@lists.sourceforge.net"
Sent: Tuesday, February 7, 2017 3:57 PM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times (Laurie, VK3AMA)
"There is also the
option that the *user take some
Also, do you have the log fields visible on JTAlert? The "Time" field there is
the start time it uses prior to the change to WSJT-X.
de Mike W9MDB
From: ANDY DURBIN
To: "wsjt-devel@lists.sourceforge.net"
Sent: Tuesday, February 7, 2017 3:57 PM
Subject: Re: [wsj
36 matches
Mail list logo
