Date   

SKCCLogger Installation Note

AC2C
 

Before you launch the downloaded self-installation file, you MUST shutdown the SKCCLogger yourself.
 
While the installer recognizes that the logger is running and offers to shut it down, it fails to do a clean shutdown of all processes.
 
-- 
Ron, AC2C
SKCC #2748S

Re: SKCCLogger v03.00.10 Pre-Release Available

Mark Swartwout, NX1K 11024 S
 

Mac version worked well on SKS.  Thanks for the great program.

Mark/NX1K
11024 S

Re: SKCCLogger v03.00.10 Pre-Release Available

Jerry WA4FQN
 

Thanks Ron, that was the issue, thought I had checked that!

Jerry

On Thu, 2018-07-26 at 19:26 -0400, AC2C wrote:
Jerry -

Make sure you have "N9OL" and not "N90L" - Oh instead of zero. If you have it that way, please send me the log file and I'll have a look.

Ron


From: SKCCLogger@groups.io [mailto:SKCCLogger@groups.io] On Behalf Of Jerry WA4FQN
Sent: Thursday, July 26, 2018 6:47 PM
To: SKCCLogger@groups.io
Subject: Re: [SKCCLogger] SKCCLogger v03.00.10 Pre-Release Available

Ron,

Followed these instructions to resolve QSO discrepancies in SKCCLogger, and still have one that I cannot resolve.  I have a QSO with N90L in 2016 that was left with no SKCC # after running "Add SKCC Numbers to Log" the second time.  Went to the SKCC memberlist, found his number is 4014S, and entered it into the QSO record and saved.  Upon running the log file award processor, still had a discrepancy for one file.  Went back and ran "Add SKCC numbers to log" once again, and found that N9OL was once again listed with no membership number.  Upon hitting the "Check" button beside his call, it comes up "NONE."  What gives?

Jerry
WA4FQN



On Thu, 2018-07-26 at 09:32 -0700, AC2C wrote:
Mike -

When a log entry is analyzed but not added to the SKCC Database, it means that something with the QSO makes it invalid.

The most common issues are:
• The other station was not a member at the time of the QSO
• The callsign and SKCC Number do not match
Doing the following USUALLY finds the errant entries:
• Use the Tools Menu "Add SKCC Numbers to Log" option.
• Any log entries where the SKCC Number and Callsign don't match will have the SKCC Number set to blank.
• When done, click on the "SKCC" column heading in the Main windows log list box. Clicking the column sorts the log list by that column.
• Now scroll the list all the way to the top or bottom to see if any SKCC Numbers were set to blank - you might find two of them.
• Running the Add SKCC Numbers tool a second time will (almost always) insert the correct SKCC Number for the callsign.
• The "almost always" comment covers the case where a callsign has been associated with more than one member and the logger can't figure out which one you logged. A search of the membership roster should help you figure it out.
If this doesn't work for you, send me your log file and I'll see if I can find out what's going on.

73,
Ron 





Re: SKCCLogger v03.00.10 Pre-Release Available

AC2C
 

Jerry -

Make sure you have "N9OL" and not "N90L" - Oh instead of zero. If you have it that way, please send me the log file and I'll have a look.

Ron

From: SKCCLogger@groups.io [mailto:SKCCLogger@groups.io] On Behalf Of Jerry WA4FQN
Sent: Thursday, July 26, 2018 6:47 PM
To: SKCCLogger@groups.io
Subject: Re: [SKCCLogger] SKCCLogger v03.00.10 Pre-Release Available

Ron,

Followed these instructions to resolve QSO discrepancies in SKCCLogger, and still have one that I cannot resolve. I have a QSO with N90L in 2016 that was left with no SKCC # after running "Add SKCC Numbers to Log" the second time. Went to the SKCC memberlist, found his number is 4014S, and entered it into the QSO record and saved. Upon running the log file award processor, still had a discrepancy for one file. Went back and ran "Add SKCC numbers to log" once again, and found that N9OL was once again listed with no membership number. Upon hitting the "Check" button beside his call, it comes up "NONE." What gives?

Jerry
WA4FQN



On Thu, 2018-07-26 at 09:32 -0700, AC2C wrote:
Mike -

When a log entry is analyzed but not added to the SKCC Database, it means that something with the QSO makes it invalid.

The most common issues are:
• The other station was not a member at the time of the QSO
• The callsign and SKCC Number do not match
Doing the following USUALLY finds the errant entries:
• Use the Tools Menu "Add SKCC Numbers to Log" option.
• Any log entries where the SKCC Number and Callsign don't match will have the SKCC Number set to blank.
• When done, click on the "SKCC" column heading in the Main windows log list box. Clicking the column sorts the log list by that column.
• Now scroll the list all the way to the top or bottom to see if any SKCC Numbers were set to blank - you might find two of them.
• Running the Add SKCC Numbers tool a second time will (almost always) insert the correct SKCC Number for the callsign.
• The "almost always" comment covers the case where a callsign has been associated with more than one member and the logger can't figure out which one you logged. A search of the membership roster should help you figure it out.
If this doesn't work for you, send me your log file and I'll see if I can find out what's going on.

