Re: [wsjt-devel] Question about QSO Start & End Times

[John Nelson]

Mike,

I wonder if the problem is in 

void MainWindow::set_dateTimeQSO(int m_ntx)

where m_dateTimeQSOOn is calculated by assuming that TX periods are in minutes 
and not 15 secs in the case of FT8.  It seems to me that a new method has to be 
needed to calculate TimeQSOOn for FT8

— John G4KLA
--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[John Nelson]

Mike,

You wrote:


If you can confirm TX 6 is set during auto-seq try this change in mainwindow.cpp


void MainWindow::on_txb6_clicked()//txb6
{
  m_ntx=6;
  ui->txrb6->setChecked(true);
  if (m_transmitting) m_restart=true;
  if (ui->txrb6->text().contains("CQ") && !ui->cbAutoSeq->isChecked ()) 
set_dateTimeQSO(-1);
  //if (ui->txrb6->text().contains("CQ")) set_dateTimeQSO(-1);
}
—

I misread your email, especially the question.

The start=stop time problem is shown at TX = 5 which is when the QSO Log  
window pops up and the times are shown.After the log window is closed then 
the seq moves to TX = 6.  So the code snippet will not do anything useful (it 
seems to me) with regard to the start=stop time problem since the QSO Log is 
already written.

— John G4KLA
--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

Mike,

didn't help ... made the change, built r7782, no change.   Made sure the 
change was in the .cpp file, and cleaned the build tree. Built it again, 
same thing, start equals the end time.   See attached screen cap.


Neil, KN3ILZ


On 7/4/2017 1:56 PM, Black Michael wrote:
That sounds reasonable to mewhen doing this I just put it in for 
double-clicking on either window.  But the right side shouldn't need it.


Go ahead and remove the "set_dateTimeQSO(-1)" line from this section 
of code in mainwindows.cpp and see if behaves for you.



voidMainWindow::doubleClickOnCall2(boolshift,boolctrl)
{
set_dateTimeQSO(-1);//resetourQSOstarttime
m_decodedText2=true;
doubleClickOnCall(shift,ctrl);
m_decodedText2=false;
}
de Mike W9MDB

*From:* Neil Zampella <ne...@techie.com>
*To:* wsjt-devel@lists.sourceforge.net
*Sent:* Tuesday, July 4, 2017 12:03 PM
*Subject:* Re: [wsjt-devel] Question about QSO Start & End Times

UM .. how else do you respond when using JT65/JT9 .. I don't use the 
buttons on TAB 2.  Double clicking on a response in the RX window when 
I'm calling CQ I agree with, that should start the QSO, but double 
clicking in the TX window should not as its a normal way to trigger 
the next dialog is a normal way to progress through the QSO.


Or am I missing something here?

Neil, KN3ILZ

On 7/4/2017 11:38 AM, Black Michael wrote:
When you say "double click" you are talking about the double-clicking 
the message in the RX Frequency window?  That will reset the start 
time as of right now.


de Mike W9MDB


*From:* Neil Zampella <ne...@techie.com> <mailto:ne...@techie.com>
*To:* wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net>

*Sent:* Monday, July 3, 2017 6:44 PM
*Subject:* Re: [wsjt-devel] Question about QSO Start & End Times

In reply to your other post .. yes, I'm using JTSDK.

Again, I'm using Tab 2, not Tab 1.  JT65/JT9 .. no auto 
sequencing.Just double clicking to trigger the next response in 
the sequence.


On 7/3/2017 12:58 PM, Black Michael wrote:

Any double-clicks on lines will reset the start time to "unknown".

When the QSO transitions to TX 2 or TX 3 the start time gets set.
Any double clicks on lines after that would also reset the start 
time.  Tx 6 also resets start time.
If start time is not set by TX 2 or TX 3 then it will end up being 
the stop time.


And does autoseq sequence to "TX 6" by itself?  That would explain 
why autoseq modes get their time reset.


Mike






--
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
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

That sounds reasonable to mewhen doing this I just put it in for 
double-clicking on either window.  But the right side shouldn't need it.
Go ahead and remove the "set_dateTimeQSO(-1)" line from this section of code in 
mainwindows.cpp and see if behaves for you.


void MainWindow::doubleClickOnCall2(bool shift, bool ctrl){  
set_dateTimeQSO(-1); // reset our QSO start time  m_decodedText2=true;  
doubleClickOnCall(shift,ctrl);  m_decodedText2=false;}
de Mike W9MDB  From: Neil Zampella <ne...@techie.com>
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Tuesday, July 4, 2017 12:03 PM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
   
 UM .. how else do you respond when using JT65/JT9 .. I don't use the buttons 
