Date   
Re: Call Column in Spot Collector

Dave AA6YQ
 

+ AA6YQ comments below

Yes. Field is Callsign and Caption is Callsign first row.

+ Thanks. Is there an errorlog.txt file in your SpotCollector folder?

+ If so, please attach the errorlog.txt file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

Re: DXCC Credit Analysis Actions

Joe Subich, W4TV
 

I can attest to the "Country Number Only" entries. I have 867 of
them: 299 Mixed, 274 CW, 294 Phone. I had to manually link every
one of them to the actual QSO/Card entry in my log.

Worse yet, since they were "number only", I had to dig out my old
record sheet (the DXCC list) and look up the call written on the
paper record before I could figure out with which QSO the credit
belonged. Pete, at least you have callsign and year to make the
linking much easier.

73,

... Joe, W4TV

On 2019-05-28 10:26 PM, BILL KENNAMER wrote:
My oldest QSO in the records reads:080Honduras (080)1945-11-15Unknown Unknown
I have Mixed credit only for that contact, although I also have Honduras on all bands, and those are also in the LOTW records.
Bill
Sent from Yahoo Mail for iPad
On Tuesday, May 28, 2019, 6:44 PM, Dave AA6YQ <@AA6YQ> wrote:
+ Here's an example of a DXCC credit awarded to a QSO I made I in 1991.
<http://www.dxlabsuite.com/dxkeeper/9Q5UN.jpg>
+ Note that it specifies
1. the callsign
2. the DXCC entity name, with its "country code" in parenthesis
3. the date
4. the mode
5. the band
+ In my experience - which began when I received my novice ticket in January 1990 - almost all DXCC credits provide the above information, though some of the information may be inaccurate due to shortcuts taken or data entry errors.
+ There was a time when submitting a QSL card for DXCC credit did not result in your receiving credit for the entity, entity-band, and entity-mode; only the credit you requested was granted. DXKeeper provides the ability to specify "entity credit only", "entity-band credit only", and "entity-mode credit only" if you have these situations; alternatively, you can resubmit the QSL card to the ARRL and receive DXCC credit for all "components".
        73,
              Dave, AA6YQ
I’d be surprised that ARRL did that much.  As I said, when we converted from paper to computer (I was in charge of that), we did not enter callsigns into the computer. We entered only the country code. All entries for mixed DXCC were mixed, no matter what mode may have been on the card. Phone credits came from phone DXCC records, etc.
There was no notation of mode, date, time, etc. at the time (1992). In fact, paper DXCC records were the original submission record that the applicant completed, and callsigns were added to the original paperwork, with new additions to the DXCC list handwritten at the bottom.
I had been logging with a computer since 1991, so was able to convert to ADIF. I then entered all QSOs before then from my handwritten longs since 1961. After doing this, I had nearly 40,000 QSOs, all of which have been entered into LOTW. The only discrepancies I ever find are those cases where I have received a card from someone who doesn’t use LOTW.  This usually is less than five QSOs, and is resolved when I make a paper submission.
I suggest you might correct a few dxkeeper entries, and resubmit to LOTW.
73
Bill
K5FUV
Sent from Yahoo Mail for iPad <https://overview.mail.yahoo.com/?.src=iOS>
On Tuesday, May 28, 2019, 2:50 PM, Pete Smith <n4zr@...> wrote:
    Bill, the problem is that ARRL apparently made the decision back when not to enter data from its pre-LOTW/pre-computer era records beyond the callsign, band, mode, and year of each QSO.  All of the credits in question derived from actual cards reviewed and accepted by ARRL, so I contend that a better approach would be for DXKeeper to look for QSOs with the station, mode and band in the *year*, and only balk if there is none, or more than one that fits.  That would take care of 99 percent of mine.
    73, Pete N4ZR
    Check out the Reverse Beacon Network
    at <http://reversebeacon.net> <http://reversebeacon.net> , now
    spotting RTTY activity worldwide.
    For spots, please use your favorite
    "retail" DX cluster.
    On 5/28/2019 3:33 PM, BILL KENNAMER wrote:
    I had no problem with mine entering QSOs back to 1961, but I entered the correct date and time.
    When these cards were originally entered in DXCC records, they were entered into the system 38 with country code number only, no call sign.  Even given that, I have no discrepancies.
    73
    Bill K5FUV
    Sent from Yahoo Mail for iPad <https://overview.mail.yahoo.com/?.src=iOS>
    On Tuesday, May 28, 2019, 1:59 PM, Pete Smith <n4zr@...> <mailto:n4zr@...>  wrote:
        Still trying to get the DXCC status in my log to match with DXCC info from ARRL.  Ran this routine and it worked great for recent QSOs, updating their QSL status to verified, but it left 525 DXCC credits in the status "no exact match found in log."  Each and every one of these is a QSO back in the 70s, 80s and 90s, and the reason why no match was found is that  there is no date in ARRL's record other than the year - for example, 1976-01-01.The instructions for this report say that it should not be used for old QSOs, but not why.  I guess this explains it.
        Is there any other way I can update the QSL status for these QSOs in bulk? They are all shown by DCXX as "card", so there is no doubt (I think) that I deserve the DXCC credit.  I'd just like to avoid 525 separate operations.
        --
        73, Pete N4ZR
        Check out the Reverse Beacon Network
        at <http://reversebeacon.net> <http://reversebeacon.net> , now
        spotting RTTY activity worldwide.
        For spots, please use your favorite
        "retail" DX cluster.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>     Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: Congratulations Dave

