Topics

LoTW "All confirmed"


Dave Cole
 

The net was built for just this... Success via redundancy.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 4/1/20 7:49 AM, Christopher Scibelli via Groups.Io wrote:
I've never been able to use "All Confirmed".  I have over 60K QSOs and I've never been able to do an all confirmed under normal conditions never mind when the net is being taxed to the max.  I'm amazed the net is still up. The IT industry is doing an amazing job.  All of America is doing amazing things.
73,
Chris  NU1O
-----Original Message-----
From: Scott Davis via Groups.Io <SNKDavis=aol.com@groups.io>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Wed, Apr 1, 2020 10:28 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"
Hi All,
Thanks for the reports.  Yes, I just tried it and got the same results here as well.  Obviously nothing changed with AC Log.  Apparently there is either a problem with the LoTW server, or ARRL has intentionally reconfigured the server's behavior, presumably to reduced demand on the server.
73, Scott
N3FJP
_http://www.n3fjp.com_ <http://www.n3fjp.com/>
/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 <http://www.n3fjp.com/Faith.htm>the hope that you have <http://www.n3fjp.com/Faith.htm>_. But do this with gentleness and respect/...
-----Original Message-----
From: Bob Stothfang <bobstothfang@gmail.com>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 1, 2020 9:57 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"
I have the same symptoms as Steve, AI3KS has experienced and I have used his same work around to accomplish the task.
My symptoms started at the same time as his also.
Bob - W8RES
On 04/01/2020 09:45, Scott Davis via Groups.Io wrote:
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:
An external service (LoTW, QRZ, etc.) or hardware device suddenly stopped working? <http://www.n3fjp.com/faq.html#q108>
http://www.n3fjp.com/faq.html#q108
Enjoy!
73, Scott
N3FJP
_http://www.n3fjp.com_ <http://www.n3fjp.com/>
/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 <http://www.n3fjp.com/Faith.htm>the hope that you have <http://www.n3fjp.com/Faith.htm>_. But do this with gentleness and respect/...
-----Original Message-----
From: AI3KS <AI3KS.01@gmail.com> <mailto:AI3KS.01@gmail.com>
To: N3FJPSoftwareUsers@groups.io <mailto: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
--


Christopher Scibelli
 

I've never been able to use "All Confirmed".  I have over 60K QSOs and I've never been able to do an all confirmed under normal conditions never mind when the net is being taxed to the max.  I'm amazed the net is still up. The IT industry is doing an amazing job.  All of America is doing amazing things.

73,

Chris  NU1O


-----Original Message-----
From: Scott Davis via Groups.Io <SNKDavis@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Wed, Apr 1, 2020 10:28 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"

Hi All,

Thanks for the reports.  Yes, I just tried it and got the same results here as well.  Obviously nothing changed with AC Log.  Apparently there is either a problem with the LoTW server, or ARRL has intentionally reconfigured the server's behavior, presumably to reduced demand on the server.


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: Bob Stothfang <bobstothfang@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 1, 2020 9:57 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"

I have the same symptoms as Steve, AI3KS has experienced and I have used his same work around to accomplish the task.
My symptoms started at the same time as his also.

Bob - W8RES


On 04/01/2020 09:45, Scott Davis via Groups.Io wrote:
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

--


AI3KS
 

Thanks Scott.

On 20/04/01 10:27, Scott Davis via Groups.Io wrote:
Hi All,

Thanks for the reports.  Yes, I just tried it and got the same results here as well.  Obviously nothing changed with AC Log.  Apparently there is either a problem with the LoTW server, or ARRL has intentionally reconfigured the server's behavior, presumably to reduced demand on the server.


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: Bob Stothfang <bobstothfang@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 1, 2020 9:57 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"

I have the same symptoms as Steve, AI3KS has experienced and I have used his same work around to accomplish the task.
My symptoms started at the same time as his also.

Bob - W8RES


On 04/01/2020 09:45, Scott Davis via Groups.Io wrote:
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

--


Scott Davis
 

Hi All,

Thanks for the reports.  Yes, I just tried it and got the same results here as well.  Obviously nothing changed with AC Log.  Apparently there is either a problem with the LoTW server, or ARRL has intentionally reconfigured the server's behavior, presumably to reduced demand on the server.


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: Bob Stothfang <bobstothfang@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 1, 2020 9:57 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"

I have the same symptoms as Steve, AI3KS has experienced and I have used his same work around to accomplish the task.
My symptoms started at the same time as his also.

Bob - W8RES


On 04/01/2020 09:45, Scott Davis via Groups.Io wrote:
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

--


Bob Stothfang
 

I have the same symptoms as Steve, AI3KS has experienced and I have used his same work around to accomplish the task.
My symptoms started at the same time as his also.

Bob - W8RES


On 04/01/2020 09:45, Scott Davis via Groups.Io wrote:
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

--


Christopher Scibelli
 

The ARRL is doing a marvelous job keeping W1AW on the air albeit with a reduced sked and with keeping LoTW up as they all work from home.  Zack, W1VT, is an employee of the League and he has 4 PCs running 24/7 and 24 monitors.

73,

Chris  NU1O


-----Original Message-----
From: Mike Olbrisch <mike-2020@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Wed, Apr 1, 2020 10:00 am
Subject: Re: [N3FJPSoftwareUsers] LoTW "All confirmed"

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


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


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


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


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