on TAB 2.  Double clicking on a response in the RX window when I'm calling CQ I 
agree with, that should start the QSO, but double clicking in the TX window 
should not as its a  normal way to trigger the next dialog is a normal way to 
progress through the QSO. 
 
 Or am I missing something here?
 
 Neil, KN3ILZ
  
 On 7/4/2017 11:38 AM, Black Michael wrote:
  
  When you say "double click" you are talking about the double-clicking the 
message in the RX Frequency window?  That will reset the start time as of right 
now.
  
  de Mike W9MDB 
From: Neil Zampella <ne...@techie.com>
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Monday, July 3, 2017 6:44 PM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
  
   In reply to your other post .. yes, I'm using JTSDK.
 
 Again, I'm using Tab 2, not Tab 1.  JT65/JT9 .. no auto sequencing.    Just 
double clicking to trigger the next response in the sequence.   
  
  On 7/3/2017 12:58 PM, Black Michael wrote:
  
  Any double-clicks on lines will reset the start time to "unknown". 
  When the QSO transitions to TX 2 or TX 3 the start time gets set.   Any 
double clicks on lines after that would also reset the start time.  Tx 6 also 
resets start time. If start time is not set by TX 2 or TX 3 then it will end up 
being the stop time. 
  And does autoseq sequence to "TX 6" by itself?  That would explain why 
autoseq modes get their time reset. 
  Mike 
 


  
 
 --
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
wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

UM .. how else do you respond when using JT65/JT9 .. I don't use the 
buttons on TAB 2.  Double clicking on a response in the RX window when 
I'm calling CQ I agree with, that should start the QSO, but double 
clicking in the TX window should not as its a normal way to trigger the 
next dialog is a normal way to progress through the QSO.


Or am I missing something here?

Neil, KN3ILZ


On 7/4/2017 11:38 AM, Black Michael wrote:
When you say "double click" you are talking about the double-clicking 
the message in the RX Frequency window?  That will reset the start 
time as of right now.


de Mike W9MDB


*From:* Neil Zampella <ne...@techie.com>
*To:* wsjt-devel@lists.sourceforge.net
*Sent:* Monday, July 3, 2017 6:44 PM
*Subject:* Re: [wsjt-devel] Question about QSO Start & End Times

In reply to your other post .. yes, I'm using JTSDK.

Again, I'm using Tab 2, not Tab 1.  JT65/JT9 .. no auto sequencing.
Just double clicking to trigger the next response in the sequence.


On 7/3/2017 12:58 PM, Black Michael wrote:

Any double-clicks on lines will reset the start time to "unknown".

When the QSO transitions to TX 2 or TX 3 the start time gets set.
Any double clicks on lines after that would also reset the start 
time.  Tx 6 also resets start time.
If start time is not set by TX 2 or TX 3 then it will end up being 
the stop time.


And does autoseq sequence to "TX 6" by itself?  That would explain 
why autoseq modes get their time reset.


Mike






--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

As I mentioned before .. this was happening WAY before FT8 was 
introduced on non-autosequenced QSOs under JT65/JT9.


Neil, KN3ILZ


On 7/4/2017 11:24 AM, John Nelson wrote:

Mike,


And does autoseq sequence to "TX 6" by itself?  That would explain why autoseq 
modes get their time reset.

I suspect this may be the cause.  Activity is low today so I have not had the 
chance to test this.

If this is the case, I assume there should be a simple fix:  if (auto_seq) then 
don’t reset start time.

— John G4KLA




--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

When you say "double click" you are talking about the double-clicking the 
message in the RX Frequency window?  That will reset the start time as of right 
now.

de Mike W9MDB
  From: Neil Zampella <ne...@techie.com>
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Monday, July 3, 2017 6:44 PM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
   
 In reply to your other post .. yes, I'm using JTSDK.
 
 Again, I'm using Tab 2, not Tab 1.  JT65/JT9 .. no auto sequencing.    Just 
double clicking to trigger the next response in the sequence.   
  
 On 7/3/2017 12:58 PM, Black Michael wrote:
  
  Any double-clicks on lines will reset the start time to "unknown". 
  When the QSO transitions to TX 2 or TX 3 the start time gets set.   Any 
double clicks on lines after that would also reset the start time.  Tx 6 also 
resets start time. If start time is not set by TX 2 or TX 3 then it will end up 
being the stop time. 
  And does autoseq sequence to "TX 6" by itself?  That would explain why 
autoseq modes get their time reset. 
  Mike 
 
   

   --
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[John Nelson]

Mike,

