Date   

Re: Can two Spot Collectors connect simultaneously to same DXKeeper database?

RowlandA
 

Hey Dave - that ability to connect WSJT-X (or JTDX) + Commander to a remote SpotCollector / DXKeeper [/DXview] is just what the Dr ordered!  Very slick!

That's really all I need for my current operating conditions, thx.  Out of curiosity, are there any other clients that could operate this way (just the client + UDP)?  
If WinWarbler did that I think all modes would be covered for the occasional non-FT8 QSO on the Radio PC.

Thanks and 73,
Rowland K4XD


Re: DXCC Submission utter confusion

N1BUG
 

+ There wasn't, but there is now: I've expanded the "Generating an LoTW Submission" section of
https://www.dxlabsuite.com/dxlabwiki/GenerateSubmission <https://www.dxlabsuite.com/dxlabwiki/GenerateSubmission>
+ to describe and characterize the two alternatives.
Looks good, Dave. Thanks.

I was able to complete my application using only LoTW. It was processed within a couple of hours. No problems downloading or linking DXCC credits in DXKeeper. This is the method that is right for me.

73,
Paul N1BUG


Re: SpotCollector

eddy on5jk
 

Evidently, that will solve my problem Dave. I should have known!

But still, in the past the <Show Spots>-window stayed as a "part of.." SC-window.

I always was able to copy correct info from that "Show Spots" part right to the Notes box of an outgoing spot.

But i'll handle the (evident) solution you proposed.

Eddy ON5JK

Op 28/07/2021 om 21:24 schreef Dave AA6YQ:

+ AA6YQ comments below

Dave i noticed a small inconvenient in my SC.

When i activated "Show Spots of <Callsign> near <QRG> in SSB " the apropriate window apears on top, showing a bunch of former spots.

Usually in the past it was possible to write a reference or so in the "Notes" box of a possible outgoing spot, still showing the window <Show
Spots> thus able to copy an earlier given reference.

Now, when i have the <Show Spots...> visible, and i move the cursor and
click in the box for the "notes for outgoing spots"

the moment i click the window "Show Spots" dissapears. It is no longer
"on top", but hidden by the SC-window.

+ That's correct behavior, Eddy: when you click on a window, it becomes active, and obscures any parts of windows behind it that do not have their "always on top" properties enabled. The "Spots of ..." window has never had its "always on top" property enabled; DXLab applications only enable a window's "always on top" property if that window displays information that the user must immediately see.

So i am not able to copy data from it, in order to generate a new spot with correct references.

+ Position the "Spots of..." window so that it is not behind SpotCollector's Main window.

73,

Dave, AA6YQ





Change of ClubLog status

3a2mw Franco Lucioni
 

Hi Dave and All,
The integration of DXKeeper with ClubLog Grid Square map works very well, and the resulting feature is really interesting.
To make it perfect, I think that DXK should change the status of ClubLog from Y to M also when there is a modification in the Grid column of DXK: Grid added or modified by LotW, Grid added copying from eQSL or QSL etc.
To check, I reuploaded my ~80K log to ClubLog, merged with existing log, and around 1600 QSO's were modified, reflecting the changes LotW or me made to the Grid column.
73
Franco 3A2MW


Re: SpotCollector

Dave AA6YQ
 

+ AA6YQ comments below

Dave i noticed a small inconvenient in my SC.

When i activated "Show Spots of <Callsign> near <QRG> in SSB " the apropriate window apears on top, showing a bunch of former spots.

Usually in the past it was possible to write a reference or so in the "Notes" box of a possible outgoing spot, still showing the window <Show
Spots> thus able to copy an earlier given reference.

Now, when i have the <Show Spots...> visible, and i move the cursor and
click in the box for the "notes for outgoing spots"

the moment i click the window "Show Spots" dissapears. It is no longer
"on top", but hidden by the SC-window.

+ That's correct behavior, Eddy: when you click on a window, it becomes active, and obscures any parts of windows behind it that do not have their "always on top" properties enabled. The "Spots of ..." window has never had its "always on top" property enabled; DXLab applications only enable a window's "always on top" property if that window displays information that the user must immediately see.

So i am not able to copy data from it, in order to generate a new spot with correct references.

+ Position the "Spots of..." window so that it is not behind SpotCollector's Main window.

73,

Dave, AA6YQ


