1. N3FJPSoftwareUsers@groups.io
   Date   
Re: LoTW "All confirmed"

Mike Olbrisch
 

And of course as always, LoTW queue status is just one click away.

 

http://www.arrl.org/logbook-queue-status

 

Long ago, I’ve seen delays of over 2 days.  In the last few years I have seen some delays of less than 3 hours after a major contest (like Field Day).  Over the last 12 hours the delay has reached 15 minutes, but seems to be under a minute nearly every other hour, except right now, running 2+ minutes.  (Who just uploaded their whole log?)  <grin>.

 

If you’re having slow return data from LoTW, check it at the above link.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Scott Davis via Groups.Io
Sent: Wednesday, April 1, 2020 7:45 AM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"

 

Hi Steve,

 

Thanks for your e-mail.  I understand that between the WPX contest last weekend and increased number of users with so many of us home, the LoTW server is experiencing heightened demand.  Please see this FAQ here:

 

 

 

Enjoy!

73, Scott

N3FJP

 

Serving the Amateur Radio community with contesting and general logging software since 1997.

 

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...

 

-----Original Message-----
From: AI3KS <AI3KS.01@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 1, 2020 9:37 am
Subject: [N3FJPSoftwareUsers] LoTW "All confirmed"

Using ACLog 6.6, LoTW Manager 1.9.

I do an "all confirmed" for LOTW several times a year. Doing that this morning it was extremely quick. Looking at the raw data, the start date was 2020-03-04. Coincidentally, that was the last time I updated the log. I tried that with all three of my callsighns and the result was the same. The only way I could get a complete history was to to a "confirmed since" and change the date to the date of the original callsign issue.

Is my config hosed or is there something else going on?

Steve, AI3KS
Re: LoTW "All confirmed"

AI3KS
 

Scott,

I thought that too, but if I do a confirmed since and change the date, it works as expected.

Here is from my LoTW manager when doing an all confirmed for my novice callsign:

ARRL Logbook of the World Status Report
Generated at 2020-04-01 13:51:48
for ai3ks
Query:
    OWNCALL: WN3SOR
   QSL ONLY: YES
  QSL SINCE: 2020-03-04 14:59:07

Here is a confirmed since:

ARRL Logbook of the World Status Report
Generated at 2020-04-01 13:55:23
for ai3ks
Query:
    OWNCALL: WN3SOR
   QSL ONLY: YES
  QSL SINCE: 1972-05-01 00:00:00

Steve, AI3KS
Re: LoTW "All confirmed"

Scott Davis
 

Hi Steve,

Thanks for your e-mail.  I understand that between the WPX contest last weekend and increased number of users with so many of us home, the LoTW server is experiencing heightened demand.  Please see this FAQ here:


http://www.n3fjp.com/faq.html#q108

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: AI3KS <AI3KS.01@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 1, 2020 9:37 am
Subject: [N3FJPSoftwareUsers] LoTW "All confirmed"

Using ACLog 6.6, LoTW Manager 1.9.
I do an "all confirmed" for LOTW several times a year. Doing that this morning it was extremely quick. Looking at the raw data, the start date was 2020-03-04. Coincidentally, that was the last time I updated the log. I tried that with all three of my callsighns and the result was the same. The only way I could get a complete history was to to a "confirmed since" and change the date to the date of the original callsign issue.

Is my config hosed or is there something else going on?

Steve, AI3KS
Re: Clublog upload no longer functional

David Galletly
 

Thanks all! Problem was indeed a password mixup.

Dave KM2O



On Wed, Apr 1, 2020 at 9:39 AM Dennis - WU6X <wu6x@...> wrote:
Hi Dave,
Log into your ClubLog account and check your Profile to make sure something there hasn't changed. I can't think of anything else that might be an issue, except maybe a mis-stored password in Windows.
73, Dennis-WU6X

Re: Question for the Polish contest this weekend

Scott Davis
 

Hi Steven,

Thanks for your e-mail.  Please see this FAQ here:




That said, if you or anyone on this group have time to test out the program, as will as a way to modify the Cabrillo submission file so it will be accepted, please let the group know!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Stephen Walls <swalls46@...>
To: n3fjpsoftwareusers@groups.io <n3fjpsoftwareusers@groups.io>
Sent: Wed, Apr 1, 2020 8:52 am
Subject: [N3FJPSoftwareUsers] Question for the Polish contest this weekend

Is there a program that will 'accommodate' their exchange.

Looks like the WPX program would possibly work

just enter 1 for contact #,  and enter the province for prefix

Any Comments  or Suggestions ????