> And does autoseq sequence to "TX 6" by itself?  That would explain why 
> autoseq modes get their time reset.

I suspect this may be the cause.  Activity is low today so I have not had the 
chance to test this.

If this is the case, I assume there should be a simple fix:  if (auto_seq) then 
don’t reset start time.

— John G4KLA
--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

In reply to your other post .. yes, I'm using JTSDK.

Again, I'm using Tab 2, not Tab 1.  JT65/JT9 .. no auto sequencing.
Just double clicking to trigger the next response in the sequence.



On 7/3/2017 12:58 PM, Black Michael wrote:

Any double-clicks on lines will reset the start time to "unknown".

When the QSO transitions to TX 2 or TX 3 the start time gets set.
Any double clicks on lines after that would also reset the start time. 
 Tx 6 also resets start time.
If start time is not set by TX 2 or TX 3 then it will end up being the 
stop time.


And does autoseq sequence to "TX 6" by itself?  That would explain why 
autoseq modes get their time reset.


Mike



*From:* Neil Zampella <ne...@techie.com>
*To:* wsjt-devel@lists.sourceforge.net
*Sent:* Monday, July 3, 2017 10:09 AM
*Subject:* Re: [wsjt-devel] Question about QSO Start & End Times

Mike,
1. I'm currently on r
2.  Tab 2, but normally a DBL click on either the CQ station or the 
one replying to my CQ

3.  The log time is the end time .. see attached.

The first is the DXKeeper entry, the second is the ALL.TXT entry, the 
third is the wsjtx.log, and the last is the relevant portion of the 
wsjtx_log.adi file.


Hope this helps.

Neil, KN3ILZ

On 7/3/2017 8:28 AM, Black Michael wrote:
I can't duplicate the problem on JT9/JT65.  I'm not sure what patch 
Bill is talking about since I can't find it in my sent folder.


So...what's different between your operation and mine?

#1 Version you running?
#2 Are you using Tab 1 or Tab 2 for QSO progression?
#3 When you log you are seeing the start=end time?  And the time is 
the time when you log it and not the start time?


Other than that there shouldn't be anything else affecting the QSO 
start time.


de Mike W9MDB






--
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
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

Any double-clicks on lines will reset the start time to "unknown".
When the QSO transitions to TX 2 or TX 3 the start time gets set.  Any double 
clicks on lines after that would also reset the start time.  Tx 6 also resets 
start time.If start time is not set by TX 2 or TX 3 then it will end up being 
the stop time.
And does autoseq sequence to "TX 6" by itself?  That would explain why autoseq 
modes get their time reset.
Mike

  From: Neil Zampella <ne...@techie.com>
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Monday, July 3, 2017 10:09 AM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
   
 Mike, 1.  I'm currently on r
 2.  Tab 2, but normally a DBL click on either the CQ station or the one 
replying to my CQ
 3.  The log time is the end time .. see attached.
 
 The first is the DXKeeper entry, the second is the ALL.TXT entry, the third is 
the wsjtx.log, and the last is the relevant portion of the wsjtx_log.adi file.
 
 Hope this helps.
 
 Neil, KN3ILZ
  
 On 7/3/2017 8:28 AM, Black Michael wrote:
  
  I can't duplicate the problem on JT9/JT65.  I'm not sure what patch Bill is 
talking about since I can't find it in my sent folder. 
  So...what's different between your operation and mine? 
  #1 Version you running?   #2 Are you using Tab 1 or Tab 2 for QSO 
progression? #3 When you log you are seeing the start=end time?  And the time 
is the time when you log it and not the start time? 
  Other than that there shouldn't be anything else affecting the QSO start 
time. 
  de Mike W9MDB 
  
  
  
   
 
 --
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
wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

So are you running JTSDK that maybe we could debug this on your system?Gotta' 
figure out why this is happening to you.
Mike

  From: Neil Zampella <ne...@techie.com>
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Monday, July 3, 2017 10:09 AM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
   
 Mike, 1.  I'm currently on r
 2.  Tab 2, but normally a DBL click on either the CQ station or the one 
replying to my CQ
 3.  The log time is the end time .. see attached.
 
 The first is the DXKeeper entry, the second is the ALL.TXT entry, the third is 
the wsjtx.log, and the last is the relevant portion of the wsjtx_log.adi file.
 
 Hope this helps.
 
 Neil, KN3ILZ
  
 On 7/3/2017 8:28 AM, Black Michael wrote:
  
  I can't duplicate the problem on JT9/JT65.  I'm not sure what patch Bill is 