Re: Can two Spot Collectors connect simultaneously to same DXKeeper database?

Dave AA6YQ
 

+ AA6YQ comments below
I'll try the approach I outlined above, running a second database on the Office PC and exporting / importing the ADIF's to the master db on the Radio PC.
I don't see a reliable way to automate this export/import but please advise if I've missed something (i.e. a "synch" function that exports/imports new QSO's each time).

+ There is no such "new QSO sync" function; when I asked here about providing this capability several years ago, no one expressed interest. Such a capability would only ensure that a new QSO logged on the remote system was also logged on the local (master) system; it would not propagate changes made to QSOs via the remote instance of DXKeeper, like updating a signal report. I fear this could cause confusion and data loss.

+ If you use the direct interoperation between WSJT-X and DXLab, all you would need on the remote system would be instances of WSJT-X and Commander; QSOs logged via the remote instance of WSJT-X would be conveyed to the local instance of SpotCollector, which would direct the local instance of DXKeeper to log them. See "Installing and Configuring Additional WSJT-X Instances" in 

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect

       73,

             Dave, AA6YQ

 


Re: Can two Spot Collectors connect simultaneously to same DXKeeper database?

RowlandA
 

Thanks Dave - my replies in bold below:

+ AA6YQ comments below


I have one Flex 6600M in my radio room with a local PC (the "Radio PC").
DXLab Suite is installed there and I consider this the master DXKeeper database.

I also remote connect to the Flex from my office PC, and have a DXLab Suite installation there as well.
I know that we can't open the same DXKeeper database simultaneously from to instances of DXKeeper, but I would like to have the Office PC and the Radio PC's Spot Collector instances both connect to the master DXKeeper database, on the Radio PC, for award progress reference ("needs"). I will then export ADIF from the office PC DXKeeper periodically and import those QSO's to the Radio PC master database.

Before implementing this, I'd like to make sure it's OK so I don't corrupt my database.

+ SpotCollector's access to your log database is "read only". I don't know of a specific reason why multiple instance of SpotCollector could not reference the same Spot Database, but the fact that one of the access paths would be a network might introduce performance problems. I have never tested this configuration, nor do I know of anyone who employs it.
OK - I can set sharing to Read Only as well on the folder holding the .mdb log file so I feel pretty confident this won't cause corruption.


+ Have you considered remotely accessing your radio room PC from your office PC? This would eliminate the WSJT-X latency issue.
Yes, I have done this but I like the "feel" better of running the logging and control apps on the local PC.  Part of my motivation for getting the Flex was to do remote radio without the remote desktop approach.

+ Alternatively, you could close DXKeeper on your radio room PC and then move your log file over the network to your office PC when you're about to make QSOs there, and close DXKeeper on your office PC and move your log file over the network back to your radio room PC when you're about to make QSOs there.
I run the Flex in "multiFlex" mode - e.g. I can leave WSJT-X running on the Radio PC sitting on 6M, while running another instance on my Office PC to do DX'ing on other bands, so having the ability to log on either computer without taking time to move the database is important for me.

I'll try the approach I outlined above, running a second database on the Office PC and exporting / importing the ADIF's to the master db on the Radio PC.
I don't see a reliable way to automate this export/import but please advise if I've missed something (i.e. a "synch" function that exports/imports new QSO's each time).

Thanks again.
73,
Rowland K4XD


73,

Dave, AA6YQ


SpotCollector

eddy on5jk
 

Dave i noticed a small inconvenient in my SC.

When i activated "Show Spots of <Callsign> near <QRG>  in SSB " the apropriate window apears on top, showing a bunch of former spots.

Usually in the past it was possible to write a reference or so in the "Notes" box of a possible outgoing spot, still showing the window <Show Spots> thus able to copy an earlier given reference.

Now, when i have the <Show Spots...> visible, and i move the cursor and click in the box for the "notes for outgoing spots"

the moment i click the window "Show Spots" dissapears. It is no longer "on top", but hidden by the SC-window.

So i am not able to copy data from it, in order to generate a new spot with correct references.

I use to do this, to correct after false "notes" are sent by another OM. (everybody makes mistakes).

Is it a setting that changed on my PC ?

Thanks for great support.

Eddy ON5JK


DXKeeper 16.2.4 is available

Dave AA6YQ
 

* If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions

before installing or upgrading to DXKeeper 16.2.4


This version

- corrects the error message displayed when attempting to Sync LoTW QSOs or Sync LoTW QSLs with no LoTW account password specified

- corrects a regression in preserving visibility of the Comment/QSLMsg items in the Capture window (tnx to Chuck WS1L, Andy K0AF,
Rien PA7RA, Don WB6BEE, Jim W5ABA, and John K1ESE)

- prevents an errorlog.txt file entry from being generated in state 5 of Capture.NoteMsgToggle_Click (tnx to Chuck WS1L)

- correctly handles double-clicking the letter R in the Mixed column on the Realtime Award Tracking window's IOTA tab (tnx to Aart
PA3C)

- ignores leading and trailing blanks in the items specified in the "Replacement options" panel on the Main window's Import QSOs tab
(tnx to Stewart G0LGS)

- if the "Sync LoTW QSOs" function encounters a duplicate QSO, sets the QSO's Select item to 'Y' (tnx to Glenn W0GJ)

- provides the "Advanced Sorts, Filters, and Modifiers" window's Duplicate filter with a Merge option that harvests information from
duplicate QSOs whose Select items are set to 'Y' and places it into empty items in the QSO whose Select item will not be set to 'Y'
(tnx to Glenn W0GJ)

- provides the "Duplicate Checking" panel on the Main window's "Import QSOs" tab with a "Merge information from each duplicate into
the existing QSO" option that when enabled updates information not present in an existing QSO with information harvested from an
imported duplicate QSO

- when double-clicking a callsign in Commander's Bandspread or Spectrum-Waterfall windows with SpotCollector's "Log Filter" set to
"call" and DXKeeper's "Display previous QSOs on Lookup" disabled, directs DXKeeper to populate its Filter panel textbox with the
double-clicked callsign (tnx to Jim W5ABA)

- includes the GRIDSQUARE and VUCC_GRIDS items when submitting a QSO to Club Log, and recognizes Club Log's new "Updated" response
(tnx to Michael G7VJR)

- updates the FilterLog.htm, Import.htm, QSL.htm, and ViewEditLog.htm documentation files


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 69 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable


2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


3. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>




DXKeeper 16.2.4 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ


Re: Transfer a Workspace ...

Dave AA6YQ
 

+ AA6YQ comments below
This all worked. The log has been transferred (via Zoom and Dropbox)
to the new Trustee. We even imported 700+ Field Day QSOs and uploaded
them to LOTW. I even discovered a couple things deep in the bowels of
DXKeeper that will smooth those imports for both him and me in the
future (ignore sub-squares, stop deducing).

All the switching of workspaces though made me think of a feature
request. My workspaces had all leaked.

+ What does it mean for a Workspace to leak?

This isn't a big deal if I switch, say, from "N5UWY" to "N5UWY-Lite" since it's the same DB and
the same LOTW creds though with different app settings ... but for the
club call, it was an issue. I've gone through and cleaned them all up
in my installation. Further, I've also made it a new habit to "save
settings" before loading another workspace.

+ The only way to force DXLab application to save its settings to the Windows Registry is to terminate it. Doing this is only necessary if you've made changes to the application's settings since starting it, and you plan to update a Workspace with those changed settings.

I also recommended this
to the new trustee and told him why. My feature request is this: For
a user who has just terminated a workspace and who goes to load a
different one, a dialog box that prompts the user to save the settings
of the workspace they just left. Not sure of the exact sequence of
events, but something that reminds me to save settings before I load
the next workspace would, I think, prevent inter-workspace leakage.
Not much of a problem if you only have a single callsign, but if you
manage club calls, I think it would be helpful.
+ I'll be able to understand this request after you explain the meaning of "Workspace leakage".
Speaking of workspaces, the new trustee was having issues with save
workspaces. Errorlog showed the MSWINSCK.OCX error that others have
mentioned.
+ To what  MSWINSCK.OCX error are you referring?

Found a couple of old list messages that had procedures
that did "something" in that we get a different error now.
+ If there's an errorlog.txt file, please attach it to an email message, and send the message to me via

aa6yq (at) ambersoft.com

    73,

           Dave, AA6YQ


FW: [Club Log] Re: New feature: grid square maps

Dave AA6YQ
 

+ AA6YQ comments below

A few small changes:

1) Club Log can now read in extra grids from the VUCC_GRIDS field, allowing more than one grid per QSO. This is to support crossing grids (i.e. QSOs where a station is on the exact boundary of grids).