Dave AA6YQ
 

+ AA6YQ comments below

On Sat, May 18, 2019 at 08:43 PM, jgmags2000 wrote:

Still playing Rachmaninoff?

+ Still trying. These two preludes are the current "state of my art":

     <http://www.ambersoft.com/Piano/Rachmaninoff%20Prelude%20Op%2032%20nr%2010.mp3>

      http://www.ambersoft.com/Piano/Rachmaninoff%20Prelude%20Op%2032%20nr%2012.mp3>

 

        73,
              Dave, AA6YQ

 

 

 

 

 

Re: Call Column in Spot Collector

John Merrill
 
Edited

On Tue, May 28, 2019 at 07:43 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Yes. Field is Callsign and Caption is Callsign first row.

+ Thanks. Is there an errorlog.txt file in your SpotCollector folder?

+ If so, please attach the errorlog.txt file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ
No error log. I added another column to see what would happen and now the Callsign column does not collapse.
John N1JM

Re: Call Column in Spot Collector

Dave AA6YQ
 

+ AA6YQ comments below

On Tue, May 28, 2019 at 10:13 PM, John Merrill wrote:

No error log.
+ Thanks. Has SpotCollector always behaved this way, or is this new behavior? If the latter, when did it first begin, and what changes did you make to your hardware or software around that time?

       73,

              Dave, AA6YQ

Re: Call Column in Spot Collector

John Merrill
 

On Tue, May 28, 2019 at 10:16 PM, Dave AA6YQ wrote:

+ AA6YQ comments below

On Tue, May 28, 2019 at 10:13 PM, John Merrill wrote:

No error log.
+ Thanks. Has SpotCollector always behaved this way, or is this new behavior? If the latter, when did it first begin, and what changes did you make to your hardware or software around that time?

       73,

              Dave, AA6YQ
I think it was ok before I integrated DxLabs with WSJT-X FT8.
John N1JM

Re: Congratulations Dave

Russ Ravella
 

Wow Dave, very nice!  Beautiful phrasing.  Very “musical”.  Could that be a Steinway “B” ?

On May 28, 2019, at 8:54 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

On Sat, May 18, 2019 at 08:43 PM, jgmags2000 wrote:

Still playing Rachmaninoff?

+ Still trying. These two preludes are the current "state of my art":

     <http://www.ambersoft.com/Piano/Rachmaninoff%20Prelude%20Op%2032%20nr%2010.mp3>

      http://www.ambersoft.com/Piano/Rachmaninoff%20Prelude%20Op%2032%20nr%2012.mp3>

 

        73,
              Dave, AA6YQ

 
 
 
 
 

Importing ADIF Log from RumlogNG

John Merrill
 

I get QSO date errors. I try to import it as a standard ADIF file. There is no other choice for RumlogNG.
73, John N1JM

Re: Congratulations Dave

Dave AA6YQ
 

+ AA6YQ comments below

Wow Dave, very nice! Beautiful phrasing. Very “musical”. Could that be a Steinway “B” ?

+ Thanks, but still a long way to go. The piano is a Yamaha C3.

Dave

Re: Call Column in Spot Collector

Dave AA6YQ
 

+ AA6YQ comments below

No error log. I added another column to see what would happen and now the Callsign column does not collapse.

+ How many columns are now being displayed?

Dave

