Re: [wsjt-devel] wrong time logged
Jim- Had the same thing happen to me once. Bill W2PKY On Sun, Jan 13, 2019 at 10:17 AM Jim Preston wrote: > Al, > > I had something similar happen during the RTTY RU. In my case, it > happened when the previous QSO was not complete, therefore not logged. > The time given for the next QSO was actually the time for the previous, > not logged, QSO. Fortunately, I noticed it and was able to make > corrections. > > 73, > > Jim N6VH > > > On 1/11/2019 8:41 AM, Al wrote: > > (WSJT-X V2.0.0, W 10 ) > > This may have been reported before ?? > > > > I was on earlier today and made several 80 contacts ending at 1319. > > I left the radio running and came back at ~16:17 and changed bands to > 17m. > > My first contact on 17m was at 16:19 but the logs recorded that contact > > time at 13:21. > > > > AL, K0VM > > > > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wrong time logged
Al, I had something similar happen during the RTTY RU. In my case, it happened when the previous QSO was not complete, therefore not logged. The time given for the next QSO was actually the time for the previous, not logged, QSO. Fortunately, I noticed it and was able to make corrections. 73, Jim N6VH On 1/11/2019 8:41 AM, Al wrote: (WSJT-X V2.0.0, W 10 ) This may have been reported before ?? I was on earlier today and made several 80 contacts ending at 1319. I left the radio running and came back at ~16:17 and changed bands to 17m. My first contact on 17m was at 16:19 but the logs recorded that contact time at 13:21. AL, K0VM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wrong time logged
We need to add one statement here probably
void MainWindow::on_dxCallEntry_textChanged (QString const& call){ m_hisCall =
call; statusChanged(); statusUpdate ();}
Tovoid MainWindow::on_dxCallEntry_textChanged (QString const& call){ m_hisCall
= call; statusChanged(); statusUpdate (); set_dateTimeQSO(-1);}
On Friday, January 11, 2019, 12:47:53 PM CST, Don AA5AU
wrote:
This happens to me all the time. When you stop using WSJT-X, then go back a
few hours later, many times it logs the next contact with a start time of when
you last made a contact a few hours earlier. The end time is correct. The QSOs
usually get flagged by eQSL as not being in the log. That's how I discovered it.
I'm using JTAlert and DXKeeper, but this has been an issue for quite some time.
I know to either restart WSJT-X after a pause, or look at the first contact I
log after a period of inactivity.
Seems to be an issue with WSJT-X. I thought it was a known issue.
Don AA5AU
On Friday, January 11, 2019, 10:43:53 AM CST, Al wrote:
(WSJT-X V2.0.0, W 10 )
This may have been reported before ??
I was on earlier today and made several 80 contacts ending at 1319.
I left the radio running and came back at ~16:17 and changed bands to 17m.
My first contact on 17m was at 16:19 but the logs recorded that contact time
at 13:21.
AL, K0VM
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wrong time logged
FWIW I am running both WSJT-X v2 and JTAlert 2.12.10. I rarely shut down either program and my computer and rig run 24/7. I never have this problem. Of course saying it just now may cause it to start (Murphy’s Law). __ Dan – K4SHQ From: m...@handgunrepairshop.com [mailto:m...@handgunrepairshop.com] Sent: Friday, January 11, 2019 1:04 PM To: k...@arrl.net; WSJT software development Subject: Re: [wsjt-devel] wrong time logged I have also experienced this logging start time issue many times, at least back as far as v1.8, usually after an aborted/incomplete or abandoned QSO. I have no idea why the previously aborted QSO start time does not clear when the Esc. or F4 key is used to clear the QSO from the DX Call & DX Grid boxes. It does seem a bit ironic to me that a program that depends on 1 second time correctness for decodes, and always correctly logs the Tx frequency to 1 Hz accuracy, has a problem keeping up with the actual current QSO start time? I am not a computer programmer, but apparently fixing this ongoing logging issue is more than the dev team wants to deal with. Having said that, I do want to express my thanks to all the dev team for this software. My log has grown over 4,000 more QSOs since beginning to use WSJT-X! 73 de KV4ZY, Doug Original Message Subject: [wsjt-devel] wrong time logged From: Al mailto:k...@arrl.net>> Date: Fri, January 11, 2019 11:41 am To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> (WSJT-X V2.0.0, W 10 ) This may have been reported before ?? I was on earlier today and made several 80 contacts ending at 1319. I left the radio running and came back at ~16:17 and changed bands to 17m. My first contact on 17m was at 16:19 but the logs recorded that contact time at 13:21. AL, K0VM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wrong time logged
I have also experienced this logging start time issue many times, at least back as far as v1.8, usually after an aborted/incomplete or abandoned QSO. I have no idea why the previously aborted QSO start time does not clear when the Esc. or F4 key is used to clear the QSO from the DX Call & DX Grid boxes.It does seem a bit ironic to me that a program that depends on 1 second time correctness for decodes, and always correctly logs the Tx frequency to 1 Hz accuracy, has a problem keeping up with the actual current QSO start time?I am not a computer programmer, but apparently fixing this ongoing logging issue is more than the dev team wants to deal with.Having said that, I do want to express my thanks to all the dev team for this software. My log has grown over 4,000 more QSOs since beginning to use WSJT-X!73 de KV4ZY, Doug Original Message Subject: [wsjt-devel] wrong time logged From: Al <k...@arrl.net> Date: Fri, January 11, 2019 11:41 am To: wsjt-devel@lists.sourceforge.net (WSJT-X V2.0.0, W 10 ) This may have been reported before ?? I was on earlier today and made several 80 contacts ending at 1319. I left the radio running and came back at ~16:17 and changed bands to 17m. My first contact on 17m was at 16:19 but the logs recorded that contact time at 13:21. AL, K0VM___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] wrong time logged
(WSJT-X V2.0.0, W 10 ) This may have been reported before ?? I was on earlier today and made several 80 contacts ending at 1319. I left the radio running and came back at ~16:17 and changed bands to 17m. My first contact on 17m was at 16:19 but the logs recorded that contact time at 13:21. AL, K0VM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wrong time logged
FWIW - Just yesterday, it was brought to my attention that an FT8 contact using RC3 was logged with the wrong time. I found the contact was logged from WSJT-X via JTAlert into DXKeeper with the wrong start time. The end time was correct. Unfortunately I have no details of how it could have happened. I had stopped operating and an hour later I restarted. The first contact I made after restarting had a start time of when I stopped an hour earlier. Don AA5AU From: m...@handgunrepairshop.com [mailto:m...@handgunrepairshop.com] Sent: Friday, November 16, 2018 10:38 PM To: WSJT software development Subject: Re: [wsjt-devel] wrong time logged Hi all, First a disclaimer, I have no programming knowledge, or any clue to the solution. My setup is V2.0.0-rc4 on Windows 10 Pro, JTAlert feeding Log4OM & OmniRig for CAT control, SignaLink USB, TS-2000. I am also seeing issues with wrong QSO time logged, particularly after using F4 or Esc keys to abort a QSO that did not complete. I seem to recall similar issues sporadically with previous versions as well. I am using copy/paste to include text from the RX Frequency frame and wsjtx.log file below. 223345 Tx 2498 ~ CQ KV4ZY EN91 223400 -16 0.1 2499 ~ KV4ZY WD5DHK EM12 223400 -4 0.0 2716 ~ KV4ZY AJ4F EL29 223419 Tx 2498 ~ WD5DHK KV4ZY -16 223430 -13 0.2 2499 ~ KV4ZY WD5DHK R-07 223445 Tx 2498 ~ WD5DHK KV4ZY RR73 223500 -17 0.2 2499 ~ KV4ZY WD5DHK 73 223516 Tx 2498 ~ AJ4F KV4ZY -04 223530 -9 0.1 2716 ~ VA7VJ AJ4F EL29 223545 Tx 2498 ~ AJ4F KV4ZY -04 223615 Tx 2498 ~ AJ4F KV4ZY -04 223630 -8 0.1 2716 ~ KV4ZY AJ4F -06 223700 -7 0.1 2716 ~ KV4ZY AJ4F -06 223730 -3 0.0 2715 ~ KV4ZY AJ4F -06 022315 Tx 2080 ~ CQ KV4ZY EN91 022330 -12 0.1 2080 ~ KV4ZY WA4GLH EM75 022345 Tx 2080 ~ WA4GLH KV4ZY -12 022415 Tx 2080 ~ WA4GLH KV4ZY -12 022445 Tx 2080 ~ WA4GLH KV4ZY -12 022500 -17 0.1 2080 ~ KV4ZY WA4GLH R-05 022515 Tx 2080 ~ WA4GLH KV4ZY RR73 022545 Tx 2080 ~ CQ KV4ZY EN91 When the QSO with WD5HDK ended I double clicked on AJ4F to try to pick him up. He was already calling VA7VJ and did not respond to my calls, I can not recall whether I used F4 or Esc to abort the QSO. Just then the XYL arrived home from getting groceries so I had to leave the operating position. XYL & I had supper & watched a DVD movie before I returned to operating position around 02:20Z. The next QSO with WA4GLH was logged with the incorrect start time as shown in the resulting wsjtx.log entries: 2018-11-16,22:34:15,2018-11-16,22:34:45,WD5DHK,EM12,14.076498,FT8,-16,-07,20,TS-2000 & H-6BTV, 2018-11-16,22:35:15,2018-11-17,02:25:15,WA4GLH,EM75,7.076080,FT8,-12,-05,20,TS-2000 & H-6BTV, I use JTAlert to send logging to Log4OM automatically. Log4OM uses the start times to sort the entries, thus the 11-17-18 02:23 QSO was logged as 11-16-18 22:35. As many others probably do, I have Log4OM set up to automatically upload QSOs to online logs like QRZ, EQSL, etc. Wrong day and 4 hours difference in QSO time will not match up very well for verifications. By the way I have not had any issues with losing the check on auto seq & call 1st when changing bands as some others have reported. 73 de Doug KV4ZY Original Message ---- Subject: [wsjt-devel] wrong time logged From: Al Date: Wed, November 14, 2018 2:54 pm To: wsjt-devel@lists.sourceforge.net ( RC4 ) 2018-11-14,19:12:15,2018-11-14,19:17:00,K1HK,FN42,14.076397,FT8,-01,+06,40,FT8 Sent: -01 Rcvd: +06, 2018-11-14,19:17:33,2018-11-14,19:42:00,W8NNX,EL98,14.076377,FT8,-09,+06,40,FT8 Sent: -09 Rcvd: +06, In the contact with W8NNX the start time should have been 19:41:15 .. After the QSO with K1HK I called CQ for 3 minutes.. and then was idles until again calling QSO at 19:41 when W8NNX answered. AL, K0VM _ _ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wrong time logged
Hi all,First a disclaimer, I have no programming knowledge, or any clue to the solution. My setup is V2.0.0-rc4 on Windows 10 Pro, JTAlert feeding Log4OM & OmniRig for CAT control, SignaLink USB, TS-2000.I am also seeing issues with wrong QSO time logged, particularly after using F4 or Esc keys to abort a QSO that did not complete. I seem to recall similar issues sporadically with previous versions as well. I am using copy/paste to include text from the RX Frequency frame and wsjtx.log file below.223345 Tx 2498 ~ CQ KV4ZY EN91 223400 -16 0.1 2499 ~ KV4ZY WD5DHK EM12 223400 -4 0.0 2716 ~ KV4ZY AJ4F EL29 223419 Tx 2498 ~ WD5DHK KV4ZY -16 223430 -13 0.2 2499 ~ KV4ZY WD5DHK R-07 223445 Tx 2498 ~ WD5DHK KV4ZY RR73 223500 -17 0.2 2499 ~ KV4ZY WD5DHK 73 223516 Tx 2498 ~ AJ4F KV4ZY -04 223530 -9 0.1 2716 ~ VA7VJ AJ4F EL29 223545 Tx 2498 ~ AJ4F KV4ZY -04 223615 Tx 2498 ~ AJ4F KV4ZY -04 223630 -8 0.1 2716 ~ KV4ZY AJ4F -06 223700 -7 0.1 2716 ~ KV4ZY AJ4F -06 223730 -3 0.0 2715 ~ KV4ZY AJ4F -06 022315 Tx 2080 ~ CQ KV4ZY EN91 022330 -12 0.1 2080 ~ KV4ZY WA4GLH EM75 022345 Tx 2080 ~ WA4GLH KV4ZY -12 022415 Tx 2080 ~ WA4GLH KV4ZY -12 022445 Tx 2080 ~ WA4GLH KV4ZY -12 022500 -17 0.1 2080 ~ KV4ZY WA4GLH R-05 022515 Tx 2080 ~ WA4GLH KV4ZY RR73 022545 Tx 2080 ~ CQ KV4ZY EN91When the QSO with WD5HDK ended I double clicked on AJ4F to try to pick him up. He was already calling VA7VJ and did not respond to my calls, I can not recall whether I used F4 or Esc to abort the QSO. Just then the XYL arrived home from getting groceries so I had to leave the operating position. XYL & I had supper & watched a DVD movie before I returned to operating position around 02:20Z. The next QSO with WA4GLH was logged with the incorrect start time as shown in the resulting wsjtx.log entries:2018-11-16,22:34:15,2018-11-16,22:34:45,WD5DHK,EM12,14.076498,FT8,-16,-07,20,TS-2000 & H-6BTV,2018-11-16,22:35:15,2018-11-17,02:25:15,WA4GLH,EM75,7.076080,FT8,-12,-05,20,TS-2000 & H-6BTV,I use JTAlert to send logging to Log4OM automatically. Log4OM uses the start times to sort the entries, thus the 11-17-18 02:23 QSO was logged as 11-16-18 22:35. As many others probably do, I have Log4OM set up to automatically upload QSOs to online logs like QRZ, EQSL, etc. Wrong day and 4 hours difference in QSO time will not match up very well for verifications.By the way I have not had any issues with losing the check on auto seq & call 1st when changing bands as some others have reported. 73 de Doug KV4ZY Original Message ---- Subject: [wsjt-devel] wrong time logged From: Al <k...@arrl.net> Date: Wed, November 14, 2018 2:54 pm To: wsjt-devel@lists.sourceforge.net ( RC4 ) 2018-11-14,19:12:15,2018-11-14,19:17:00,K1HK,FN42,14.076397,FT8,-01,+06,40,FT8 Sent: -01 Rcvd: +06, 2018-11-14,19:17:33,2018-11-14,19:42:00,W8NNX,EL98,14.076377,FT8,-09,+06,40,FT8 Sent: -09 Rcvd: +06, In the contact with W8NNX the start time should have been 19:41:15 .. After the QSO with K1HK I called CQ for 3 minutes.. and then was idles until again calling QSO at 19:41 when W8NNX answered. AL, K0VM___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] wrong time logged
( RC4 ) 2018-11-14,19:12:15,2018-11-14,19:17:00,K1HK,FN42,14.076397,FT8,-01,+06,40,FT8 Sent: -01 Rcvd: +06, 2018-11-14,19:17:33,2018-11-14,19:42:00,W8NNX,EL98,14.076377,FT8,-09,+06,40,FT8 Sent: -09 Rcvd: +06, In the contact with W8NNX the start time should have been 19:41:15 .. After the QSO with K1HK I called CQ for 3 minutes.. and then was idles until again calling QSO at 19:41 when W8NNX answered. AL, K0VM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