2) Merging now works. If you upload an ADIF which contains grids etc. then they are merged in. No need to clear your log anymore.

3) Real time logging now returns "Updated" rather than "Dupe" when updates are made to an existing QSO.

Thanks to Dave AA6YQ for the tip about VUCC_GRIDS and Dave, N9FN for his (amazing) test log which helped immeasurably with this.

+ I have updated the next version of DXKeeper to recognize the new "Updated QSO" response from Club Log, and tested it by both uploading a previously-uploaded QSO that specifies a grid square ,and uploading a previously-uploaded QSO that was just confirmed via LoTW; in both cases, the response from Club Log was "Updated QSO.

73,

Dave, AA6YQ


Re: DXCC Submission utter confusion

Dave AA6YQ
 

+ AA6YQ comments below
Merely as a personal comment: I am sure somewhere in the DXLab documentation what you explained earlier about the alternate, though potentially more expensive option is duly noted. However, I never found it or failed to understand. Had there been a note in the relevant portion of

http://www.dxlabsuite.com/dxlabwiki/GenerateSubmission

explaining that the procedure can be tedious and noting an alternate method, that might have saved me a lot of time and frustration both in 2016 and in recent weeks

+ There wasn't, but there is now: I've expanded the "Generating an LoTW Submission" section of 