73,
Ron

Re: SKCCLogger v03.00.10 Pre-Release Available

Jerry WA4FQN
 

Ron,

Followed these instructions to resolve QSO discrepancies in SKCCLogger, and still have one that I cannot resolve.  I have a QSO with N90L in 2016 that was left with no SKCC # after running "Add SKCC Numbers to Log" the second time.  Went to the SKCC memberlist, found his number is 4014S, and entered it into the QSO record and saved.  Upon running the log file award processor, still had a discrepancy for one file.  Went back and ran "Add SKCC numbers to log" once again, and found that N9OL was once again listed with no membership number.  Upon hitting the "Check" button beside his call, it comes up "NONE."  What gives?

Jerry
WA4FQN



On Thu, 2018-07-26 at 09:32 -0700, AC2C wrote:
Mike -

When a log entry is analyzed but not added to the SKCC Database, it means that something with the QSO makes it invalid.

The most common issues are:
  • The other station was not a member at the time of the QSO
  • The callsign and SKCC Number do not match
Doing the following USUALLY finds the errant entries:
  • Use the Tools Menu "Add SKCC Numbers to Log" option.
  • Any log entries where the SKCC Number and Callsign don't match will have the SKCC Number set to blank.
  • When done, click on the "SKCC" column heading in the Main windows log list box. Clicking the column sorts the log list by that column.
  • Now scroll the list all the way to the top or bottom to see if any SKCC Numbers were set to blank - you might find two of them.
  • Running the Add SKCC Numbers tool a second time will (almost always) insert the correct SKCC Number for the callsign.
  • The "almost always" comment covers the case where a callsign has been associated with more than one member and the logger can't figure out which one you logged. A search of the membership roster should help you figure it out.
If this doesn't work for you, send me your log file and I'll see if I can find out what's going on.

73,
Ron

Re: SKCCLogger v03.00.10 Pre-Release Available

Mike - KK7H 12301S
 

Hi Ron
That took care of the issue. I would not have found the bad records by just looking over the entries.
The new program is working great here.
Thanks
73
Mike   KK7H  12301S

Re: SKCCLogger v03.00.10 Pre-Release Available

Brian - KQ4MM
 

MAC version worked flawlessly for the sprint .... 
--
Brian - KQ4MM 17450T

Re: SKCCLogger v03.00.10 Pre-Release Available

Mike - KK7H 12301S
 

Hi Ron
Thanks for the info. I'll give it a try. I now know where to look.
Thanks again.
73
Mike

Re: SKCCLogger v03.00.10 Pre-Release Available

AC2C
 

Mike -

When a log entry is analyzed but not added to the SKCC Database, it means that something with the QSO makes it invalid.

The most common issues are:
  • The other station was not a member at the time of the QSO
  • The callsign and SKCC Number do not match
Doing the following USUALLY finds the errant entries:
  • Use the Tools Menu "Add SKCC Numbers to Log" option.
  • Any log entries where the SKCC Number and Callsign don't match will have the SKCC Number set to blank.
  • When done, click on the "SKCC" column heading in the Main windows log list box. Clicking the column sorts the log list by that column.
  • Now scroll the list all the way to the top or bottom to see if any SKCC Numbers were set to blank - you might find two of them.
  • Running the Add SKCC Numbers tool a second time will (almost always) insert the correct SKCC Number for the callsign.
  • The "almost always" comment covers the case where a callsign has been associated with more than one member and the logger can't figure out which one you logged. A search of the membership roster should help you figure it out.
If this doesn't work for you, send me your log file and I'll see if I can find out what's going on.

73,
Ron

Re: SKCCLogger v03.00.10 Pre-Release Available

Mike - KK7H 12301S
 

Downloaded and installed, and all seems to working great.  But I do have a question. I only have valid skcc contacts in the log and if I do log a contact that is not a member or not using a straight key, I remove it and place it into my master log HRD. When I run the award application process and process the logfile, it analyzes 1583 records, it then adds 1581 records to the database. I have not been able to figure out why the difference.  Two records is not a big deal, but just scratching my head to figure out why.
Thanks for all that you do for the group.
Mike Hamner  KK7H 12301S

Re: SKCCLogger v03.00.10 Pre-Release Available

Brian - KQ4MM
 

Downloaded, will run the MAC version in tonights SKS

--
Brian - KQ4MM 17450T

Re: SKCCLogger v03.00.10 Pre-Release Available

Cliff Clark AG7CC
 

I’ll give it a try tonight on Linux.

On Mon, Jul 23, 2018 at 09:04 AC2C <AC2C@...> wrote:
Unless problems are found in testing, I plan to release version v03.00.10 on 1 August.

Installation files for Linux, Mac, and Windows are now available for download in the Files/Current Release section of this group.