EXCHANGE GROUPS:
  • Polish stations send a report, consisting of a signal report (RS or RST) plus the letter of the province designator (e.g., 59 B). The 16 province designators are: B, C, D, F, G, J, K, L, M, O, P, R, S, U, W and Z.
  • Foreign stations send a report consisting of a signal report (RS or RST) plus contact number beginning with 001 (e.g., 59 001).


Thanks,   Steve  K4ELI
Re: Clublog upload no longer functional

Dennis - WU6X
 

Hi Dave,
Log into your ClubLog account and check your Profile to make sure something there hasn't changed. I can't think of anything else that might be an issue, except maybe a mis-stored password in Windows.
73, Dennis-WU6X
LoTW "All confirmed"

AI3KS
 

Using ACLog 6.6, LoTW Manager 1.9.

I do an "all confirmed" for LOTW several times a year. Doing that this morning it was extremely quick. Looking at the raw data, the start date was 2020-03-04. Coincidentally, that was the last time I updated the log. I tried that with all three of my callsighns and the result was the same. The only way I could get a complete history was to to a "confirmed since" and change the date to the date of the original callsign issue.

Is my config hosed or is there something else going on?

Steve, AI3KS
Question for the Polish contest this weekend

Stephen Walls
 

Is there a program that will 'accommodate' their exchange.

Looks like the WPX program would possibly work

just enter 1 for contact #,  and enter the province for prefix

Any Comments  or Suggestions ????

EXCHANGE GROUPS:
  • Polish stations send a report, consisting of a signal report (RS or RST) plus the letter of the province designator (e.g., 59 B). The 16 province designators are: B, C, D, F, G, J, K, L, M, O, P, R, S, U, W and Z.
  • Foreign stations send a report consisting of a signal report (RS or RST) plus contact number beginning with 001 (e.g., 59 001).


Thanks,   Steve  K4ELI
Re: DX Spotting

Pat Whelton
 

Hi Mel.  Not sure this will help or not but it might be worth checking out.  I grew tired of all the FT4 and FT8 spots that kept hitting DX spots and was hoping there was a way to block them.  Scott made a change sometime within the last year or so to block all the FT4/FT8 and I’ve been a happy camper ever since.  It’s possible that somehow your settings got changed to block these unwanted spots.

 

You can check by going to:

  • Settings
  • DX Spotting
  • Configure
  • More Filtering
  • Under More Filtering place a check mark by “Block Digital”.

 

After making this change it got rid of all the stuff above 14.080 and made the DX spots a whole lot more meaningful for me.  For some reason the FT4/FT8 folks feel they have to spot every contact they make.

 

You may have a totally different problem but it might be worth looking into.

 

Good luck.

 

Pat – KZ5J

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Malcolm Pelham
Sent: Tuesday, March 31, 2020 9:47 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] DX Spotting

 

I have been using N3FJP software for at least 9 years and have never had a problem I could not solve.  But since I have upgraded to 6.6 my DX Spots do not post.  Every once and awhile I will have one post, but recently few and far between.  My FT-8 DX contacts do not post, and were posting prior to version 6.6.  I can't even post when I do it directly from DX Spot.  So I was wonsdering if anyone has seen this problem, and are there any fixes.  Attached please find a screen shot of my DX Spotting setup.

 

Thanks for your help

 

Mal

WF5K
Re: Hamvention QSO Party

Scott Davis
 

Hi Ken,

Thanks for the great information!  That might work, as no Cabrillo file is required.  Scores are just entered on 3830.

Thanks for thinking outside the box!  :)

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Ken Gunther <Yahoo_groups@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Mar 31, 2020 3:20 pm
Subject: Re: [N3FJPSoftwareUsers] Hamvention QSO Party

    I have an interesting idea, use the program for the IARU HF contest. The exchange for the IARU HF contest is RST and ITU zone. I tested and the the N3FJP program will accept various numbers between 1952 and 2020 for ITU zone, those numbers are the years of the Hamvention. You can ignore the score since there are no multipliers.

    Just a crazy idea, I wonder if the Cabrillo file would be acceptable.

    What does everybody think about this?

                                Ken WB2KWC

On 3/30/2020 06:24, Scott Davis via Groups.Io wrote:
Hi Mitch,

Thanks for your e-mail.  I would love to write a program for the Hamvention QSO Party, but there just aren't enough hours in the day.  With over 100 individually customized logging programs that I am supporting already, along with all the daily e-mail questions, I have to be sure to only add programs to the package that will continue to be widely used beyond one year.

Please see this link for more details here:


I'm sorry that I didn't have the answer that you were hoping for.