https://www.dxlabsuite.com/dxlabwiki/GenerateSubmission

+ to describe and characterize the two alternatives.

       73,

               Dave, AA6YQ

 


Re: Clublog autoupload gridsquare

w6de
 

I submit QSOs to ClubLog after each operating session.  Most of these QSO are ‘new’ and not confirmed.  In the following days/weeks. I periodically Sync the OSOs and then Sync QLSs.  If only a few QSL confirmations are received, I will ‘right click select’ each of those QSOs individually and choose “Upoad to Club Log: W6DE.”  For each of those QSO QSLs I will receive from Club Log via DXKeeper a message that says: “Upload QSO to Club Log succeeded: Dupe.”

Comment:  If I have more than a few confirmations from a QSL Sync QSL operation, I use batch submission via DXLAB | Check Progress Tab | Club Log: W6DE | Upload.  I don’t recall   what I receive in response to those bulk uploads.

 

I have never thought much about this.  But, this may have some bearing on the issue you are pursuing with G7VJR.

 

 

73,

Dave, w6de

 

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ via groups.io
Sent: Tuesday, July 27, 2021 20:09
To: DXLab@groups.io
Subject: Re: [DXLab] Clublog autoupload gridsquare

 

+ AA6YQ comments below

Grid Squares Map feature (still in beta) has been added to Clublog. I checked my log, but most of QSOs don't have gridsquare :( ClubLogUpload.adi file for autoupload does not provide GRIDSQUARE or VUCC_GRIDS fields. Can you please consider add this two fields ?

+ I have already added the submission of each QSO's GRIDSQUARE and VUCC_FIELDS)items to the next version of DXKeeper, but ClubLog reports "Dupe" when I attempt to resubmit a previously-submitted QSO that now specifies one or more grid squares. I am working with Michael G7VJR to resolve this.

       73,

              Dave, AA6YQ


Re: DXCC Submission utter confusion

N1BUG
 

Thanks for your help, Dave.

More comments below.

+ What's missing is the LoTW API that would enable DXKeeper to send the 128 QSOs in it submission to LoTW to say "select these".
I understand that but I wasn't prepared for such a large difference in the number of QSOs.

Merely as a personal comment: I am sure somewhere in the DXLab documentation what you explained earlier about the alternate, though potentially more expensive option is duly noted. However, I never found it or failed to understand. Had there been a note in the relevant portion of

http://www.dxlabsuite.com/dxlabwiki/GenerateSubmission

explaining that the procedure can be tedious and noting an alternate method, that might have saved me a lot of time and frustration both in 2016 and in recent weeks.

I've had such a difficult time with this that when I finally get the easier procedure down and am sure it works for me, I will be writing my own personal "how to" on this for next time.

+ How many QSOs does LoTW select for submission?
LoTW did not appear to say, but it was at least several hundred. My impression was that it was well past a thousand.

73,
Paul N1BUG


Re: Can two Spot Collectors connect simultaneously to same DXKeeper database?