I have tested the Windows versions quite a bit but sure would like to hear from some Linux and Mac users prior to 1 August.

73 to all,
Ron, AC2C

Re: SKCCLogger v03.00.10 Pre-Release Available

AC2C
 

Here's a quick snapshot of fixes and enhancements from v03.00.09:
  • Fixed a bug with RagChew QSOs that spanned a date changed.
  • Fixed an error raised when a log file path was not absolute.
  • Added basic gridsquare tracking capability.
  • The main processing portion of the award processor now operates as a process "thread" so that the GUI can be updated smoothly while displaying a progress bar.
  • Both load and save ADIF Log file processing is now handled by a process thread. A progress bar is displayed that will be visible when large log files are loaded or saved.
  • The Main window log list box is now invisible while the log is being loaded - this makes the processing considerably faster.
  • The Add Log Entry Callsign "Check" Button now will display a list of similar callsigns if the entered callsign does not exist as-is. You must enter at least 3 characters and you can use a percent symbol (%) as a wildcard. This can be handy when QRM or QSB keeps you from copying a complete callsign.

Re: SKCCLogger v03.00.10 Pre-Release Available

N3MLB
 

Ron,

Thank you for all the work you do. Can't wait to get home and test out the new versions.  

-Chris
N3MLB


On Mon, Jul 23, 2018, 12:04 PM AC2C <AC2C@...> wrote:
Unless problems are found in testing, I plan to release version v03.00.10 on 1 August.

Installation files for Linux, Mac, and Windows are now available for download in the Files/Current Release section of this group.

I have tested the Windows versions quite a bit but sure would like to hear from some Linux and Mac users prior to 1 August.

73 to all,
Ron, AC2C

SKCCLogger v03.00.10 Pre-Release Available

AC2C
 

Unless problems are found in testing, I plan to release version v03.00.10 on 1 August.

Installation files for Linux, Mac, and Windows are now available for download in the Files/Current Release section of this group.

I have tested the Windows versions quite a bit but sure would like to hear from some Linux and Mac users prior to 1 August.

73 to all,
Ron, AC2C

Re: Interim version v03.00.09D has been released

Bill Ellis - WB9CAC
 

Ron,

Just downloaded ver.09D. Runs fast and when scanning the log for awards, the dialog box showing the progress is a welcome addition..

73's/Thanks,

Bill, WB9CAC
SKCC # 3830T
--------------------------------------------
On Sat, 6/16/18, AC2C <@RonBower> wrote:

Subject: [SKCCLogger] Interim version v03.00.09D has been released
To: SKCCLogger@groups.io
Date: Saturday, June 16, 2018, 10:23 AM

I have released SKCCLogger interim
version v03.00.09D. Unless there are issues discovered, this
may well be released as v03.00.10 in a couple weeks.

The revision history section of the User Guide is
attached so you can quickly learn of the changed made from
the basic v03.00.09 release.

For me, the
significant changes are in the award processing, load/save
log file processing, and the partial callsign lookup
feature.

73 to all,
Ron, AC2C

Interim version v03.00.09D has been released

AC2C
 

I have released SKCCLogger interim version v03.00.09D. Unless there are issues discovered, this may well be released as v03.00.10 in a couple weeks.

The revision history section of the User Guide is attached so you can quickly learn of the changed made from the basic v03.00.09 release.

For me, the significant changes are in the award processing, load/save log file processing, and the partial callsign lookup feature.

73 to all,
Ron, AC2C

Re: Will webpage move require a new SKCCLogger version

Alton N4IDH
 

We should be good.  The skimmer looks to the site for a data file.  When we update the name server with the new host, the skimmer will look to the new host.  It might take an hour for the dns server change to propagate throughout the internet.
i have verified the site to be building th data file as required.

Alton
N4IDH
12,228S
Webmaster

Re: Will webpage move require a new SKCCLogger version

TOM BINGHAM
 

As I understand it, this will be transparent to those that use the SKCCLogger.  There may be a hiccup or two but the webmaster and related programmers have gone to great lengths to create a step by step process that has been reviewed numerous times for consistency and service provision prior to making the switch.

The programming group and webmasters did a similar switch when SKCC converted from one database product to another for the K3Y Anniversary event several years ago and that was, for the most part, seamless and transparent.

73!
Tom

On 6/13/2018 05:57 PM, Bruce Forsberg wrote:
I got a message today from the SKCC group that the web page is moving. Just wondering if this will require a new SKCCLogger version for DB updates?

Thanks,
Bruce, WB6IZG, 17714T
--
Tom Bingham WB7EUX
http://www.wb7eux.radio/
SKCC 9833S
NAQCC 6346

Will webpage move require a new SKCCLogger version

Bruce Forsberg
 

I got a message today from the SKCC group that the web page is moving. Just wondering if this will require a new SKCCLogger version for DB updates?

Thanks,
Bruce, WB6IZG, 17714T