That said, your score is just the number of QSOs, so you could log your contact activity in AC Log.

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: mitch matteau <n0dim@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Mon, Mar 30, 2020 5:30 am
Subject: [N3FJPSoftwareUsers] Hamvention QSO Party

See https://hamvention.org/hamvention-qso-party-saturday-may-16/

Any chance of creating a contest logging software version for this special event?

73

Mitch N0DIM

Re: DX Spotting

Scott Davis
 

Hi Mal,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  There were no DX Spotting changes with the 6.6 upgrade and o other problem reports.  If you are only watching for the spots from AC Log's main form, make sure your Filter settings are not blocking your posts.  No filters are applied on the DX spotting form.

Since you are not able to post spots from DXSpots.com either, unless your filters are at play, the problem is external to AC Log.

Good luck!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Malcolm Pelham <malcolm.pelham@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Mar 31, 2020 10:47 pm
Subject: [N3FJPSoftwareUsers] DX Spotting

I have been using N3FJP software for at least 9 years and have never had a problem I could not solve.  But since I have upgraded to 6.6 my DX Spots do not post.  Every once and awhile I will have one post, but recently few and far between.  My FT-8 DX contacts do not post, and were posting prior to version 6.6.  I can't even post when I do it directly from DX Spot.  So I was wonsdering if anyone has seen this problem, and are there any fixes.  Attached please find a screen shot of my DX Spotting setup.

Thanks for your help

Mal
WF5K
Elecraft K3 [Programming F Keys]

Scott Davis
 


Hi All,

Elecraft users, please see Mark's good information below:

-----Original Message-----
To: Snkdavis <SNKDavis@...>
Sent: Tue, Mar 31, 2020 7:45 pm
Subject: Elecraft K3

Scott,
If anyone ever asks about how to program the "F" keys in the logging software to trigger the DVR memories on a K3/K3S, the following commands will perform the function when used as instructed in the logging program notes.  I couldn't get the F1 key to loop play the command but Elecraft users can program the loop function on the radio itself if desired.
Memory 1 - "SWT21;"
Memory 2 - "SWT31;"
Memory 3 - "SWT35;"
Memory 4 - "SWT39;"

73
Mark McLauchlin KN7T


73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...
DX Spotting

Malcolm Pelham <malcolm.pelham@...>
 

I have been using N3FJP software for at least 9 years and have never had a problem I could not solve.  But since I have upgraded to 6.6 my DX Spots do not post.  Every once and awhile I will have one post, but recently few and far between.  My FT-8 DX contacts do not post, and were posting prior to version 6.6.  I can't even post when I do it directly from DX Spot.  So I was wonsdering if anyone has seen this problem, and are there any fixes.  Attached please find a screen shot of my DX Spotting setup.

Thanks for your help

Mal
WF5K

?
N3FJP Screenshot.docx

Re: Hamvention QSO Party

Ken Gunther
 

    I have an interesting idea, use the program for the IARU HF contest. The exchange for the IARU HF contest is RST and ITU zone. I tested and the the N3FJP program will accept various numbers between 1952 and 2020 for ITU zone, those numbers are the years of the Hamvention. You can ignore the score since there are no multipliers.

    Just a crazy idea, I wonder if the Cabrillo file would be acceptable.

    What does everybody think about this?

                                Ken WB2KWC

On 3/30/2020 06:24, Scott Davis via Groups.Io wrote:
Hi Mitch,

Thanks for your e-mail.  I would love to write a program for the Hamvention QSO Party, but there just aren't enough hours in the day.  With over 100 individually customized logging programs that I am supporting already, along with all the daily e-mail questions, I have to be sure to only add programs to the package that will continue to be widely used beyond one year.

Please see this link for more details here:


I'm sorry that I didn't have the answer that you were hoping for.

That said, your score is just the number of QSOs, so you could log your contact activity in AC Log.

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: mitch matteau <n0dim@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Mon, Mar 30, 2020 5:30 am
Subject: [N3FJPSoftwareUsers] Hamvention QSO Party

See https://hamvention.org/hamvention-qso-party-saturday-may-16/

Any chance of creating a contest logging software version for this special event?

73

Mitch N0DIM

Re: Clublog upload no longer functional

Christopher Scibelli
 

Password?  I dunno, but I just uploaded fine.

73,

Chris  NU1O


-----Original Message-----
From: David Galletly <d4star@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Tue, Mar 31, 2020 10:44 am
Subject: [N3FJPSoftwareUsers] Clublog upload no longer functional

I recently swapped out my shack computer to a mini Win 10. New install of latest ACL configured with transfer of log database went fine. LOTW transfer went fine as well. Now, however, Clublog gives me a 403 Forbidden error when I try to upload. No changes in my user information plus I can sign in manually to my account with no problem. What did I miss?