talking about since I can't find it in my sent folder. 
  So...what's different between your operation and mine? 
  #1 Version you running?   #2 Are you using Tab 1 or Tab 2 for QSO 
progression? #3 When you log you are seeing the start=end time?  And the time 
is the time when you log it and not the start time? 
  Other than that there shouldn't be anything else affecting the QSO start 
time. 
  de Mike W9MDB 
  
  
  
   
 
 --
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
wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[John Nelson]

Mike,

>  Running r on Mac OSX 10.11.

This is compiled on a Mac.   I understand that JTDSK is a Windows/Linux 
installation package.

>  I can't seem to duplicate it here.

I assume you are running FT8 on Windows…?

I checked that start/stop times are correct with JT9.

I then tried FT8 with Auto-Seq disabled (need to be quick) and start/stop times 
are also correct.   Maybe this is a problem with auto-sequencing?

I’ll have a look at the code myself and see if I can spot something not right 
with start/stop times with auto-seq.

— John G4KLA



--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

Mike,

1.  I'm currently on r
2.  Tab 2, but normally a DBL click on either the CQ station or the one 
replying to my CQ

3.  The log time is the end time .. see attached.

The first is the DXKeeper entry, the second is the ALL.TXT entry, the 
third is the wsjtx.log, and the last is the relevant portion of the 
wsjtx_log.adi file.


Hope this helps.

Neil, KN3ILZ


On 7/3/2017 8:28 AM, Black Michael wrote:
I can't duplicate the problem on JT9/JT65.  I'm not sure what patch 
Bill is talking about since I can't find it in my sent folder.


So...what's different between your operation and mine?

#1 Version you running?
#2 Are you using Tab 1 or Tab 2 for QSO progression?
#3 When you log you are seeing the start=end time?  And the time is 
the time when you log it and not the start time?


Other than that there shouldn't be anything else affecting the QSO 
start time.


de Mike W9MDB






--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

I can't duplicate the problem on JT9/JT65.  I'm not sure what patch Bill is 
talking about since I can't find it in my sent folder.
So...what's different between your operation and mine?
#1 Version you running?  #2 Are you using Tab 1 or Tab 2 for QSO progression?#3 
When you log you are seeing the start=end time?  And the time is the time when 
you log it and not the start time?
Other than that there shouldn't be anything else affecting the QSO start time.
de Mike W9MDB



--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

But Mike,   that was happening to me when I was just JT65/JT9 !!

Neil, KN3ILZ


On 7/2/2017 11:28 PM, Black Michael wrote:
I"m not running FT8 so questiondo you see the "Next" buttons 
getting enabled when progressing on auto sequence?


I get the feeling they are not being set which means it would skip 
setting the QSO start time...and is why you set start=end since start 
never gets set.


de Mike W9MDB



*From:* John Nelson <j...@rmnjmn.co.uk>
*To:* Black Michael <mdblac...@yahoo.com>; WSJT software development 
<wsjt-devel@lists.sourceforge.net>

*Sent:* Sunday, July 2, 2017 2:42 PM
*Subject:* Re: [wsjt-devel] Question about QSO Start & End Times

Mike,


Like Neil I also notice that start time = end time in wsjtx.log and 
wsjtx_log.adi.  Running r on Mac OSX 10.11.


Extract from ALL.TXT

192430  0  0.6 1057 ~  CQ A92AA LL56
192430 -16  0.4  945 ~  EK6RSC YO2NAA KN05
192430  -9  0.6 1351 ~  MM0LGS CT1GVN IM67
1924  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92
192500  -2  0.3 1055 ~  CQ A92AA LL56
192500 -13  0.1 1210 ~  UR4UM YO2NAA KN05
192500  2  0.2 1431 ~  MM0LGS CT1GVN R-05
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92
192530  0  0.8 1057 ~  G4KLA A92AA -17
192530  5  0.2 1430 ~  MM0LGS CT1GVN 73
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+00
192600  1  0.3 1056 ~  G4KLA A92AA -17
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+01
192630  2  0.3 1056 ~  G4KLA A92AA -17
192630 -17  0.2 1675 ~  AK1P CT1GVN IM67
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+02
192700  1  0.3 1055 ~  G4KLA A92AA RRR
192700 -13  0.2 1674 ~  AK1P CT1GVN IM67
1927  Transmitting 14.079 MHz  FT8:  A92AA G4KLA 73
192730  2  0.3 1055 ~  G4KLA A92AA 73

Extract from wsjtx.log

2017-07-02,19:27,2017-07-02,19:27,A92AA,LL56,14.080055,FT8,+02,-17,20W,v1.7.1-dev 
r 10.11,Fawaz


