Date   

Re: Missing QSO's

Joe Subich, W4TV
 

Bill,

1) *BACK UP YOUR DXKEEPER LOG*
2) On the DXKeeper Import QSOs tab, make sure Duplicate checking
is enabled (check "check duplicates on import range +/- 1 minutes -
set to 1 minutes if not already set to 1 minute)
3) Import the WSJTX_LOG.adi file.

The majority of the QSOs should be ignored as duplicates, the
"missing" 37 should be imported if they are not themselves duplicates
of existing QSOs (log entries).

73,

... Joe, W4TV

On 2020-10-20 12:16 PM, Bill - AA4M wrote:
They are both showing the same 37 QSO error.
73, Bill  AA4M
On 10/20/2020 09:11:17, Carl - WC4H via groups.io wrote:
Hi Bill.

wsjtx.log file is not the log.  The wsjtx_log.adi file is the one to look at.

73.
Carl - WC4H


Re: N1MM to DXKeeper Gateway multiple county issue

ve3ki
 

Correct. If your contest entry category in N1MM+ is ROVER and you use the COUNTYLINE command to enter the location as the corner of DuPage, Kane, Kendall and Will counties (DUPG,KANE,KEND,WILL) and enter a single contact with W9IAU with the exchange GALL/HAML/SALI/WHIT, sixteen QSOs will automatically appear in the N1MM+ log, one for each of the 4x4 county combinations. The QSOs will be logged with times differing by two-second intervals, which means they might all be logged within the same clock minute, or they might be logged within two consecutive clock minutes if the 2-second increments happen to cause the minutes part of the time to roll over. Apart from the 2-second time differences, an internal database guid and the contents of the Exchange1 field, the contacts will be otherwise identical.

If you then export the log to ADIF and import that ADIF file into DXKeeper, all 16 contacts will be imported into the DXKeeper log. The rx info (SRX_STRING) field will contain the county abbreviation received from the other station. If you have not used the AD1C county conversion program and you want to record the other station's county in the county field in the DXKeeper log with the full county name, you will have to enter that information (you may be able to use the Advanced Sorts, Filters and Modifiers window to help with this). 

N1MM+ does not export the sent exchange to ADIF, so the tx info (STX_STRING) field in DXKeeper will be empty. If you wish, you can fill it in manually by referring to the sent exchange column in the Cabrillo file. If you wish to upload these contacts to LotW with the correct counties in the station information, you will have to separate out the contacts by individual sent exchange and use a separate tQSL station location for each county (sent exchange).

73,
Rich VE3KI


On Tue, Oct 20, 2020 at 10:57 AM, Scott Stembaugh wrote:
you have to tell N1MM that you are on a county line. I think you enter COUNTYLINE in the callbox before you make qsos. 

On Tue, Oct 20, 2020, 07:29 Mike - W1MI <aa1ar@...> wrote:
On Tue, Oct 20, 2020 at 04:00 AM, Phil Deaver wrote:
One more note on state QSO parties. This was true a few months ago and is probably still true (although I wasn't able to verify it with the station I worked this weekend. None of the callsigns on the QRZ page list an email address unfortunately). The station on the county line only gets credit for one contact while the contacting station gets credit for 2 or 3 or 4 QSOs. We found this out the hard way during the 7QP QSO party. We were told we would get double QSO points being on the county line, but that apparently was bad information. N1MM would only log one contact for the county line station with both counties in the report field. So it took us extra time to send out both counties info, we had many requests for repeats since it was a little unusual and we had to train some of the stations on how to input the two counties into N1MM. All of this slowed us down (quite a bit) and the only benefit to us was that our station was more desirable since it was a 2-fer to the calling station. So the result of this is that the calling station would have 2 QSOs into DXKeeper and LOTW while the called station would have 1 QSO. 

 Phil,
Looking at the last few paragraphs of https://n1mmwp.hamdocs.com/manual-supported/contests-setup/setup-qsop-contests/
you should have gotten multiple QSOs in your log for each contact.  Maybe something wasn't set up quite right...
73, Mike - W1MI


Re: LOTW Download Error Message

Dave AA6YQ
 

+ AA6YQ comments below
I am new to DXLab and am transiting from an different logging program.
+ Welcome to DXLab, Henry!

I have successfully imported my existing log and have successfully uploaded that log to LotW and have successfully synced LotW QSOs, all 65K of them. When I try to sync QSLs, I get the following error from DXKeeper. What might I have missed? 

"Unable to download from LotW: Invalid request"

+ Given that you've successfully invoked "Sync LoTW QSOs", your LoTW username and password are specified correctly. If retrying the "Sync LoTW QSLs" operation doesn't produce a different outcome, please do the following:

1. on the Configuration window's General tab, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper

4. invoke the "Sync LoTW QSLs" operation

5. on the Configuration window's General tab, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

           73,

                 Dave, AA6YQ


Re: Award progress report CSV generation

Dave AA6YQ
 

+ AA6YQ comments below
How can I generate a progress report in CSV, instead of TXT?
I saw the instructions below but it is not clear where I configure it:

+ Most award progress reports are generated as text files. A few (like WAZ) are generated as HTML files because their complexity warrants the use of tables with hyperlinks. A few (like Marathon) "award submission files" are generated in comma-delimited format because that's what their award sponsors required. 

+ There is no option to generate a progress report in a format of your choosing.

          73,

                 Dave, AA6YQ


Re: Missing QSO's

Dave AA6YQ
 

+ AA6YQ comments below
I just discovered  that my "wsjtx.log" file is showing 37 more QSO's than DXKeeper.  I  think what happened is that at some point in the past I accidentally turned off JTAlert, which resulted in a group of contacts not making it to DXKeeper.  Is there any easy way I can find the missing QSO's?

+ First, make a backup copy of your log file (in case things don't go as expected).

+ Second, direct DXKeeper to import your WSJT-X log file with "duplicate checking" enabled, with a range of 1 minute. Prepare for this operation to take a while. See

<https://www.dxlabsuite.com/dxkeeper/Help/Import.htm#Duplicate_Checking>

      73,

              Dave, AA6YQ


LOTW Download Error Message

Henry Boze
 

I am new to DXLab and am transiting from an different logging program. I have successfully imported my existing log and have successfully uploaded that log to LotW and have successfully synced LotW QSOs, all 65K of them. When I try to sync QSLs, I get the following error from DXKeeper. What might I have missed? 

"Unable to download from LotW: Invalid request"

Thanks for any help with this issue.

73,

Henry, N4HB


Re: N1MM to DXKeeper Gateway multiple county issue

Dave AA6YQ
 

+ AA6YQ comments below
Looking at the last few paragraphs of https://n1mmwp.hamdocs.com/manual-supported/contests-setup/setup-qsop-contests/
you should have gotten multiple QSOs in your log for each contact.  Maybe something wasn't set up quite right...
+ N1MM did log multiple QSOs for county-line contacts, but the current version of the N1MM-DXKeeper Gateway ks unaware of this possibility.

        73,

             Dave, AA6YQ


Re: N1MM to DXKeeper Gateway multiple county issue

Dave AA6YQ
 

* more AA6YQ comments below

The 2 second time difference creates another issue for me.  I also saw only two QSO's in DXKeeper for each of my 5 sets of QSOs with multiple counties.  If I import the entire contest log, DXKeeper rejects the missing QSOs as dupes because I have a checkmark next to "Check duplicates on import, range +/- 1 minutes".  If I remove the checkmark, I will get many dupes

 

+ Why are you enabling duplicate checking when importing your contest log from N1MM?

 

Since the majority of my contest log is already in DXKeeper, turning off dupe checking and re-importing would result in many dupes, would it not?

* Yes, it would. I'd misunderstood your earlier report to mean that you were importing an ADIF file with your contest QSOs after the contest, and was wondering why you had duplicate checking enabled when you did that.

       73,

             Dave, AA6YQ


Award progress report CSV generation

Py2Rn
 

How can I generate a progress report in CSV, instead of TXT?
I saw the instructions below but it is not clear where I configure it:

Generating Award Progress and Submission Reports

The awards for which DXKeeper provides progress reporting have differing requirements as to which items must be recorded with a QSO in order to properly determine credit. A table describing the requirements for each supported award is provided here.

DXKeeper can generate a wide variety of award progress and submission reports. The format of all dates used in these reports is specified via the Date Format panel on the Config window's Reports tab. Generated reports are placed in files in DXKeeper's  Reports sub-folder with filenames constructed from your callsign, the report name, and the report date, e.g.

  • AA6YQ Marathon Unlimited Mixed Progress 2014-12-15.txt

  • AA6YQ Marathon Formula Mixed Submission 2014-12-01.csv

  • AA6YQ Worked All DOKs 2008-11-27.txt

  • AA6YQ Worked All Prefixes Summary 2008-08-23.htm

Generated reports are saved as text files unless otherwise noted to produce files in HTML or CSV (comma-separated values) formats. After generating a progress report file, DXKeeper will display the report using the default viewer application for the file type assigned in Windows; typically, this assignment is

  • Notepad for .txt files

  • Microsoft Internet Explorer for .htm files

  • Microsoft Excel for .csv files

    Thanks

    Ed 

    PY2RN


Re: Missing QSO's

Bill - AA4M
 

They are both showing the same 37 QSO error.

73, Bill  AA4M


On 10/20/2020 09:11:17, Carl - WC4H via groups.io wrote:
Hi Bill.

wsjtx.log file is not the log.  The wsjtx_log.adi file is the one to look at.

73.
Carl - WC4H


Re: Missing QSO's

Carl - WC4H
 

Hi Bill.

wsjtx.log file is not the log.  The wsjtx_log.adi file is the one to look at.

73.
Carl - WC4H


Missing QSO's

Bill - AA4M
 

Hello,

I just discovered  that my "wsjtx.log" file is showing 37 more QSO's than DXKeeper.  I  think what happened is that at some point in the past I accidentally turned off JTAlert, which resulted in a group of contacts not making it to DXKeeper.  Is there any easy way I can find the missing QSO's?

73, Bill  AA4M


Re: N1MM to DXKeeper Gateway multiple county issue

Scott Stembaugh
 

you have to tell N1MM that you are on a county line. I think you enter COUNTYLINE in the callbox before you make qsos. 


On Tue, Oct 20, 2020, 07:29 Mike - W1MI <aa1ar@...> wrote:
On Tue, Oct 20, 2020 at 04:00 AM, Phil Deaver wrote:
One more note on state QSO parties. This was true a few months ago and is probably still true (although I wasn't able to verify it with the station I worked this weekend. None of the callsigns on the QRZ page list an email address unfortunately). The station on the county line only gets credit for one contact while the contacting station gets credit for 2 or 3 or 4 QSOs. We found this out the hard way during the 7QP QSO party. We were told we would get double QSO points being on the county line, but that apparently was bad information. N1MM would only log one contact for the county line station with both counties in the report field. So it took us extra time to send out both counties info, we had many requests for repeats since it was a little unusual and we had to train some of the stations on how to input the two counties into N1MM. All of this slowed us down (quite a bit) and the only benefit to us was that our station was more desirable since it was a 2-fer to the calling station. So the result of this is that the calling station would have 2 QSOs into DXKeeper and LOTW while the called station would have 1 QSO. 

 Phil,
Looking at the last few paragraphs of https://n1mmwp.hamdocs.com/manual-supported/contests-setup/setup-qsop-contests/
you should have gotten multiple QSOs in your log for each contact.  Maybe something wasn't set up quite right...
73, Mike - W1MI


Re: Sync LoTW

Salvatore Besso
 

Mike,

the "Sync LotW QSLs" date doesn't change if there are no LotW changes, for example new confirmations but also data corrections. What does the text log say at the end of the sync operation? If it says "there are no changes..." or something similar, the sync date will not change and it will remain at the last date where you've had changes.

73 de
Salvatore (I4FYV)


Sync LoTW

w3qt_mike
 

I’m having a slight problem with DXK on the QSL tab in the LoTW Operations pane.  The Sync LoTW QSLs date and time stamp does not change at the end of the operation.  This just started.  Currently the upload date shows as 10/19/20.  The Sync date is stuck on 10/15/20 but should read 10/20/2020.  I’ve restarted the computer, DXK several times, as well as retrying the sync several times but no change.  The Upload to LoTW stamp is accurate.  Thanks.

 

73,

Mike, W3QT

 


Re: N1MM to DXKeeper Gateway multiple county issue

Mike - W1MI
 

On Tue, Oct 20, 2020 at 04:00 AM, Phil Deaver wrote:
One more note on state QSO parties. This was true a few months ago and is probably still true (although I wasn't able to verify it with the station I worked this weekend. None of the callsigns on the QRZ page list an email address unfortunately). The station on the county line only gets credit for one contact while the contacting station gets credit for 2 or 3 or 4 QSOs. We found this out the hard way during the 7QP QSO party. We were told we would get double QSO points being on the county line, but that apparently was bad information. N1MM would only log one contact for the county line station with both counties in the report field. So it took us extra time to send out both counties info, we had many requests for repeats since it was a little unusual and we had to train some of the stations on how to input the two counties into N1MM. All of this slowed us down (quite a bit) and the only benefit to us was that our station was more desirable since it was a 2-fer to the calling station. So the result of this is that the calling station would have 2 QSOs into DXKeeper and LOTW while the called station would have 1 QSO. 

 Phil,
Looking at the last few paragraphs of https://n1mmwp.hamdocs.com/manual-supported/contests-setup/setup-qsop-contests/
you should have gotten multiple QSOs in your log for each contact.  Maybe something wasn't set up quite right...
73, Mike - W1MI


Re: N1MM to DXKeeper Gateway multiple county issue

Mike - W1MI
 

On Mon, Oct 19, 2020 at 07:54 PM, ve3ki wrote:
Mike,

If you already have a lot of QSOs transferred from N1MM+ to DXKeeper via the Gateway and the only ones you are missing are from county line QSOs (which I assume are only a small fraction of the total), then what I would do is export the full ADIF from N1MM+ and then edit out all of the QSOs that are already in DXKeeper (all the non-county-line QSOs pus the county-line ones that did make it through the Gateway). You can do this quite easily in ADIF Master (<http://www.dxshell.com/adif-master.html>), which presents the ADIF file in a spreadsheet format, allows sorting on any field, and makes editing tasks like deleting unwanted rows en masse quite easy. Once the file is pared down to only non-dupe QSOs, which should take only a couple of minutes, you can import it into DXKeeper with dupe checking turned off.

73,
Rich VE3KI
Thanks, Rich

I was going to edit it in notepad, but ADIF Master would speed things up!

73, Mike - W1MI


Re: N1MM to DXKeeper Gateway multiple county issue

Mike - W1MI
 

On Mon, Oct 19, 2020 at 07:01 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
The 2 second time difference creates another issue for me.  I also saw only two QSO's in DXKeeper for each of my 5 sets of QSOs with multiple counties.  If I import the entire contest log, DXKeeper rejects the missing QSOs as dupes because I have a checkmark next to "Check duplicates on import, range +/- 1 minutes".  If I remove the checkmark, I will get many dupes.

+ Why are you enabling duplicate checking when importing your contest log from N1MM?

 

Since the majority of my contest log is already in DXKeeper, turning off dupe checking and re-importing would result in many dupes, would it not?


Re: N1MM to DXKeeper Gateway multiple county issue

Phil Deaver
 

One more note on state QSO parties. This was true a few months ago and is probably still true (although I wasn't able to verify it with the station I worked this weekend. None of the callsigns on the QRZ page list an email address unfortunately). The station on the county line only gets credit for one contact while the contacting station gets credit for 2 or 3 or 4 QSOs. We found this out the hard way during the 7QP QSO party. We were told we would get double QSO points being on the county line, but that apparently was bad information. N1MM would only log one contact for the county line station with both counties in the report field. So it took us extra time to send out both counties info, we had many requests for repeats since it was a little unusual and we had to train some of the stations on how to input the two counties into N1MM. All of this slowed us down (quite a bit) and the only benefit to us was that our station was more desirable since it was a 2-fer to the calling station. So the result of this is that the calling station would have 2 QSOs into DXKeeper and LOTW while the called station would have 1 QSO. 


Re: WSJT-X stopped logging to DXK

Dave AA6YQ
 

+ AA6YQ comments below

Today WSJT-X stopped logging to DXK. Clicking OK on the Log QSO box has no effect. The QSO just disappeared. Normally the DXK log entry is populated and the QSO is logged. This is not happening. Ive had to open the capture window and log the call manually in order to secure a DXK entry. I checked SC and if is running but I do not see the window showing DXK and SC are connected.

+ In the "Spot source status" panel at the top of SpotCollector's Main window, there are 7 circular indicators. What color is the right-most indicator in this panel.

+ In the title bar of SpotCollector's Main window, what letters appear between the square brackets?

+ In your SpotCollector folder, is there a file named

errorlog.txt

+ or

SC_WSJTX_Errorlog.txt

+ ? If either or both are present, please attach them to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

4081 - 4100 of 200930