Dave AA6YQ
 

+ AA6YQ comments below

I have one Flex 6600M in my radio room with a local PC (the "Radio PC").
DXLab Suite is installed there and I consider this the master DXKeeper database.

I also remote connect to the Flex from my office PC, and have a DXLab Suite installation there as well.
I know that we can't open the same DXKeeper database simultaneously from to instances of DXKeeper, but I would like to have the Office PC and the Radio PC's Spot Collector instances both connect to the master DXKeeper database, on the Radio PC, for award progress reference ("needs"). I will then export ADIF from the office PC DXKeeper periodically and import those QSO's to the Radio PC master database.

Before implementing this, I'd like to make sure it's OK so I don't corrupt my database.

+ SpotCollector's access to your log database is "read only". I don't know of a specific reason why multiple instance of SpotCollector could not reference the same Spot Database, but the fact that one of the access paths would be a network might introduce performance problems. I have never tested this configuration, nor do I know of anyone who employs it.

+ Have you considered remotely accessing your radio room PC from your office PC? This would eliminate the WSJT-X latency issue.

+ Alternatively, you could close DXKeeper on your radio room PC and then move your log file over the network to your office PC when you're about to make QSOs there, and close DXKeeper on your office PC and move your log file over the network back to your radio room PC when you're about to make QSOs there.

73,

Dave, AA6YQ


Re: DXCC Submission utter confusion

Dave AA6YQ
 

+ AA6YQ comments below
Case A. I am trying to make an application based exclusively on QSOs confirmed in LoTW.

The idea is to include four all time new ones which would get me back on Honor Roll, to include several new ones on 160m, and to include LoTW confirmed QSOs for 6m and 2m.

DXKeeper selected 128 LoTW confirmed QSOs for this submission. That looked fine but when I got to the steps involving comparing this list to that selected by LoTW there were far too many to deal with in LoTW.

I think I had an incorrect URL in my first post. I started with "Generating an LoTW Submission" here:

http://www.dxlabsuite.com/dxlabwiki/GenerateSubmission

In step 6 that leads me to

http://www.dxlabsuite.com/dxlabwiki/SubmitLotW

Step 2 there leads me to

https://lotw.arrl.org/lotw-help/dxcc-award-candidates/

That is where I get lost trying to get the list in LoTW to match the list prepared by DXKeeper. LoTW has thousands of confirmed QSOs in its list. It would take days of work for me to do all the editing to get it down to the 128 DXKeeper selects. I keep thinking I must be missing a step, but I do not see where.

+ What's missing is the LoTW API that would enable DXKeeper to send the 128 QSOs in it submission to LoTW to say "select these".

+ How many QSOs does LoTW select for submission?

    73,

           Dave, AA6YQ

 

 


Re: DXCC Submission utter confusion

Steve Phillips - NS4P
 

Paul,

Dave AA6YQ has provided the authoritative answer in his post.

But you are not wrong, If you want to submit the minimal number of QSOs that you need to meet your objectives (i.e. spend the least amount of money) you need to manually check or uncheck the QSOs in LOTW one at a time based on the list that DXKeeper generates.  This might take a while.

Your other choice is to just let LOTW pick which QSOs to submit.  You will pay more, but you will also be done in 10 much less time.


Re: DXCC Submission utter confusion

N1BUG
 

Steve,

Case A. I am trying to make an application based exclusively on QSOs confirmed in LoTW.

The idea is to include four all time new ones which would get me back on Honor Roll, to include several new ones on 160m, and to include LoTW confirmed QSOs for 6m and 2m.

DXKeeper selected 128 LoTW confirmed QSOs for this submission. That looked fine but when I got to the steps involving comparing this list to that selected by LoTW there were far too many to deal with in LoTW.

I think I had an incorrect URL in my first post. I started with "Generating an LoTW Submission" here:

http://www.dxlabsuite.com/dxlabwiki/GenerateSubmission

In step 6 that leads me to

http://www.dxlabsuite.com/dxlabwiki/SubmitLotW

Step 2 there leads me to

https://lotw.arrl.org/lotw-help/dxcc-award-candidates/

That is where I get lost trying to get the list in LoTW to match the list prepared by DXKeeper. LoTW has thousands of confirmed QSOs in its list. It would take days of work for me to do all the editing to get it down to the 128 DXKeeper selects. I keep thinking I must be missing a step, but I do not see where.