Extract from wsjtx_log.adi

A92AA LL56 FT8 +02 
-17 20170702 1927 
20170702 1927 20m 
14.080055 G4KLA IO92ak 
20W v1.7.1-dev r 10.11 Fawaz 


— John G4KLA




--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[John Nelson]

Mike,

> I get the feeling they [Next buttons] are not being set 

Not correct.   Auto-seq is on;  the QSO proceeds as expected with Next buttons 
moving from 1, 3 to 5

1924  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92 Next button 1 set
192500  -2  0.3 1055 ~  CQ A92AA LL56
192500 -13  0.1 1210 ~  UR4UM YO2NAA KN05
192500  2  0.2 1431 ~  MM0LGS CT1GVN R-05   
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92  
192530  0  0.8 1057 ~  G4KLA A92AA -17  
192530  5  0.2 1430 ~  MM0LGS CT1GVN 73 
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+00  Next button  3 set
192600  1  0.3 1056 ~  G4KLA A92AA -17  
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+01  
192630  2  0.3 1056 ~  G4KLA A92AA -17  
192630 -17  0.2 1675 ~  AK1P CT1GVN IM67 
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+02  
192700  1  0.3 1055 ~  G4KLA A92AA RRR  
192700 -13  0.2 1674 ~  AK1P CT1GVN IM67 
1927  Transmitting 14.079 MHz  FT8:  A92AA G4KLA 73  Next button 5 set 

— John G4KLA
--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

I"m not running FT8 so questiondo you see the "Next" buttons getting 
enabled when progressing on auto sequence?
I get the feeling they are not being set which means it would skip setting the 
QSO start time...and is why you set start=end since start never gets set.
de Mike W9MDB

  From: John Nelson <j...@rmnjmn.co.uk>
 To: Black Michael <mdblac...@yahoo.com>; WSJT software development 
<wsjt-devel@lists.sourceforge.net> 
 Sent: Sunday, July 2, 2017 2:42 PM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
   
Mike,

Like Neil I also notice that start time = end time in wsjtx.log and 
wsjtx_log.adi.  Running r on Mac OSX 10.11.

Extract from ALL.TXT

192430  0  0.6 1057 ~  CQ A92AA LL56        
192430 -16  0.4  945 ~  EK6RSC YO2NAA KN05  
192430  -9  0.6 1351 ~  MM0LGS CT1GVN IM67  
1924  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92      
192500  -2  0.3 1055 ~  CQ A92AA LL56        
192500 -13  0.1 1210 ~  UR4UM YO2NAA KN05    
192500  2  0.2 1431 ~  MM0LGS CT1GVN R-05  
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92      
192530  0  0.8 1057 ~  G4KLA A92AA -17      
192530  5  0.2 1430 ~  MM0LGS CT1GVN 73    
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+00      
192600  1  0.3 1056 ~  G4KLA A92AA -17      
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+01      
192630  2  0.3 1056 ~  G4KLA A92AA -17      
192630 -17  0.2 1675 ~  AK1P CT1GVN IM67    
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+02      
192700  1  0.3 1055 ~  G4KLA A92AA RRR      
192700 -13  0.2 1674 ~  AK1P CT1GVN IM67    
1927  Transmitting 14.079 MHz  FT8:  A92AA G4KLA 73        
192730  2  0.3 1055 ~  G4KLA A92AA 73      

Extract from wsjtx.log

2017-07-02,19:27,2017-07-02,19:27,A92AA,LL56,14.080055,FT8,+02,-17,20W,v1.7.1-dev
 r 10.11,Fawaz

Extract from wsjtx_log.adi

A92AA LL56 FT8 +02 -17 
20170702 1927 20170702 1927 
20m 14.080055 G4KLA IO92ak 
20W v1.7.1-dev r 10.11 Fawaz 

— John G4KLA

   --
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[John Nelson]

Mike,

Like Neil I also notice that start time = end time in wsjtx.log and 
wsjtx_log.adi.   Running r on Mac OSX 10.11.

Extract from ALL.TXT

