Topics

Why these errors?

Rich - K1HTV
 

With over 147K QSOs in my DXKeeper log, things are working great. However, I wonder why, after running Sync LoTW QSLs, processing 35 QSLs there were 35 errors. Here is the report received: All of the QSOs listed below appear in the K1HTV log, so why does each line say "no matching QSO in log"?
for k1htv
Query:
    OWNCALL: K1HTV
   QSL ONLY: YES
  QSL SINCE: 2019-05-24 00:57:05

<PROGRAMID:4>LoTW
<APP_LoTW_LASTQSL:19>2019-05-24 20:03:03

<APP_LoTW_NUMREC:2>35

        Date      Time           Call    Band      Mode       Station Call    Result

  2019-05-24  19:32:00          N3CAL      6M       FT8              K1HTV    no matching QSO in log
  2019-05-24  19:24:00          K4JKB      6M       FT8              K1HTV    no matching QSO in log
  2019-04-30  15:33:00           RG3R     20M      DATA              K1HTV    no matching QSO in log
  2019-04-30  12:31:00           S52D     20M      DATA              K1HTV    no matching QSO in log
  2019-05-14  00:27:00           K1VI     40M      DATA              K1HTV    no matching QSO in log
  2019-05-23  17:39:00           KB6C     17M       FT8              K1HTV    no matching QSO in log
  2019-03-17  02:26:38          PY2KJ     40M        CW              K1HTV    no matching QSO in log
  2019-05-09  00:46:00           W4GO     40M      DATA              K1HTV    no matching QSO in log
  2019-05-05  23:05:00          PY5EJ     40M      DATA              K1HTV    no matching QSO in log
  2019-05-23  21:06:00          PY6ZL     20M       FT8              K1HTV    no matching QSO in log
  2019-05-24  01:19:00         MM0HVU     60M       FT8              K1HTV    no matching QSO in log
  2019-05-09  00:56:00         WA4MIT     40M      DATA              K1HTV    no matching QSO in log
  2019-05-09  00:21:00         WA3ZSC     40M      DATA              K1HTV    no matching QSO in log
  2019-04-30  00:12:00           N2RJ     80M      DATA              K1HTV    no matching QSO in log
  2019-05-24  01:22:00          LU1YT     60M       FT8              K1HTV    no matching QSO in log
  2019-04-30  11:27:00         RX3ASP     20M      DATA              K1HTV    no matching QSO in log
  2019-04-30  11:33:00          ES1QV     20M      DATA              K1HTV    no matching QSO in log
  2019-05-23  17:20:00          WK0DX     17M       FT8              K1HTV    no matching QSO in log
  2019-05-24  01:35:00          W8DSI     60M       FT8              K1HTV    no matching QSO in log
  2019-05-24  01:39:00          AC8TO     60M       FT8              K1HTV    no matching QSO in log
  2019-05-24  01:18:00         MM0EAX     60M       FT8              K1HTV    no matching QSO in log
  2019-05-24  01:34:00          K8DID     60M       FT8              K1HTV    no matching QSO in log
  2019-05-24  01:26:00         VE3MZD     60M       FT8              K1HTV    no matching QSO in log
  2019-05-24  01:30:00         VE3OTL     60M       FT8              K1HTV    no matching QSO in log
  2018-12-01  20:51:00          KD0XD     20M       FT8              K1HTV    no matching QSO in log
  2018-11-10  22:41:00          KD0XD     60M       FT8              K1HTV    no matching QSO in log
  2019-05-23  21:29:00          AA5AT     30M       FT8              K1HTV    no matching QSO in log
  2018-04-25  03:13:00         VK2SPB     20M       FT8              K1HTV    no matching QSO in log
  2018-06-21  23:49:00         JR1LZK      6M       FT8              K1HTV    no matching QSO in log
  2019-05-23  21:34:00         OE3UKW     30M       FT8              K1HTV    no matching QSO in log
  2019-05-23  21:33:00          W5VMA     30M       FT8              K1HTV    no matching QSO in log
  2019-05-23  11:35:00         WH6EXS     40M       FT8              K1HTV    no matching QSO in log
  2019-05-23  17:31:00           NH6Y     17M       FT8              K1HTV    no matching QSO in log
  2019-05-23  17:13:00          A41ZZ     17M       FT8              K1HTV    no matching QSO in log
  2019-05-05  22:07:00         IZ5HNI     40M      DATA              K1HTV    no matching QSO in log

LotW operations: 35 QSLs processed, 0 log entries updated, 35 errors

No new confirmations of anything needed and previously unconfirmed

73,
Rich - K1HTV

Dave AA6YQ
 

+ AA6YQ comments below

On Fri, May 24, 2019 at 01:57 PM, Rich - K1HTV wrote:

With over 147K QSOs in my DXKeeper log, things are working great. However, I wonder why, after running Sync LoTW QSLs, processing 35 QSLs there were 35 errors. Here is the report received: All of the QSOs listed below appear in the K1HTV log, so why does each line say "no matching QSO in log"?
for k1htv

+ Let's drill down on the first QSO in your list of "no matching QSO in log" errors:

 2019-05-24  19:32:00          N3CAL      6M       FT8              K1HTV    no matching QSO in log

+ In DXKeeper, please locate your logged QSO with N3CAL on 2019-05-24. What "QSO Begin" time is logged with this QSO?

+ Was this QSO logged by DXKeeper, or by another application?

+ Was this QSO submitted to LoTW by DXKeeper, or by another application?

       73,

                Dave, AA6YQ

 

 

 

Rich - K1HTV
 

Dave,
  The start time for the QSO is 19:32, the end time is 19:33 both on the same date.
This and all of my QSOs are logged exclusively by DXkeeper.
All QSOs are uploaded to LOTW and to eQSL using DXKeeper.

I'm wondering if, after uploading the 35 QSOs, that I clicked on Sync LoTW QSLs before clicking on Sync LoTW QSOs. Would that cause the error message that I received?
73,
Rich - K1HTV

Dave AA6YQ
 

+ AA6YQ comments below


On Fri, May 24, 2019 at 03:32 PM, Rich - K1HTV wrote:

The start time for the QSO is 19:32, the end time is 19:33 both on the same date.
+ In the Options panel on the Configuration window's General tab, check the "Display seconds in date/time fields" box. Having done that, what does DXKeeper show as the start time for the QSO?
This and all of my QSOs are logged exclusively by DXkeeper.
All QSOs are uploaded to LOTW and to eQSL using DXKeeper.

I'm wondering if, after uploading the 35 QSOs, that I clicked on Sync LoTW QSLs before clicking on Sync LoTW QSOs. Would that cause the error message that I received?

+ No, it would not. You can invoke those functions in either order.

+ If the QSOs in questions were logged in DXKeeper and submitted to LotW from DXKeeper, the typical cause of "no matching QSO in log" is "QSO was modified after submitting to LoTW". 

+ I'm focusing first on the QSO begin time because the "QSO Begin" time of every QSO in your "no matching QSO in log" list has its seconds set to 00, which seems highly unlikely.

       73,

             Dave, AA6YQ

Rich - K1HTV
 

Dave,
   ALL of my QSOs in DXKeeper are entered with the seconds option turned OFF. I turned it on as you suggested and checked and the N3CAL QSO in question has a start time of 19:32:00 and end time of 19:33:00. I checked QSO made over the past 2 months and found that prior to March 18, all QSOs had their seconds entered as actual time. Since then the seconds entries for all QSOs have been :00.  

After turning on the seconds config option in DXKeeper I made an FT8 QSO . When the QSO was completed, the WSJT-X log box that popped up indicated exact seconds for both start and end times.  The QSO was sent to DXKeeper, as usual via JTAlert. However, when I checked the QSO in DXKeeper, I found that the start time was 03:04:00 and the end time was 03:05:00. The minutes were correct, but the seconds were set to :00.

Ideas?

73,
Rich - K1HTV

Dave AA6YQ
 

+ AA6YQ comments below

ALL of my QSOs in DXKeeper are entered with the seconds option turned OFF. I turned it on as you suggested and checked and the N3CAL QSO in question has a start time of 19:32:00 and end time of 19:33:00. I checked QSO made over the past 2 months and found that prior to March 18, all QSOs had their seconds entered as actual time. Since then the seconds entries for all QSOs have been :00.

After turning on the seconds config option in DXKeeper I made an FT8 QSO . When the QSO was completed, the WSJT-X log box that popped up indicated exact seconds for both start and end times. The QSO was sent to DXKeeper, as usual via JTAlert. However, when I checked the QSO in DXKeeper, I found that the start time was 03:04:00 and the end time was 03:05:00. The minutes were correct, but the seconds were set to :00.

+ The FT8 QSOs I've logged in the past via JT-Alert all specify hours, minutes, and seconds in their "begin" and "end" items. Is there now an option in JT-Alert to log QSOs with the seconds in start and end times set to 00?