Re: Importing ADIF Log from RumlogNG

Dave AA6YQ
 

+ AA6YQ comments below

I get QSO date errors. I try to import it as a standard ADIF file. There is no other choice for RumlogNG.

+ Please attach the ADIF file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ
_._,_._,_

Re: Congratulations Dave

Russ Ravella
 

Yeah, well Rachmaninoff said the same thing his whole life.

Lotta bass for a 6’ piano. A very nice specimen.

On May 28, 2019, at 11:57 PM, Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

Wow Dave, very nice! Beautiful phrasing. Very “musical”. Could that be a Steinway “B” ?

+ Thanks, but still a long way to go. The piano is a Yamaha C3.

Dave




Re: Congratulations Dave

John K3TN
 

Well deserved! 

73 John K3TN

DXKeeper window keeps randomly changing configuration to larger format

John K3TN
 

Haven't been able to figure this one out:

Pretty much on a daily basis, the DXKeeper main window upper screen will expand to a larger format, usually by causing the QSL box on the confg screen to be checked, occasionally it is the Awards box. Unchecking those boxes returns DXkeeper display to my preferred size that fits on my screen.

Is there some setting that could be causing that to happen?

Thanks and 73 John K3TN

Re: DXCC Credit Analysis Actions

Pete Smith
 

Oh I know they exist, Joe - I have a number of them myself.  Fortunately, my DXKeeper log goes back to 1971, so I'll be able to find most of them.  There may be a few issues, because that's also the year I got my first DXCC, meaning that the first hundred countries won't be in this log anyway.

This is all a little beside the point, anyhow - pre-1971 DXCC was done by manual checking and manual record-keeping, so there's no doubt - each of those DXCC codes represents a QSO and a QSL card deemed valid by ARRL.  When it comes to QSOs confirmed by card, ARRL's blessing is all that really matters now.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 5/28/2019 11:17 PM, Joe Subich, W4TV wrote:


I can attest to the "Country Number Only" entries.  I have 867 of
them: 299 Mixed, 274 CW, 294 Phone.  I had to manually link every
one of them to the actual QSO/Card entry in my log.

Worse yet, since they were "number only",  I had to dig out my old
record sheet (the DXCC list) and look up the call written on the
paper record before I could figure out with which QSO the credit
belonged.  Pete, at least you have callsign and year to make the
linking much easier.

73,

   ... Joe, W4TV


On 2019-05-28 10:26 PM, BILL KENNAMER wrote:
My oldest QSO in the records reads:080Honduras (080)1945-11-15Unknown Unknown
I have Mixed credit only for that contact, although I also have Honduras on all bands, and those are also in the LOTW records.
Bill


Sent from Yahoo Mail for iPad


On Tuesday, May 28, 2019, 6:44 PM, Dave AA6YQ <aa6yq@...> wrote:

+ Here's an example of a DXCC credit awarded to a QSO I made I in 1991.

<http://www.dxlabsuite.com/dxkeeper/9Q5UN.jpg>

+ Note that it specifies

1. the callsign

2. the DXCC entity name, with its "country code" in parenthesis

3. the date

4. the mode

5. the band

+ In my experience - which began when I received my novice ticket in January 1990 - almost all DXCC credits provide the above information, though some of the information may be inaccurate due to shortcuts taken or data entry errors.

+ There was a time when submitting a QSL card for DXCC credit did not result in your receiving credit for the entity, entity-band, and entity-mode; only the credit you requested was granted. DXKeeper provides the ability to specify "entity credit only", "entity-band credit only", and "entity-mode credit only" if you have these situations; alternatively, you can resubmit the QSL card to the ARRL and receive DXCC credit for all "components".

         73,

               Dave, AA6YQ



I’d be surprised that ARRL did that much.  As I said, when we converted from paper to computer (I was in charge of that), we did not enter callsigns into the computer. We entered only the country code. All entries for mixed DXCC were mixed, no matter what mode may have been on the card. Phone credits came from phone DXCC records, etc.

There was no notation of mode, date, time, etc. at the time (1992). In fact, paper DXCC records were the original submission record that the applicant completed, and callsigns were added to the original paperwork, with new additions to the DXCC list handwritten at the bottom.

I had been logging with a computer since 1991, so was able to convert to ADIF. I then entered all QSOs before then from my handwritten longs since 1961. After doing this, I had nearly 40,000 QSOs, all of which have been entered into LOTW. The only discrepancies I ever find are those cases where I have received a card from someone who doesn’t use LOTW.  This usually is less than five QSOs, and is resolved when I make a paper submission.