192430   0  0.6 1057 ~  CQ A92AA LL56
192430 -16  0.4  945 ~  EK6RSC YO2NAA KN05   
192430  -9  0.6 1351 ~  MM0LGS CT1GVN IM67   
1924  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92  
192500  -2  0.3 1055 ~  CQ A92AA LL56
192500 -13  0.1 1210 ~  UR4UM YO2NAA KN05
192500   2  0.2 1431 ~  MM0LGS CT1GVN R-05   
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA IO92  
192530   0  0.8 1057 ~  G4KLA A92AA -17  
192530   5  0.2 1430 ~  MM0LGS CT1GVN 73 
1925  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+00  
192600   1  0.3 1056 ~  G4KLA A92AA -17  
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+01  
192630   2  0.3 1056 ~  G4KLA A92AA -17  
192630 -17  0.2 1675 ~  AK1P CT1GVN IM67 
1926  Transmitting 14.079 MHz  FT8:  A92AA G4KLA R+02  
192700   1  0.3 1055 ~  G4KLA A92AA RRR  
192700 -13  0.2 1674 ~  AK1P CT1GVN IM67 
1927  Transmitting 14.079 MHz  FT8:  A92AA G4KLA 73
192730   2  0.3 1055 ~  G4KLA A92AA 73   

Extract from wsjtx.log

2017-07-02,19:27,2017-07-02,19:27,A92AA,LL56,14.080055,FT8,+02,-17,20W,v1.7.1-dev
 r 10.11,Fawaz

Extract from wsjtx_log.adi

A92AA LL56 FT8 +02 -17 
20170702 1927 20170702 1927 
20m 14.080055 G4KLA IO92ak 
20W v1.7.1-dev r 10.11 Fawaz 

— John G4KLA
--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

Bill & Mike,

don't know if you got this or not.  I saw it come back on the reflector, 
but didn't see any comments from y'all.


Thanks,

Neil, KN3ILZ


On 6/26/2017 10:36 PM, Neil Zampella wrote:


Sorry guys ... I'm been busy with other things that are interfering 
with my ham radio time .. :)


See attached ...

Neil, KN3ILZ


On 6/26/2017 1:00 PM, Black Michael wrote:

Nope...haven't heard anything from him.

de Mike W9MDB

*From:* Bill Somerville <g4...@classdesign.com>
*To:* wsjt-devel@lists.sourceforge.net
*Sent:* Monday, June 26, 2017 11:56 AM
*Subject:* Re: [wsjt-devel] Question about QSO Start & End Times

On 25/06/2017 13:40, Bill Somerville wrote:
> Hi Neil,
>
> can you provide a portion of your ALL.TXT file that covers one of the
> QSOs that are logged with equal start and end times please?

Nothing heard on this. Are you debugging this with Mike, W9MDB, off
list? If so I have a patch from Mike from a while back that I am still
reviewing which probably addresses this matter.


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
wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net>

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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

Sorry guys ... I'm been busy with other things that are interfering with 
my ham radio time .. :)


See attached ...

Neil, KN3ILZ


On 6/26/2017 1:00 PM, Black Michael wrote:

Nope...haven't heard anything from him.

de Mike W9MDB

*From:* Bill Somerville <g4...@classdesign.com>
*To:* wsjt-devel@lists.sourceforge.net
*Sent:* Monday, June 26, 2017 11:56 AM
*Subject:* Re: [wsjt-devel] Question about QSO Start & End Times

On 25/06/2017 13:40, Bill Somerville wrote:
> Hi Neil,
>
> can you provide a portion of your ALL.TXT file that covers one of the
> QSOs that are logged with equal start and end times please?

Nothing heard on this. Are you debugging this with Mike, W9MDB, off
list? If so I have a patch from Mike from a while back that I am still
reviewing which probably addresses this matter.


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
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