Paul

On 7/27/21 3:50 PM, Steve Phillips - NS4P wrote:
Paul,
We are trying to help, but you need to provide more information.  Which of the following describes your situation?
Case A - You are making an application based exclusively on QSOs confirmed in LOTW (i.e. no physical cards)
Case B - You are making an application based exclusively on QSOs confirmed with physical cards (i.e. no LOTW confirmations)
Case C - You are submitting both LOTW confirmations and physical cards for DXCC credit.
Finally, what is the total number of QSOs we are talking about (in a round number)?
Steve


Re: DXCC Submission utter confusion

Dave AA6YQ
 

+ AA6YQ comments below
I'm no expert, but I think you are making this harder than it needs to be.

Question - Are all the QSOs you want to use loaded and matched in LOTW?

If the answer is yes, I don't understand why you are using DX Keeper at all.  Why not just generate the application from LOTW? 

+ Because LoTW's DXCC submission generator is sub-optimal, and will therefore submit more confirmations than necessary, costing your more money than necessary. For a handful of confirmations, the difference is minimal, but if you are submitting hundreds or thousands of confirmations for DXCC Challenge, the difference can be significant.

+ The choice is straightforward:

A. Let LoTW choose the QSOs to submit. After your submission has been processed, direct DXKeeper to download your DXCC Credits and update your logged QSOs to reflect the newly-granted award credits. You might pay more than necessary, but process is automated.

B. Let DXKeeper assemble the submission, and then in LoTW choose the QSOs that DXKeeper picked but LoTW didn't - one at a time. After your submission has been processed, direct DXKeeper to with one mouse click mark all of the QSOs in your submission as having received DXCC award credit.


+ If you choose path A, steps 1-4 in

https://lotw.arrl.org/lotw-help/dxcc-award-candidates/

+ explain how to let LoTW create a submission. These instructions explain how to download your DXCC Credits and update your logged QSOs to reflect DXCC award credit granted after your LoTW submission has been processed:

https://www.dxlabsuite.com/dxlabwiki/ManageDXCCCredits

 

+ If you choose path B, steps 1-4 in

https://lotw.arrl.org/lotw-help/dxcc-award-candidates/

+ explain how to let LoTW create a submission, and step 5 explains how to modify that submission to match DXKeeper's submission. Yes, this is tedious. If LoTW provided an API that enabled DXKeeper to specify the QSOs to be submitted (as is done for QSL cards with "DXCC Online"), the entire "path B" process could be automated; sadly, the prospects for adding such an API are negligible, as the ARRL no longer has developers that are familiar with LoTW internals, and the ARRL CEO is advocating a multi-year project to replace LoTW with a new cloud-hosted implementation. 

+ If you consider the complexity of "path B" to be too great, use "path A" and accept the additional cost.

       73,

             Dave, AA6YQ

 

 

 

 

 

 

 

 

(Awards - Select DXCC Account - Application)  You can select the awards you want to apply for, select the QSOs you want to use on the application, and submit your payment all on-line.


Re: DXCC Submission utter confusion

DAVID BERNHEISEL
 

Which of the following applications is causing the confusion?


A

Online DXCC Application

Welcome to the ARRL DXCC online application system*.

*Be sure to review important DXCC application information before accessing Online DXCC.

Check your browser. For optimal user experience, please upgrade your browser to its latest version or use an alternative browser such as Firefox, Chrome, or Safari.

Be sure to pay CLOSE attention to your data entry. Check each entry to be sure you have entered the correct callsign, accurate date, band and mode and that you have selected the correct entity. Data mismatches will almost always cause a problem and may result in a QSO being rejected.

After completeing your online DXCC application, you may bring your cards and forms to a local DXCC card checker or send in the paperwork and cards to the ARRL DXCC Desk. Use the DXCC Card Checker Search to find a DXCC card checker.

If mailing cards to ARRL, package the cards securely, protect the cards from moisture, and use a trackable shipping method.


B


DXCC Award Application -- Part 1

Use this form to apply for a new DXCC award or an endorsement.

Entity QSO Check all
Clear all
Awards
Digital* 160M 80M* 40M* 30M* 20M* 17M* 15M* 12M* 10M* 6M Challenge*



Dave, N2DPF

3241 - 3260 of 205885