+ DXKeeper expects that when LoTW reports information about a QSO (because you invoked "Sync LoTW QSOs", "Sync LoTW QSLs", or "Update from LoTW", that the callsign, date, time, frequency, band, and mode reported by LoTW will all *exactly* match what's in your log..

+ If a QSO is submitted to LoTW with a "begin" item that specifies the exact seconds but logged to DXKeeper with a "begin" item whose seconds are set to 00, then the result will be "no matching QSO in log".

73,

Dave, AA6YQ

Rich - K1HTV
 

Dave,
  You nailed it!. For some reason, the JTAlert option to log seconds in the time_on and time_off was unchecked. I turned the option back on and now the seconds are being logged in DXKeeper. Many thanks for solving this problem.

73,
Rich - K1HTV

Dave AA6YQ
 

+ AA6YQ comments below

You nailed it!. For some reason, the JTAlert option to log seconds in the time_on and time_off was unchecked. I turned the option back on and now the seconds are being logged in DXKeeper. Many thanks for solving this problem.

+ What version of JTAlert are you running, Rich?

73,

Dave, AA6YQ

Danny Douglas
 

I cannot remember the exact numbers, but when LOTW started up, they advised us that there was give or take time of 10 or 20 minutes. Ive never worried about an exact number, no matter how I uploaded to them, and the only time I have seen them turn a match down was when I was doing the paper to LOTW logging, which took months. I have never worried about seconds, but on occasion I missed typing in the correct hour or even day of a past contact. When those bounced, I took another look at the paper logs and would discover I was indeed off an hour, or several minutes, when I typed them, or maybe even when a clock wasn't right on either my, or the other operators end. I would find the contact, and change my log to whatever they said theirs was, and it would go through. I certainly am not anal retentive about it, and frankly dont care if I am 5 minutes off. I can still remember the days of having an old wind up clock setting on the desk. Hey, even freqs. When I started this, back in the 50s, few of us even had a rig that was correct to even 1 KHZ, and many of them were only marked ever 5 or 10 KC on the main dial. I still actually prefer the old BAND logging. 14.025 or 14.272 are still 20 meters. And I have thousands of contacts logged that way.

It scares me to think that 1 or 2 seconds difference between my log, and the other stations log would result in a reject of a QSO. I would be in a whole world of hurt , because NONE of my contacts in DXKeeper have seconds listed, even to right now. Read your note the third time, and am hoping it means if you use exact seconds one time, and not the second, that is the only time they will reject the contact. I am guessing that if we find we made a mistake in the first submission, and change something, we best have the times set for the same seconds, or if we dont use seconds at all, we are free and clear.

N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On May 27, 2019 at 11:29 PM Dave AA6YQ <@AA6YQ> wrote:


+ AA6YQ comments below

ALL of my QSOs in DXKeeper are entered with the seconds option turned OFF. I turned it on as you suggested and checked and the N3CAL QSO in question has a
+ If a QSO is submitted to LoTW with a "begin" item that specifies the exact seconds but logged to DXKeeper with a "begin" item whose seconds are set to 00, then the result will be "no matching QSO in log".

73,

Dave, AA6YQ




Dave AA6YQ
 

+ AA6YQ comments below

I cannot remember the exact numbers, but when LOTW started up, they advised us that there was give or take time of 10 or 20 minutes. Ive never worried about an exact number, no matter how I uploaded to them, and the only time I have seen them turn a match down was when I was doing the paper to LOTW logging, which took months. I have never worried about seconds, but on occasion I missed typing in the correct hour or even day of a past contact. When those bounced, I took another look at the paper logs and would discover I was indeed off an hour, or several minutes, when I typed them, or maybe even when a clock wasn't right on either my, or the other operators end. I would find the contact, and change my log to whatever they said theirs was, and it would go through. I certainly am not anal retentive about it, and frankly dont care if I am 5 minutes off. I can still remember the days of having an old wind up clock setting on the desk. Hey, even freqs. When I started this, back in the 50s, few of us even had a rig that was correct to even 1 KHZ, and many of them were only marked ever 5 or 10 KC on the main dial. I still actually prefer the old BAND logging. 14.025 or 14.272 are still 20 meters. And I have thousands of contacts logged that way.

It scares me to think that 1 or 2 seconds difference between my log, and the other stations log would result in a reject of a QSO. I would be in a whole world of hurt , because NONE of my contacts in DXKeeper have seconds listed, even to right now. Read your note the third time, and am hoping it means if you use exact seconds one time, and not the second, that is the only time they will reject the contact. I am guessing that if we find we made a mistake in the first submission, and change something, we best have the times set for the same seconds, or if we dont use seconds at all, we are free and clear.

+ The discussion in this thread has nothing to do with matching what your QSO partner submitted in order to obtain a confirmation.

+ DXKeeper expects that when LoTW reports information about a QSO you submitted to LoTW, that the reported information -- callsign, date, time, band, mode, propagation mode, satellite name -- will *exactly* match what's in your log.

+ There are 3 situations that will cause LoTW to report information that doesn't exactly match what's in your log:

1. after submitting a logged QSO from DXKeeper to LoTW, you subsequently modify that QSO in DXKeeper.

2. you use an application that both submits QSO information to LoTW and logs QSO information to DXKeeper, but the two sets of QSO information are not identical - e.g. one set specifies the QSO time to the second, and the other specifies the QSO time to the minute, with seconds set to 00.

3. a defect in LoTW or DXKeeper

73,

Dave, AA6YQ