2017-06-25 02:48  7.075998 MHz  JT9+JT65
0248 -10  0.0 2576 @  CQ W5COV EM26
0248  -5 -0.2 1069 #  W1GQQ KK4UDN R-01
0248  -1  0.3 1185 #  5W1SA K3GAU EM89
0248  -1 -0.1 1387 #  CQ DX KJ4JEK EM65
0249 -18  0.1 1189 #  CQ N4LHY FM03
0249 -17  3.4 1329 #  AC0XR HK3JJH -07
0249  -1  0.4 1500 #  4A IL 73
0249 -17  0.2 1925 #  US8IAT EA9BO R-06
0249  -3  0.2 2116 #  HP1CDZ KJ4UZU R-09
0249 -10  1.4 2685 @  N0JAX KG5SYK EM20
0249  -9  0.2 2826 @  K1PLL K1BMW CM99
0249 -15  0.5 2414 #  CQ DX E73Y JN93
0249 -11  0.1 1666 #  CQ TI2AIM EJ79
0249 -23  0.2 1793 #  KH6F KJ6PWH R-17
0250  Transmitting 7.075998 MHz  JT65:  E73Y KN3ILZ FN00
0251 -13  1.3 2685 @  N0JAX KG5SYK R-19
0251 -10  0.2 2827 @  K1PLL K1BMW R-13
0251 -14  0.8 2414 #  VE2DSB E73Y -02
0251 -18  0.1  830 #  CQ N4LHY FM03
0251 -17  3.4 1329 #  AC0XR HK3JJH RR73
0251  -2  0.4 1500 #  CQ W9RNM EM57
0251 -20  0.1 1925 #  US8IAT EA9BO R-04
0251  -3  0.2 2116 #  HP1CDZ KJ4UZU 73
0251 -14  0.1 1667 #  CG3ON TI2AIM -14
0252  -2  0.1  628 #  ZP5DNB KM4ZS EM79
0252 -15  0.2 1013 #  VE2TRL OA4BUO -15
0252  -9  0.2 1272 #  HK3JJH W7AH DM42
0252  -8 -0.6 1501 #  W9RNM N8DVE EM79
0252 -13  0.5 2827 @  K1BMW K1PLL RR73
0252  -4  1.5 1671 #  TI2AIM KE4ZBI EM55
0252 -12  1.0 2973 @  CQ N5WXY EM40
0252 -22  0.3 1924 #  EA9BO W3NTP FM18
0252  -1  0.1 2119 #  HP1CDZ DE N8A
0252  -2  0.1 2414 #  E73Y VE2DSB R-04
0252 -11  0.1 1328 #  HK3JJH AC0XR 73
0252  -9  0.1 1496 #  CQ VA3MJR FN03
0252 -18  0.1 1665 #  TI2AIM CG3ON R-14
0252 -18 -0.4 2115 #  CQ HP1CDZ FJ09
0253  Transmitting 7.075998 MHz  JT9:  N5WXY KN3ILZ FN00
0254  -6  1.0 2972 @  KN3ILZ N5WXY -13
0254  -1  0.0  632 #  ZP5DNB 73LOTW
0254  -8  0.2 1013 #  CQ OA4BUO FH17
0254  -6  0.4 2827 @  CQ K1PLL FN42
0254  -5  0.2 1272 #  HK3JJH W7AH R-14
0254  -1  1.5 1671 #  CQ KE4ZBI EM55
0254 -15  0.3 1925 #  EA9BO W3NTP FM18
0254  -1  0.1 2119 #  HP1CDZ DE N8A
0254 -23  0.0 2328 #  BR6HZU BQ1ICY RM73
0254  -1 -0.0 2414 #  TU LOTW 73
0255  Transmitting 7.075998 MHz  JT9:  N5WXY KN3ILZ R-06
0256  -7  1.0 2972 @  KN3ILZ N5WXY 73
0256 -15 -0.1  853 #  N7MDW K7G DN55
0256 -10  0.1  865 #  CQ W6WAS CM96
0256 -10  0.2 1014 #  CQ OA4BUO FH17
0256  -4  0.2 1273 #  HK3JJH W7AH 73
0256  -7  0.4 2827 @  N4LHY K1PLL -17
0256  -1 -0.6 1675 #  CQ K8GLC EM88
0256 -13  0.3 1924 #  EA9BO W3NTP R-12
0256  -1  0.1 2123 #  HP1CDZ DE N8A
0256  -1  0.2 2618 #  BQ1ICY NK9B EL29
0256 -12  0.1 1295 #  VA3JLF AC0XR DN70
0256  -8 -0.2 1611 #  CQFD VE2CLM F
0257  Transmitting 7.075998 MHz  JT9:  N5WXY KN3ILZ 73
0258 -14  0.0  584 #  KS0CW KI7HEC DN17
0258 -18  0.2  627 #  W9RNM N7LFX CN82
0258 -14  0.1  865 #  LW2DOD W6WAS R-08
0258 -13  0.2 1014 #  CQ OA4BUO FH17
0258  -1  0.1 1329 #  CQ DX N8AWG EN81
0258 -10  0.6 1516 #  CQ TI2VLM EJ79
0258  -7  0.4 2827 @  N4LHY K1PLL RR73
0258  -3  1.5 1671 #  KI0IH KE4ZBI 73
0258 -22  0.3 1925 #  EA9BO W3NTP 73
0258 -11 -1.0 2115 #  UR4UT HP1CDZ -15
0258 -14  1.4 2412 #  E73Y WI6K DM14
0258 -12 -0.2 1612 #  CQFD VE2CLM F
0258 -22  0.2 2326 #  CQ KJ6PWH CM87
0259  -3  0.8  442 #  CQ KG5LWL EM35
0259  -1  0.3  584 #  PD7RF KS0CW -19
0259 -13  0.1  853 #  K7G N7MDW -15
0259  -1  0.3 1013 #  OA4BUO NO4J EL99
0259  -2  0.2 1221 #  LZ1SJ KU4NZ EM53
0259  -1  1.5 1322 #  N8AWG K8GLC EM88
0259  -1  0.2 1515 #  TI2VLM N4WXB EM64
0259  -4  0.2 1672 #  KE4ZBI KI0IH 73
0259 -17  0.1 1925 #  RW3ADB EA9BO R-19
0259  -8  1.0 2603 @  KC3BVL N5WXY EM40
0259  -8  0.4 2414 #  CQ DX E73Y JN93
0259 -16  0.1 2685 @  N0JAX VA3MJR R-05
0259 -18  0.1 2827 @  K1PLL N4LHY 73
0259 -10  0.4  627 #  N7LFX W9RNM -03
0259  -6  0.1 1171 #  LZ1SJ VE2DSB FN35
0259 -10  0.4 1514 #  TI2VLM WD5EED EM44
0259  -9 -0.6 1608 #  VE2CLM K6XJ DM06

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