I suggest you might correct a few dxkeeper entries, and resubmit to LOTW.

73

Bill
K5FUV


Sent from Yahoo Mail for iPad <https://overview.mail.yahoo.com/?.src=iOS>



On Tuesday, May 28, 2019, 2:50 PM, Pete Smith <n4zr@...> wrote:

     Bill, the problem is that ARRL apparently made the decision back when not to enter data from its pre-LOTW/pre-computer era records beyond the callsign, band, mode, and year of each QSO.  All of the credits in question derived from actual cards reviewed and accepted by ARRL, so I contend that a better approach would be for DXKeeper to look for QSOs with the station, mode and band in the *year*, and only balk if there is none, or more than one that fits.  That would take care of 99 percent of mine.
    
     73, Pete N4ZR
     Check out the Reverse Beacon Network
     at <http://reversebeacon.net> <http://reversebeacon.net> , now
     spotting RTTY activity worldwide.
     For spots, please use your favorite
     "retail" DX cluster.
     On 5/28/2019 3:33 PM, BILL KENNAMER wrote:
    
     I had no problem with mine entering QSOs back to 1961, but I entered the correct date and time.

     When these cards were originally entered in DXCC records, they were entered into the system 38 with country code number only, no call sign.  Even given that, I have no discrepancies.

     73

     Bill K5FUV
               Sent from Yahoo Mail for iPad <https://overview.mail.yahoo.com/?.src=iOS>
         
     On Tuesday, May 28, 2019, 1:59 PM, Pete Smith <n4zr@...> <mailto:n4zr@...>  wrote:

         Still trying to get the DXCC status in my log to match with DXCC info from ARRL.  Ran this routine and it worked great for recent QSOs, updating their QSL status to verified, but it left 525 DXCC credits in the status "no exact match found in log."  Each and every one of these is a QSO back in the 70s, 80s and 90s, and the reason why no match was found is that  there is no date in ARRL's record other than the year - for example, 1976-01-01.The instructions for this report say that it should not be used for old QSOs, but not why.  I guess this explains it.
        
         Is there any other way I can update the QSL status for these QSOs in bulk? They are all shown by DCXX as "card", so there is no doubt (I think) that I deserve the DXCC credit.  I'd just like to avoid 525 separate operations.
        
         --
                  73, Pete N4ZR
         Check out the Reverse Beacon Network
         at <http://reversebeacon.net> <http://reversebeacon.net> , now
         spotting RTTY activity worldwide.
         For spots, please use your favorite
         "retail" DX cluster.


  <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>     Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
















Re: Congratulations Dave

Jack - WE5ST
 

Wish we could combine the recorded collective applause in a single reply. Wonderful! 

Re: Congratulations Dave

N3HEE
 

Congrats Dave !  Thanks for all that you do for the ham radio community.  We certainly appreciate it.

Re: Congratulations Dave

Stephen Rabinowitz
 

Compared with Rachmaninoff, CW seems trivial.
All the best, Dave.
73, Steve K2SN

Sent from BlueMail

On May 28, 2019, at 11:54 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

On Sat, May 18, 2019 at 08:43 PM, jgmags2000 wrote:

Still playing Rachmaninoff?

+ Still trying. These two preludes are the current "state of my art":

     <http://www.ambersoft.com/Piano/Rachmaninoff%20Prelude%20Op%2032%20nr%2010.mp3>

      http://www.ambersoft.com/Piano/Rachmaninoff%20Prelude%20Op%2032%20nr%2012.mp3>

 

        73,
              Dave, AA6YQ

 

 

 

 

 

Re: DXKeeper window keeps randomly changing configuration to larger format

Dave AA6YQ
 

+ AA6YQ comments below

Haven't been able to figure this one out:

Pretty much on a daily basis, the DXKeeper main window upper screen will expand to a larger format, usually by causing the QSL box on the confg screen to be checked, occasionally it is the Awards box. Unchecking those boxes returns DXkeeper display to my preferred size that fits on my screen.

+ When DXKeeper encounters a logged QSO with an item that is erroneous or invalid, it automatically makes visible the panel in which that item is present so that you see the item’s flashing blue or red label.

73,

Dave, AA6YQ

Re: How to save a DX Commander setup for a radio

Marty King
 

Just the information I needed.
Thanks
Marty - N7MKA