|
Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024. ? It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date. ? If I go to ARRL LotW query page the lates QSO shown is Dec 4 That agrees with DXKeeper ? All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4. ? ? Am I missing something or is LoTW really that far behind?? I suspect I am missing something here with my DXKeeper operation. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ? -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
This listing shows the number of QSOs you have uploaded and the number of matches (QSLs) each of your call signs. It also shows the oldest and newest QSO date for each call sign. Call Sign | # QSOs | # QSLs | Oldest | Newest | W0MN | 10,229 | 4,455 | 1953-12-27 18:30:00 | 2024-12-04 19:59:56 | W0RYM | 1,105 | 3 | 1953-12-27 18:30:00 | 1978-11-05 02:20:00 | AC0RYM | 41 | 0 | 1976-01-01 17:56:00 | 1976-11-11 14:35:00 |
? ? ? I guess they are behind as show by this from the Website. Horrible. ? ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Gilbert Baron W0MN via groups.io
Sent: Sunday, February 2, 2025 6:53 AM
To: [email protected]
Subject: [DXLab] LOTW confirmations? Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024. ? It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date. ? If I go to ARRL LotW query page the lates QSO shown is Dec 4 That agrees with DXKeeper ? All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4. ? ? Am I missing something or is LoTW really that far behind?? I suspect I am missing something here with my DXKeeper operation. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
--
W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron W0MN
via groups.io wrote:
Not sure if missing something with new sync
methods or if LOTW is just behind. Looking at status the
latest LotW Sent is Y and date of latest QSO (not necessarily
confirmed, some just received and shown as a QSO on a LOTW
Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is shown
as Sent in DXKeeper should have the date sent and date
received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates
QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW really
that far behind?? I suspect I am missing something here with
my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
I really should have included a
reply from the ARRL:
Due to the ARRL cyber attack,
we find ourselves with thousands of unprocessed DXCC
applications. Please note we currently have a five month
processing delay.
We are working on May card/paper applications and completing
credit card charges for July Logbook applications. We expect
these Logbook applications to be
completed in the DXCC and Logbook programs in four to five
weeks. Once fully processed, your credits will be moved over
in your Logbook account.
Certificates and stickers will be mailed at a later date.
Online DXCC is still unavailable, but progress is being made
to restore the system.
You can obtain updates by visiting under ARRL
Systems Service Disruption.
For concerns other than inquiries as to your application
processing date or credit cards being charged, please feel
free to let me know. Take care.
On 2/2/2025 9:28 AM, William WC2L
wrote:
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron
W0MN via groups.io wrote:
Not sure if missing something with new
sync methods or if LOTW is just behind. Looking at status
the latest LotW Sent is Y and date of latest QSO (not
necessarily confirmed, some just received and shown as a QSO
on a LOTW Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is
shown as Sent in DXKeeper should have the date sent and date
received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates
QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW really
that far behind?? I suspect I am missing something here with
my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
On 2025-02-02 9:32 AM, William WC2L wrote: I really should have included a reply from the ARRL: That reply is terribly out of date. Here is what they posted on January 14 (although it is somewhat optimistic): DXCC Application Processing Caught Up 01/14/2025
DXCC? application processing is back to typical processing times.
In October, we reported that the ARRL DXCC? System had been returned
to service following work that was completed to ensure the security
and integrity of the system following the cyber-attack in May. Over
4,000 DXCC applications have been logged into the system for
processing since returning the system to service.
We are currently processing applications submitted in December, and
we continue to mail orders for paper DXCC certificates and
endorsement stickers. There were 315 certificates mailed between
December 27, 2024, and January 13, 2025.
I made a "simple" DXCC application on 2024-12-27 by LotW with no new certificates or endorsement stickers and it has still not been processed. It has now five weeks plus when simple LotW applications were being processed in three days or fewer prior to the data breach. 73, ... Joe, W4TV On 2025-02-02 9:32 AM, William WC2L wrote: I really should have included a reply from the ARRL:
/Due to the ARRL cyber attack, we find ourselves with thousands of unprocessed DXCC applications. Please note we currently have a five month processing delay.
We are working on May card/paper applications and completing credit card charges for July Logbook applications. We expect these Logbook applications to be
completed in the DXCC and Logbook programs in four to five weeks. Once fully processed, your credits will be moved over in your Logbook account.
Certificates and stickers will be mailed at a later date.
Online DXCC is still unavailable, but progress is being made to restore the system.
You can obtain updates by visiting www.arrl.org under ARRL Systems Service Disruption.
For concerns other than inquiries as to your application processing date or credit cards being charged, please feel free to let me know. Take care.
/
On 2/2/2025 9:28 AM, William WC2L wrote:
LOTW is very far behind!!
Will WC2L
|
On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote: I guess they are behind as show by this from the Website. Horrible. LotW is processing normally and is current. That "clip" shows that you have not successfully uploaded any QSOs since early December. I suggest you go to "Your Account" (top menu) -> "Your Activity" (left menu) and check the Activity and results of each upload for errors and correct any you find. 73, ... Joe, W4TV On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote: This listing shows the number of QSOs you have uploaded and the number of matches (QSLs) each of your call signs. It also shows the oldest and newest QSO date for each call sign.
*Call Sign*
*# QSOs*
*# QSLs*
*Oldest*
*Newest*
W0MN
10,229
4,455
1953-12-27 18:30:00
2024-12-04 19:59:56
W0RYM
1,105
3
1953-12-27 18:30:00
1978-11-05 02:20:00
AC0RYM
41
0
1976-01-01 17:56:00
1976-11-11 14:35:00
I guess they are behind as show by this from the Website. Horrible.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
|
Gil,
it means that you have not made any q's and uploaded them since dec
4th
which from what you stated agrees with dxkeeper.
so how is it you think lotw is behind?
Mine shows 2025-01-31 which is the last time I made and uploaded
something. it's working fine.
73
Bob
On 2/2/2025 8:26 AM, Gilbert Baron W0MN
via groups.io wrote:
This listing
shows the number of QSOs you have uploaded and the number of
matches (QSLs) each of your call signs. It also shows the
oldest and newest QSO date for each call sign.
|
Call Sign
|
# QSOs
|
# QSLs
|
Oldest
|
Newest
|
|
W0MN
|
10,229
|
4,455
|
1953-12-27
18:30:00
|
2024-12-04
19:59:56
|
|
W0RYM
|
1,105
|
3
|
1953-12-27
18:30:00
|
1978-11-05
02:20:00
|
|
AC0RYM
|
41
|
0
|
1976-01-01
17:56:00
|
1976-11-11
14:35:00
|
?
?
?
I guess they
are behind as show by this from the Website. Horrible.
?
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
?
Not sure if missing something with new sync
methods or if LOTW is just behind. Looking at status the
latest LotW Sent is Y and date of latest QSO (not necessarily
confirmed, some just received and shown as a QSO on a LOTW
Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is shown
as Sent in DXKeeper should have the date sent and date
received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates
QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW really
that far behind?? I suspect I am missing something here with
my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
|
Will,
No it is not!
They may be behind processing awards, but that is a separate
issue.
On 2/2/2025 8:28 AM, William WC2L
wrote:
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron
W0MN via groups.io wrote:
Not sure if missing something with new
sync methods or if LOTW is just behind. Looking at status
the latest LotW Sent is Y and date of latest QSO (not
necessarily confirmed, some just received and shown as a QSO
on a LOTW Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is
shown as Sent in DXKeeper should have the date sent and date
received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates
QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW really
that far behind?? I suspect I am missing something here with
my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
Sorry, misread.. Awards are way
behind. Submitting is up today
FYI, that was a very recent email!!
Will WC2L
On 2/2/2025 10:09 AM, KA9JAC via
groups.io wrote:
Will,
No it is not!
They may be behind processing awards, but that is a separate
issue.
On 2/2/2025 8:28 AM, William WC2L
wrote:
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron
W0MN via groups.io wrote:
Not sure if missing something with new
sync methods or if LOTW is just behind. Looking at status
the latest LotW Sent is Y and date of latest QSO (not
necessarily confirmed, some just received and shown as a
QSO on a LOTW Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is
shown as Sent in DXKeeper should have the date sent and
date received showing in the log page unless L:oTW is up
to date.
?
If I go to ARRL LotW query page the
lates QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW
really that far behind?? I suspect I am missing something
here with my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
I have changed nothing in the way I upload. I use DXKeeper and it has been working fie and QRZ log was updated. Unless there is a change in how to use QSL via DXKeeper and the stats on it that shows the QSOes as R meaning relieved I will wait util I hear more about what is going on.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Joe Subich, W4TV via groups.io Sent: Sunday, February 2, 2025 8:48 AM To: [email protected]Subject: Re: [DXLab] LOTW confirmations On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote: > I guess they are behind as show by this from the Website. Horrible. LotW is processing normally and is current. That "clip" shows that you have not successfully uploaded any QSOs since early December. I suggest you go to "Your Account" (top menu) -> "Your Activity" (left menu) and check the Activity and results of each upload for errors and correct any you find. 73, ... Joe, W4TV On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote: This listing shows the number of QSOs you have uploaded and the number
of matches (QSLs) each of your call signs. It also shows the oldest
and newest QSO date for each call sign.
*Call Sign*
*# QSOs*
*# QSLs*
*Oldest*
*Newest*
W0MN
10,229
4,455
1953-12-27 18:30:00
2024-12-04 19:59:56
W0RYM
1,105
3
1953-12-27 18:30:00
1978-11-05 02:20:00
AC0RYM
41
0
1976-01-01 17:56:00
1976-11-11 14:35:00
I guess they are behind as show by this from the Website. Horrible.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
-- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
|
Well then I have done something wrong with DXKeeper. Why QRZ shows my log but not LoTW is confusing me. I guess I missed seething when the change was made to Upload to all without setting the Queue. Later I will do some reading and see what I? am missing because I ?HAVE CHANGED NOTHIN AND UNTIL Dec 4 it was all working ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of KA9JAC via groups.io
Sent: Sunday, February 2, 2025 9:07 AM
To: [email protected]
Subject: Re: [DXLab] LOTW confirmations? Gil,
it means that you have not made any q's and uploaded them since dec 4th
which from what you stated agrees with dxkeeper.
so how is it you think lotw is behind?
Mine shows 2025-01-31 which is the last time I made and uploaded something. it's working fine.
73
Bob On 2/2/2025 8:26 AM, Gilbert Baron W0MN via groups.io wrote: This listing shows the number of QSOs you have uploaded and the number of matches (QSLs) each of your call signs. It also shows the oldest and newest QSO date for each call sign. Call Sign | # QSOs | # QSLs | Oldest | Newest | W0MN | 10,229 | 4,455 | 1953-12-27 18:30:00 | 2024-12-04 19:59:56 | W0RYM | 1,105 | 3 | 1953-12-27 18:30:00 | 1978-11-05 02:20:00 | AC0RYM | 41 | 0 | 1976-01-01 17:56:00 | 1976-11-11 14:35:00 |
? ? ? I guess they are behind as show by this from the Website. Horrible. ? ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ? ? Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024. ? It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date. ? If I go to ARRL LotW query page the lates QSO shown is Dec 4 That agrees with DXKeeper ? All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4. ? ? Am I missing something or is LoTW really that far behind?? I suspect I am missing something here with my DXKeeper operation. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
--
W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
--
W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
? -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
Are you thinking that the Sync All button does everything, NOT
you still have to upload the q's
On 2/2/2025 9:34 AM, Gilbert Baron W0MN
via groups.io wrote:
toggle quoted message
Show quoted text
Well then I
have done something wrong with DXKeeper. Why QRZ shows my
log but not LoTW is confusing me. I guess I missed seething
when the change was made to Upload to all without setting
the Queue. Later I will do some reading and see what I? am
missing because I ?HAVE CHANGED NOTHIN AND UNTIL Dec 4 it
was all working
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
?
Gil,
it means that you have not made any q's and uploaded them
since dec 4th
which from what you stated agrees with dxkeeper.
so how is it you think lotw is behind?
Mine shows 2025-01-31 which is the last time I made and
uploaded something. it's working fine.
73
Bob
On 2/2/2025 8:26 AM, Gilbert Baron W0MN
via groups.io wrote:
This
listing shows the number of QSOs you have uploaded and the
number of matches (QSLs) each of your call signs. It also
shows the oldest and newest QSO date for each call sign.
|
Call Sign
|
# QSOs
|
# QSLs
|
Oldest
|
Newest
|
|
W0MN
|
10,229
|
4,455
|
1953-12-27
18:30:00
|
2024-12-04
19:59:56
|
|
W0RYM
|
1,105
|
3
|
1953-12-27
18:30:00
|
1978-11-05
02:20:00
|
|
AC0RYM
|
41
|
0
|
1976-01-01
17:56:00
|
1976-11-11
14:35:00
|
?
?
?
I guess
they are behind as show by this from the Website.
Horrible.
?
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
?
Not sure if missing something with new
sync methods or if LOTW is just behind. Looking at status
the latest LotW Sent is Y and date of latest QSO (not
necessarily confirmed, some just received and shown as a QSO
on a LOTW Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is
shown as Sent in DXKeeper should have the date sent and date
received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates
QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for
sent but the Date sent item Shows none after Dec 4.
?
?
Am I missing something or is LoTW really
that far behind?? I suspect I am missing something here with
my DXKeeper operation.
?
Outlook
LT Gil W0MN
Hierro
Candente Batir de Repente
44.08226
N 92.51265 W EN34rb
?
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP
Laptop
|
On 2025-02-02 10:31 AM, Gilbert Baron W0MN via groups.io wrote: Unless there is a change in how to use QSL via DXKeeper and the stats on it that shows the QSOes as R meaning relieved I will wait
util I hear more about what is going on. You are wrong. 'R' means *REQUESTED* ... 'Y' means received. See the legend just to the right of the QSL panel on DXKeeper's Log QSOs tab. If LotW Sent = R, the QSOs are waiting to be uploaded to LotW. If LotW Rcvd = R, you have [attempted] to upload to LotW and have are waiting on a reply (Requested confirmation). LotW Sent = 'U' means you have uploaded to LotW but LotW has not accepted the upload ("sync QSOs") and LotW Sent = 'Y' means the QSOs have been accepted by LotW ("sync QSOs" complete). and QRZ log was updated. QRZ Log means nothing. If you are expecting to use QRZ as an intermediary to LotW it is a waste of time and just one more place to screw things up. 73, ... Joe, W4TV On 2025-02-02 10:31 AM, Gilbert Baron W0MN via groups.io wrote: I have changed nothing in the way I upload. I use DXKeeper and it has been working fie and QRZ log was updated. Unless there is a change in how to use QSL via DXKeeper and the stats on it that shows the QSOes as R meaning relieved I will wait util I hear more about what is going on.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV via groups.io
Sent: Sunday, February 2, 2025 8:48 AM
To: [email protected]
Subject: Re: [DXLab] LOTW confirmations
On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote:
> I guess they are behind as show by this from the Website. Horrible.
LotW is processing normally and is current. That "clip" shows that you have not successfully uploaded any QSOs since early December.
I suggest you go to "Your Account" (top menu) -> "Your Activity"
(left menu) and check the Activity and results of each upload for errors and correct any you find.
73,
... Joe, W4TV
On 2025-02-02 9:26 AM, Gilbert Baron W0MN via groups.io wrote:
This listing shows the number of QSOs you have uploaded and the number
of matches (QSLs) each of your call signs. It also shows the oldest
and newest QSO date for each call sign.
*Call Sign*
*# QSOs*
*# QSLs*
*Oldest*
*Newest*
W0MN
10,229
4,455
1953-12-27 18:30:00
2024-12-04 19:59:56
W0RYM
1,105
3
1953-12-27 18:30:00
1978-11-05 02:20:00
AC0RYM
41
0
1976-01-01 17:56:00
1976-11-11 14:35:00
I guess they are behind as show by this from the Website. Horrible.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
|
On 2025-02-02 10:17 AM, William WC2L wrote: Sorry, misread.. Awards are way behind. Submitting is up today
FYI, that was a very recent email!! Can't be that recent, Online DXCC returned to online in late November and the January 14 update posted on both ARRL News and the LotW homepage indicated they were processing applications submitted in December not *MAY*. 73, ... Joe, W4TV On 2025-02-02 10:17 AM, William WC2L wrote: Sorry, misread.. Awards are way behind. Submitting is up today
FYI, that was a very recent email!!
Will WC2L
On 2/2/2025 10:09 AM, KA9JAC via groups.io wrote:
Will,
*No it is not!
*They may be behind processing awards, but that is a separate issue.*
*
On 2/2/2025 8:28 AM, William WC2L wrote:
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron W0MN via groups.io wrote:
Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024.
It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date.
If I go to ARRL LotW query page the lates QSO shown is Dec 4
That agrees with DXKeeper
All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4.
Am I missing something or is LoTW really that far behind?? I suspect I am missing something here with my DXKeeper operation.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
--
William Liporace WC2L
or
AR-Cluster Node? telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
I just asked for an update. They
email is about 45 days!
If they are in December, I should be processed shortly.
Will WC2L
On 2/2/2025 11:42 AM, Joe Subich, W4TV
wrote:
On
2025-02-02 10:17 AM, William WC2L wrote:
> Sorry, misread.. Awards are way behind. Submitting is up
today
> FYI, that was a very recent email!!
Can't be that recent, Online DXCC returned to online in late
November and the January 14 update posted on both ARRL News and
the
LotW homepage indicated they were processing applications
submitted
in December not *MAY*.
73,
?? ... Joe, W4TV
On 2025-02-02 10:17 AM, William WC2L wrote:
Sorry, misread.. Awards are way behind.
Submitting is up today
FYI, that was a very recent email!!
Will WC2L
On 2/2/2025 10:09 AM, KA9JAC via groups.io wrote:
Will,
*No it is not!
*They may be behind processing awards, but that is a separate
issue.*
*
On 2/2/2025 8:28 AM, William WC2L wrote:
LOTW is very far behind!!
Will WC2L
On 2/2/2025 7:53 AM, Gilbert Baron W0MN via groups.io wrote:
Not sure if missing something with new sync methods or if
LOTW is just behind. Looking at status the latest LotW
Sent is Y and date of latest QSO (not necessarily
confirmed, some just received and shown as a QSO on a LOTW
Query is WAY BACK at Dec 4 2024.
It seems that a QSO that old that is shown as Sent in
DXKeeper should have the date sent and date received
showing in the log page unless L:oTW is up to date.
If I go to ARRL LotW query page the lates QSO shown is Dec
4
That agrees with DXKeeper
All QSOes sent from DXKeeper show R for sent but the Date
sent item Shows none after Dec 4.
Am I missing something or is LoTW really that far behind??
I suspect I am missing something here with my DXKeeper
operation.
Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb
--?
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
--?
William Liporace WC2L
orhttps://dxc.wc2l.com
AR-Cluster Node? telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
--
William Liporace WC2L
or
AR-Cluster Node telnet dxc.wc2l.com 7373 or 144.93 MHz
wc2l@...
|
+ AA6YQ comments below
Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024.
?
It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date.
?
If I go to ARRL LotW query page the lates QSO shown is Dec 4
That agrees with DXKeeper
?
All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4.
+ The "new sync method", by which I assume you mean the "Sync All" function, simply automates the invocation of previously existing upload (Club Log, QRZ) and sync (eQSL, LoTW, Club Log, QRZ) functions. There has been no change to the functionality of any of these operations. + Note that "Sync All" does not upload QSOs to LoTW (or eQSL); it is still necessary to direct DXKeeper to upload your QSOs to LoTW. There are two ways to do this: 1. On the Main window's QSL tab with the "QSL Via" panel set to LoTW, click the "Add Requested" button and then click the "Upload to LoTW" button + or 2a. On the "QSL Configuration" window's LoTW tab, check the "Upload each QSO logged via the Capture window..." box + and 2b. If you have WSJT-X directly interoperating with DXLab, check the LoTW box in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window + and 2c. If you are using JTAlert, configure it to direct DXKeeper to upload QSOs logged to LoTW + and 2d. If you are using the N1MM-DXKeeper Gateway, configure it to upload QSOs logged to LOTW + A QSO's "LoTW Sent" item, visible in the "Online QSL" panel on the "Log QSOs" tab of DXKeeper's Main window, reveals its status: blank - not uploaded to LoTW R - requested to be uploaded to LoTW, but not yet uploaded U - uploaded to LoTW, but not reported by LoTW as "accepted" Y - uploaded to LoTW and reported by LoTW as "accepted"; the date of acceptance is shown in the QSOs' "LoTW date sent" item in the "Online QSL" panel on the "Log QSOs" tab of DXKeeper's Main window ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ
|
MEA culpa. Sorry for the unneeded post. First is I did not do the create of the QSL que. I somehow thought the new code did all that for you. I was wrong. Second, when I did finally do that, I found that somehow I had the wrong pathway to TQSL. I fixed all of that and now all has worked as expected. ? All seems well now. I have Workspaces for SSB, CW, and FT8 and it is easy to fix one and mot the other. I should be more careful. ? ? ? ? ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ via groups.io
Sent: Sunday, February 2, 2025 13:07
To: [email protected]
Subject: Re: [DXLab] LOTW confirmations? Not sure if missing something with new sync methods or if LOTW is just behind. Looking at status the latest LotW Sent is Y and date of latest QSO (not necessarily confirmed, some just received and shown as a QSO on a LOTW Query is WAY BACK at Dec 4 2024. ? It seems that a QSO that old that is shown as Sent in DXKeeper should have the date sent and date received showing in the log page unless L:oTW is up to date. ? If I go to ARRL LotW query page the lates QSO shown is Dec 4 That agrees with DXKeeper ? All QSOes sent from DXKeeper show R for sent but the Date sent item Shows none after Dec 4.
+ The "new sync method", by which I assume you mean the "Sync All" function, simply automates the invocation of previously existing upload (Club Log, QRZ) and sync (eQSL, LoTW, Club Log, QRZ) functions. There has been no change to the functionality of any of these operations.
+ Note that "Sync All" does not upload QSOs to LoTW (or eQSL); it is still necessary to direct DXKeeper to upload your QSOs to LoTW. There are two ways to do this:
1. On the Main window's QSL tab with the "QSL Via" panel set to LoTW, click the "Add Requested" button and then click the "Upload to LoTW" button
+ or
2a. On the "QSL Configuration" window's LoTW tab, check the "Upload each QSO logged via the Capture window..." box
+ and
2b. If you have WSJT-X directly interoperating with DXLab, check the LoTW box in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window
+ and
2c. If you are using JTAlert, configure it to direct DXKeeper to upload QSOs logged to LoTW
+ and
2d. If you are using the N1MM-DXKeeper Gateway, configure it to upload QSOs logged to LOTW
+ A QSO's "LoTW Sent" item, visible in the "Online QSL" panel on the "Log QSOs" tab of DXKeeper's Main window, reveals its status:
blank - not uploaded to LoTW
R - requested to be uploaded to LoTW, but not yet uploaded
U - uploaded to LoTW, but not reported by LoTW as "accepted"
Y - uploaded to LoTW and reported by LoTW as "accepted"; the date of acceptance is shown in the QSOs' "LoTW date sent" item in the "Online QSL" panel on the "Log QSOs" tab of DXKeeper's Main window
? ? ? 73,
? ? ? ? ? ? ?Dave, AA6YQ -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
Gilbert Baron W0MN
William WC2L