Thanks
Dave KM2O

Clublog upload no longer functional

David Galletly
 

I recently swapped out my shack computer to a mini Win 10. New install of latest ACL configured with transfer of log database went fine. LOTW transfer went fine as well. Now, however, Clublog gives me a 403 Forbidden error when I try to upload. No changes in my user information plus I can sign in manually to my account with no problem. What did I miss?

Thanks
Dave KM2O
Re: Previous entries disappear from the list with dx spotting

Vincent Pasquarello
 

Thank you very much!


On Mar 31, 2020, at 9:53 AM, Scott Davis via Groups.Io <SNKDavis@...> wrote:


Hi Vincent,

Thanks for your e-mail.  When you tab from the Call field, any previous contacts are listed with that station and the list will be blank if there aren't any.  You can click Settings > List Matches and deselect the Call option if you would like to disable that behavior.

Either way, there is no need to restart your PC.  Simply pressing Esc will clear the fields and relist your QSO records.

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Vincent Pasquarello <pasquarello@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Mar 31, 2020 8:29 am
Subject: [N3FJPSoftwareUsers] Previous entries disappear from the list with dx spotting

Hello, I have a question:
When I use dx spotting and click on a station, it puts the information in the boxes as I would expect.  But if I don't log that entry and click on another station, it puts that station's information in the boxes, but all of the previous contact entries on my list disappear.  I have to restart the program to see them again (at least that's the only option I have figured out.) Am I doing something wrong?  How can I still see my previous contacts on the list without restarting the program?
Thank you in advance.
Re: Previous entries disappear from the list with dx spotting

Scott Davis
 

Hi Vincent,

Thanks for your e-mail.  When you tab from the Call field, any previous contacts are listed with that station and the list will be blank if there aren't any.  You can click Settings > List Matches and deselect the Call option if you would like to disable that behavior.

Either way, there is no need to restart your PC.  Simply pressing Esc will clear the fields and relist your QSO records.

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Vincent Pasquarello <pasquarello@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Mar 31, 2020 8:29 am
Subject: [N3FJPSoftwareUsers] Previous entries disappear from the list with dx spotting

Hello, I have a question:
When I use dx spotting and click on a station, it puts the information in the boxes as I would expect.  But if I don't log that entry and click on another station, it puts that station's information in the boxes, but all of the previous contact entries on my list disappear.  I have to restart the program to see them again (at least that's the only option I have figured out.) Am I doing something wrong?  How can I still see my previous contacts on the list without restarting the program?
Thank you in advance.
Previous entries disappear from the list with dx spotting

Vincent Pasquarello
 

Hello, I have a question:
When I use dx spotting and click on a station, it puts the information in the boxes as I would expect. But if I don't log that entry and click on another station, it puts that station's information in the boxes, but all of the previous contact entries on my list disappear. I have to restart the program to see them again (at least that's the only option I have figured out.) Am I doing something wrong? How can I still see my previous contacts on the list without restarting the program?
Thank you in advance.
Re: One LoTW conformation are not being downloaded

Scott Davis
 

Hi Nickus,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  That is really unusual and there have been no changes to the LoTW code, which has been solid for years, though there was one similar report yesterday.

Here is the criteria.  Since the record is coming down on download, only 3-5 apply:

1. Your records must be successfully uploaded to LoTW.
2. Your records must be successfully downloaded from LoTW

3. The callsign must match the call of the station worked.
4. The band must match the band of the station worked.
5. The date and time in AC Log must match the date and time on the LoTW record.

Note that to speed processing, once AC Log finds a match, it doesn't continue searching your log for more matches, so if you have two contacts with the same station on the same band at the same time (such as working county line stations in a state QSO party), only one of the QSOs will be automatically marked.  When that occurs, just edit the unmarked contact and mark it manually.

If the call, band, date and time are matching, they should be marked.  I would love to know why it is not.

In any case, you can mark it manually.  Just be sure to put an L for the Confirmed By designation.

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Nickus de Vos <shack@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Mar 31, 2020 6:57 am
Subject: [N3FJPSoftwareUsers] One LoTW conformation are not being downloaded

Hi all
Yesterday I noticed my confirmed countries on LoTW doesn't match up with ACL, this despite trying to download all data a couple of times.

Weird thing is, it only seams to be this one contact, LoTW shows it as confirmed, but it doesn't update the contact to confirmed in ACL.

Any idea why this might be? Obviously I can manually mark it as confirmed by LoTW, but this kind of defeats the point, it's supposed to do it automatically.

Nickus - ZS6J

6261 - 6280 of 47141