Nope...haven't heard anything from him.

de Mike W9MDB
  From: Bill Somerville <g4...@classdesign.com>
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Monday, June 26, 2017 11:56 AM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
   
On 25/06/2017 13:40, Bill Somerville wrote:
> Hi Neil,
>
> can you provide a portion of your ALL.TXT file that covers one of the 
> QSOs that are logged with equal start and end times please? 

Nothing heard on this. Are you debugging this with Mike, W9MDB, off 
list? If so I have a patch from Mike from a while back that I am still 
reviewing which probably addresses this matter.

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
wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Bill Somerville]

On 25/06/2017 13:40, Bill Somerville wrote:

Hi Neil,

can you provide a portion of your ALL.TXT file that covers one of the 
QSOs that are logged with equal start and end times please? 


Nothing heard on this. Are you debugging this with Mike, W9MDB, off 
list? If so I have a patch from Mike from a while back that I am still 
reviewing which probably addresses this matter.


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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Bill Somerville]

On 25/06/2017 13:36, Neil Zampella wrote:
Both the ADI file, and the WSJT.LOG file show the same thing.  Here 
are screen caps showing the latest QSOs. 


Hi Neil,

can you provide a portion of your ALL.TXT file that covers one of the 
QSOs that are logged with equal start and end times please?


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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Neil Zampella]

Mike,

Both the ADI file, and the WSJT.LOG file show the same thing. Here are 
screen caps showing the latest QSOs.


The interesting part is they NEVER showed a different end time, they 
always show the same time as the beginning starting on Jan 18th 2017, 
when I compiled and installed a version back then.


Neil, KN3ILZ


On 6/25/2017 8:01 AM, Black Michael wrote:

I'm running 7735 and times are correct.
Do you have entries from the ADI file that show the problem?
Happened more than once?

de Mike W9MDB


*From:* Neil Zampella 
*To:* wsjt-devel@lists.sourceforge.net
*Sent:* Saturday, June 24, 2017 11:32 PM
*Subject:* [wsjt-devel] Question about QSO Start & End Times

Hi all,

for some reason tonight, I took a look at the LOG window as I was
logging a QSO, and noticed that the start and end times were exactly the
same.Now as I recall the system used to log the actual start and end
times, I wasn't sure if this was due to a change in WSJT-X, or JT-Alert.

I went back through the log, and noticed that I must have compiled a new
executable of v1.7.1 between 13:34 and 16:35 GMT on April 22.  As the
start & end times were different before that compile, and the same
after.  I'm currently using r7735.

Has the code changed in WSJT-X, or should I look elsewhere?


Thanks,

Neil Zampella, KN3ILZ




--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question about QSO Start & End Times

[Black Michael via wsjt-devel]

I'm running 7735 and times are correct.Do you have entries from the ADI file 
that show the problem?Happened more than once?
de Mike W9MDB

  From: Neil Zampella 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Saturday, June 24, 2017 11:32 PM
 Subject: [wsjt-devel] Question about QSO Start & End Times
   
Hi all,

for some reason tonight, I took a look at the LOG window as I was 
logging a QSO, and noticed that the start and end times were exactly the 
same.    Now as I recall the system used to log the actual start and end 
times, I wasn't sure if this was due to a change in WSJT-X, or JT-Alert.

I went back through the log, and noticed that I must have compiled a new 
executable of v1.7.1 between 13:34 and 16:35 GMT on April 22.  As the 
start & end times were different before that compile, and the same 
after.  I'm currently using r7735.

Has the code changed in WSJT-X, or should I look elsewhere?


Thanks,

Neil Zampella, KN3ILZ


--
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
wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel