Re: Installing DXLab on Win11 machine
Print the instructions in the Moving between PCs link below.
Then check off the steps as you perform them.?
You may get distracted during the process and accidently skip a step.?
?
72,
Dave, w6de
?
toggle quoted message
Show quoted text
From: DXLab@groups.io
<DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io
Sent: 29 January, 2025 19:51
To: DXLab@groups.io
Subject: Re: [DXLab] Installing DXLab on Win11 machine
?
I am preparing to purchase a new Win11 machine. I have run DXLabs software for years. The primary Items I wish to transfer is my DX Keeper (log) data base and back ups files. From what I am reading I will make a copy of both databases to
a thumb drive. My next step is to download the launcher and start the application and copy the data bases into the C drive in the DXKeeper data bases folder and then run the application.
I have read and reread the moving between PCs. I am really just trying to get a feel for what I am about to do and REALLY do not want to screw this up. Initially I had hoped that I could use Workspaces to populate commander but that appears
not to be the case. This looks like a long and intense process, or am I just confused?
+ Ops who carefully follow the
step-by-step instructions in
+ report that it takes about 20 minutes.
+ re "Initially I had hoped that I could use Workspaces to populate commander but that appears not to be the case" - what leads you to that conclusion?
? ? ? ?73,
? ? ? ? ? ? Dave AA6YQ
|
Re: DXKeeper comment field
+ AA6YQ comments below
When I log an FT8 contact, I'm getting the DXKeeper comment field automatically filled with the word POTA even though I have not selected it in WSJT-X.?? I have searched in WSJT-x for the word POTA and didn't find it.? I even deleted the comments.txt file. The word POTA still shows up on each FT8 entry I make.
Where is DXKeeper getting this information to fill in the comments field?
+ From the application that sent DXKeeper a "QSO Record" with instructions to add it to your log. ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ ? ? ? ?
|
Re: FT8 row in the DXCC Summary (RAT)
+ AA6YQ comments below
I apologize if this question has already been asked but I did not find the answer I was looking for.
Using the RAT function (DXCC tab) an FT8 line is present among all others.
In my case it shows:
Worked: 262
Confirmed: 249
Verified: 26
?
The DIGI row shows:
Worked: 310
Confirmed: 308
Verified: 305
?
From what I know ARRL does not issue a separate certificate for the FT8 as the mode is included in the digital group (RTTY, PSK, etc).
I wonder how DXKeeper manage this data (and updates the RAT)and in particular the "verified" field.
+ QSOs in digital modes like FT8 "count" towards "DXCC Digital awards"; DXLab's award tracking functions fully support this. + When Peter G3PLX introduced PSK31 back in 2001, I added a PSK31 checkbox to the "DXCC Bands & Modes" panel on the Awards tab of DXKeeper's Configuration window - even though there was (and still isn't ) a PSK31-specific DXCC award. I wanted to encourage the use of PSK31 by DXers; the PSK31 checkbox made it easy to pursue the objective of confirming all DXCC entities in PSK31. + Later, I added a Selector so that users could choose any single digital mode (except RTTY) with which to pursue all DXCC entities, not just PSK31. I'm at 300 in FT8. ? ? ? ? 73, ? ? ? ? ? ? ? ?Dave, AA6YQ
|
+ 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
|
Re: DXKeeper comment field
In the WSJTX-devel "Log QSOs" dialog, look at the "Comments" box and
clear it. Also clear the "Retain" check box at the right end of the
Comments line.
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-02-02 1:17 PM, E. Glenn Wolf Jr. via groups.io wrote: No, just straight wsjt-x version 2.7.1-devel 250106-rc8 improved plus
On 2/2/2025 11:58, Bruce - K5WBM via groups.io wrote:
Are you using JTAlert?? If so, could POTA be in the JTAlert comment field and get sent to DXKeeper?
Bruce - K5WBM
On Feb 2, 2025, at 10:40?AM, E. Glenn Wolf Jr. via groups.io <glenn@...> wrote:
?Good day!
When I log an FT8 contact, I'm getting the DXKeeper comment field automatically filled with the word POTA even though I have not selected it in WSJT-X.?? I have searched in WSJT-x for the word POTA and didn't find it.? I even deleted the comments.txt file. The word POTA still shows up on each FT8 entry I make.
Where is DXKeeper getting this information to fill in the comments field?
--
Glenn
N5RN
White Hall, AR
|
Re: FT8 row in the DXCC Summary (RAT)
On 2025-02-02 12:43 PM, Franco IZ4MJP via groups.io wrote: The choice of FT8 is specified in Config -> Awards -> DXCC Bands & Modes -> User Specified digital mode family I wonder how DXKeeper manage this data (and updates the RAT)and in particular the "verified" field. DXKeeper updates that data as it does all other modes in the "Recompute" process. Verified indicates that that entity-mode has been accepted for credit by ARRL. In the case of FT8 (or any other digital mode family) that QSO/QSL would have been used for "Digital" credit. Unfortunately, RTTY is the only digital mode that can not be selected as the "User Specified Digital Mode Family". 73, ... Joe, W4TV On 2025-02-02 12:43 PM, Franco IZ4MJP via groups.io wrote: I apologize if this question has already been asked but I did not find the answer I was looking for.
Using the RAT function (DXCC tab) an FT8 line is present among all others.
In my case it shows:
Worked: 262
Confirmed: 249
Verified: 26
The DIGI row shows:
Worked: 310
Confirmed: 308
Verified: 305
From what I know ARRL does not issue a separate certificate for the FT8 as the mode is included in the digital group (RTTY, PSK, etc).
I wonder how DXKeeper manage this data (and updates the RAT)and in particular the "verified" field.
Thanks for the answer.
Best 73 IZ4MJP Franco
|
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@...
|
Re: DXKeeper comment field
No, just straight wsjt-x version 2.7.1-devel 250106-rc8 improved plus
toggle quoted message
Show quoted text
On 2/2/2025 11:58, Bruce - K5WBM via groups.io wrote: Are you using JTAlert? If so, could POTA be in the JTAlert comment field and get sent to DXKeeper?
Bruce - K5WBM
On Feb 2, 2025, at 10:40?AM, E. Glenn Wolf Jr. via groups.io <glenn@...> wrote:
?Good day!
When I log an FT8 contact, I'm getting the DXKeeper comment field automatically filled with the word POTA even though I have not selected it in WSJT-X. I have searched in WSJT-x for the word POTA and didn't find it. I even deleted the comments.txt file. The word POTA still shows up on each FT8 entry I make.
Where is DXKeeper getting this information to fill in the comments field?
--
Glenn
N5RN
White Hall, AR
--
Glenn
N5RN
White Hall, AR
|
Reasonable call prefilter
SpotCollector's?prefiltering feature is very helpful.?
One thing that I would appreciate is an additional filter, blocking the spots of? clearly unreasonable callsigns produced by digital mode skimmers.
Recently I have seen calls like 5WGYH86QK6J, EZZE3K8A3LL, and now a few? minutes ago, STZJ4GCNWEE spotted on digital modes. When the last one? appeared I got an alert since I have yet to work Sudan on 40m.
There are some quite strange special event callsigns, such as OU0POLIO and DL2025B,? so the filter cannot be too strict but it would be helpful if the most obvious could be blocked. As a user option, of course.
Some ideas for rules would be?
Base callsigns (with any prefix or suffix stripped) starting with a letter having more than one group of digits Base callsigns starting with a digit that is followed by more than two letters or having more than two groups of digits? Base callsigns having more than two letters before the first digit
Bj?rn SM7IUN
|
Re: DXKeeper comment field
Are you using JTAlert? If so, could POTA be in the JTAlert comment field and get sent to DXKeeper?
Bruce - K5WBM
toggle quoted message
Show quoted text
On Feb 2, 2025, at 10:40?AM, E. Glenn Wolf Jr. via groups.io <glenn@...> wrote:
?Good day!
When I log an FT8 contact, I'm getting the DXKeeper comment field automatically filled with the word POTA even though I have not selected it in WSJT-X. I have searched in WSJT-x for the word POTA and didn't find it. I even deleted the comments.txt file. The word POTA still shows up on each FT8 entry I make.
Where is DXKeeper getting this information to fill in the comments field?
--
Glenn
N5RN
White Hall, AR
|
FT8 row in the DXCC Summary (RAT)
I apologize if this question has already been asked but I did not find the answer I was looking for.
Using the RAT function (DXCC tab) an FT8 line is present among all others.
In my case it shows:
Worked: 262
Confirmed: 249
Verified: 26
?
The DIGI row shows:
Worked: 310
Confirmed: 308
Verified: 305
?
From what I know ARRL does not issue a separate certificate for the FT8 as the mode is included in the digital group (RTTY, PSK, etc).
I wonder how DXKeeper manage this data (and updates the RAT)and in particular the "verified" field.
?
Thanks for the answer.
?
Best 73 IZ4MJP Franco
|
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@...
|
Good day!
When I log an FT8 contact, I'm getting the DXKeeper comment field automatically filled with the word POTA even though I have not selected it in WSJT-X.?? I have searched in WSJT-x for the word POTA and didn't find it.? I even deleted the comments.txt file. The word POTA still shows up on each FT8 entry I make.
Where is DXKeeper getting this information to fill in the comments field?
--
Glenn
N5RN
White Hall, AR
|
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: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV via groups.io
Sent: Sunday, February 2, 2025 8:48 AM
To: DXLab@groups.io
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
|
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
|
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: DXLab@groups.io <DXLab@groups.io> On Behalf Of KA9JAC via groups.io
Sent: Sunday, February 2, 2025 9:07 AM
To: DXLab@groups.io
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
|
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: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV via groups.io Sent: Sunday, February 2, 2025 8:48 AM To: DXLab@groups.io 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
|
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@...
|
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@...
|
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
|
William WC2L
Bj?rn SM7IUN
Gilbert Baron W0MN