Upload QSO to Club Log timed out

For the past day or so I have been seeing this message when logging via the Capture window.??

"Upload QSO to Club Log timed out"

My Clublog account works, I can log in to their website and see my data.

If I right-click from the log QSO's tab and choose upload to ClubLog I get the same error message.

If I wait for the upload to time out I can go to the QSL Tab, select ClubLog and click the Upload to ClubLog button and get the message "succeeded: 23 QSOs uploaded."

So, DXKeeper seems to be communicating with ClubLog for bulk uploads via the QSL tab but not via the Capture window on Log QSO's tab for single uploads.

No error log in menu bar.

73 de Chuck, WS1L

chandlerusm@...

Upload QSO to Club Log timed out

#229366

Hello,

?

a couple of days ago I noticed uploading to Club Log timed out.? This started with QSO's from 5/25/2025.? I am using DXKeeper latest version 18.1.4.

?

Below is information from the error log when attempted to upload a QSO to club log.? Any thoughts? LOTW auto upload is working as expected

?

thanks? K4JKB

?

2025-05-26 10:26:35.817 > ClubLogModule.SendQSO: begin
2025-05-26 10:26:35.823 > ClubLogModule.SendQSO: initiating upload to https://clublog.org/realtime.php
2025-05-26 10:26:35.830 > ? ?Params = False
2025-05-26 10:26:35.837 > ClubLogModule.SendQSO: upload initiated
2025-05-26 10:26:35.845 > ClubLogModule.HandleInetStateChange, theState = 3(Connecting), OperationCompleted = False
2025-05-26 10:26:35.851 > ClubLogModule.HandleInetStateChange: connecting to Club Log host
2025-05-26 10:26:35.916 > ClubLogModule.HandleInetStateChange, theState = 4(Connected), OperationCompleted = False
2025-05-26 10:26:35.924 > ClubLogModule.HandleInetStateChange: connected to Club Log host
2025-05-26 10:26:36.003 > ClubLogModule.HandleInetStateChange, theState = 5(Requesting), OperationCompleted = False
2025-05-26 10:26:36.013 > ClubLogModule.HandleInetStateChange: sending request to Club Log
2025-05-26 10:26:36.020 > ClubLogModule.HandleInetStateChange, theState = 6(Request Sent), OperationCompleted = False
2025-05-26 10:26:36.026 > ClubLogModule.HandleInetStateChange: successfully sent request to Club Log
2025-05-26 10:26:36.034 > ClubLogModule.HandleInetStateChange, theState = 7(Receiving Response), OperationCompleted = False
2025-05-26 10:26:36.041 > ClubLogModule.HandleInetStateChange: receiving response from Club Log
2025-05-26 10:26:36.088 > ClubLogModule.HandleInetStateChange, theState = 8(Response Received), OperationCompleted = False
2025-05-26 10:26:36.096 > ClubLogModule.HandleInetStateChange icResponseReceived: still executing
2025-05-26 10:26:36.103 > ClubLogModule.HandleInetStateChange: received response from Club Log
2025-05-26 10:26:36.111 > ClubLogModule.HandleInetStateChange, theState = 12(Response Completed), OperationCompleted = False
2025-05-26 10:26:36.118 > ClubLogModule.HandleInetStateChange: response completed?
2025-05-26 10:26:36.495 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 8, ColIndex = 0, DXLogSetup.TooltipsCheckbox.Value = 1
2025-05-26 10:26:36.504 > ? ?theColName = BAND
2025-05-26 10:26:36.510 > ? ?Callsign = KC3OL, CellContents = 20M
2025-05-26 10:26:36.516 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip
2025-05-26 10:26:36.855 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 8, ColIndex = 0, DXLogSetup.TooltipsCheckbox.Value = 1
2025-05-26 10:26:36.863 > ? ?theColName = BAND
2025-05-26 10:26:36.871 > ? ?Callsign = KC3OL, CellContents = 20M
2025-05-26 10:26:36.877 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip
2025-05-26 10:26:38.445 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 8, ColIndex = 0, DXLogSetup.TooltipsCheckbox.Value = 1
2025-05-26 10:26:38.455 > ? ?theColName = BAND
2025-05-26 10:26:38.461 > ? ?Callsign = KC3OL, CellContents = 20M
2025-05-26 10:26:38.467 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip
2025-05-26 10:26:39.261 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 2, ColIndex = 19, DXLogSetup.TooltipsCheckbox.Value = 1
2025-05-26 10:26:39.269 > ? ?theColName = QSO_BEGIN
2025-05-26 10:26:39.277 > ? ?Callsign = CO8ZZ, CellContents = 5/23/2025 ? 01:11
2025-05-26 10:26:39.283 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip
2025-05-26 10:27:36.099 > ClubLogModule.DownloadTimedOut
2025-05-26 10:27:36.110 > ClubLogModule.SendQSO: upload aborted after 4connection retries
2025-05-26 10:27:36.118 > Message.DisplayMessage: Title: DXKeeper Club Log Upload, Message = Upload QSO to Club Log timed out
2025-05-26 10:27:36.144 > DXLogMain.popClubLogUpload_Click: complete
2025-05-26 10:27:36.154 > DXLogMain.LogGrid_Click, ClickCallsign = KF8CGR, ClickAbsolute = 63987
2025-05-26 10:27:36.161 > DXLogMain.LogGrid_Click: complete
2025-05-26 10:27:36.396 > DXLogMain.RowChangeLookupTimer_Timer
2025-05-26 10:27:36.405 > DXLogModule.UpdateFieldVisibility, DXCCID = 291
2025-05-26 10:27:36.413 > DXLogModule.UpdateFieldVisibility: unneeded
2025-05-26 10:27:36.421 > DXLogMain.ValidFields: KF8CGR
2025-05-26 10:27:36.429 > DXLogMain.ValidFields: complete
2025-05-26 10:27:36.437 > DXLogModule.UpdateProgressDisplays
2025-05-26 10:27:36.445 > DXLogModule.UpdateDetailGrid
2025-05-26 10:27:36.453 > DXLogModule.UpdateDetailGrid: K
2025-05-26 10:27:36.461 > StatusString.UpdateGrid
2025-05-26 10:27:36.468 > StatusString.UpdateGrid complete
2025-05-26 10:27:36.475 > DXLogModule.UpdateDetailGrid: complete
2025-05-26 10:27:36.483 > WAZModule.UpdateWAZDetailGrid
2025-05-26 10:27:36.490 > WAZModule.UpdateWAZDetailGrid: CQ Zone 4
2025-05-26 10:27:36.498 > WAZModule.UpdateWAZDetailGrid: complete
2025-05-26 10:27:36.506 > DXLogMain.RowChangeLookup (not suppressed) KF8CGR
2025-05-26 10:27:36.513 > DDEClientModule.PrefixLookup, theCallsign = KF8CGR, theDXCCPrefix = K
2025-05-26 10:27:36.519 > DDEClientModule.PrefixLookup via DXView PrefixLookupCommand
2025-05-26 10:27:36.546 > DDEClientModule.PrefixLookup, LotW = Y, eQSL = N
2025-05-26 10:27:36.554 > DDEClientModule.UpdateLatLon: 43 30' N, 85 0' W
2025-05-26 10:27:36.562 > DXLogMain.RowChangeLookupTimer_Timer: enabling CallbookCmd
2025-05-26 10:27:36.569 > DXLogMain.RowChangeLookupTimer_Timer: complete

Re: TQSL

#229365

Hi Rick

?

Many thanks for this.

The path was wrong. Corected and now all seems ok.

?

Thanks again,

Roger

EI8KN.

?

Re: support for new radio

#229364

+ AA6YQ comments below

Might I suggest that one of you give Yaesu a call or send an email. The couple of times I've had issues with my FT-891 they've always been helpful on the phone 

+ Based on my experience with Yaesu over the past 24 years, I'll pass on that suggestion. When a CAT instruction set manual is publically available, I'll review it.

        73,

                 Dave, AA6YQ

Re: support for new radio

#229363

Might I suggest that one of you give Yaesu a call or send an email. The couple of times I've had issues with my FT-891 they've always been helpful on the phone?

?

--

John P.
WA2FZW

Re: support for new radio

#229362

+ AA6YQ comments below

English manual for the Yaesu FTX-! Series available here:??

+ Thanks, but I looked downloaded that manual from the Yaesu web page yesterday: it doesn't include documentation of the radio's CAT instruction set.

? ? ? 73,

? ? ? ? ? ?Dave, AA6YQ

Re: support for new radio

#229361

English manual for the Yaesu FTX-! Series available here:??

I just downloaded a copy for grins.? I'll keep my Elecraft radios....

Rich, NU6T

Show quoted text

On Sun, May 25, 2025 at 4:59?PM Richard Hill via <nu6t.rich=[email protected]> wrote:

Others have reportedly downloaded a pdf but it is currently unavailable:

NU6T, Rich

Richard Hill

On Sat, May 24, 2025, 2:12?PM Joe Subich, W4TV via <lists=[email protected]> wrote:

> + From what URL can I download documentation for this radio's CAT
?> instruction set?

There is no CAT instruction set info in any of the documentation at:
<>

73,

? ? ... Joe, W4TV

On 2025-05-24 4:34 PM, Dave AA6YQ wrote:
> + AA6YQ comments below
>
>>
>> We are pleased to introduce the new FTX-1F and FTX-1Optima"
>>
>>
>> "FTX-1Field is a Portable 6W or 10W* HF/50MHz/VHF/UHF Multimode
>> Transceiver.?(*10w with 13.8VDC supply.)"
>>
>>
>>
>> "FTX-1Optima is the FTX-1Field with a 100W on HF/6m & 50W on VHF/UHF
>> clip-on Linear Amplifier with built in ATU for HF/6M."
>>
>>
>
> + From what URL can I download documentation for this radio's CAT instruction set?
>
> 73,
>
> Dave, AA6YQ
>

--

Richard Hill

Re: support for new radio

#229360

Others have reportedly downloaded a pdf but it is currently unavailable:

NU6T, Rich

Richard Hill

Show quoted text

On Sat, May 24, 2025, 2:12?PM Joe Subich, W4TV via <lists=[email protected]> wrote:

> + From what URL can I download documentation for this radio's CAT
?> instruction set?

There is no CAT instruction set info in any of the documentation at:
<>

73,

? ? ... Joe, W4TV

On 2025-05-24 4:34 PM, Dave AA6YQ wrote:
> + AA6YQ comments below
>
>>
>> We are pleased to introduce the new FTX-1F and FTX-1Optima"
>>
>>
>> "FTX-1Field is a Portable 6W or 10W* HF/50MHz/VHF/UHF Multimode
>> Transceiver.?(*10w with 13.8VDC supply.)"
>>
>>
>>
>> "FTX-1Optima is the FTX-1Field with a 100W on HF/6m & 50W on VHF/UHF
>> clip-on Linear Amplifier with built in ATU for HF/6M."
>>
>>
>
> + From what URL can I download documentation for this radio's CAT instruction set?
>
> 73,
>
> Dave, AA6YQ
>

Re: TQSL on a new build isn't uploading

#229359

+ AA6YQ comments below
From: [email protected] [mailto:[email protected]] On Behalf Of Greg Engle
Sent: Sunday, May 25, 2025 4:40 PM
To: [email protected]
Subject: Re: [DXLab] TQSL on a new build isn't uploading

In the actual QSO the myQTH is Bakersfield

In the myQTH Tab it’s Bakersfield

In the QSO tab it’s Bakersfield in the LoTW operation window

In TQSL it’s Bakersfield

+ So that I can see what's going on, please do the following:

1. on the Configuration window's General tab, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper, and wait for it to fully initialize

4. attempt to upload the QSO in question

5. on the Configuration window's General tab, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your DXKeeper folder to an email message, and send that message to me via

aa6yq (at) ambersoft.com

      73,

                Dave, AA6YQ

Re: TQSL on a new build isn't uploading

#229358

开云体育

In the actual QSO the myQTH is Bakersfield

In the myQTH Tab it’s Bakersfield

In the QSO tab it’s Bakersfield in the LoTW operation window

In TQSL it’s Bakersfield

?

I just tried uploading again and got the same message.

?

Greg

NZ6E

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ
Sent: Sunday, May 25, 2025 12:57 PM
To: [email protected]
Subject: Re: [DXLab] TQSL on a new build isn't uploading

?

+ AA6YQ comments below

I'm getting the message:
Disabled QSL Queue entry for JH8ISO on 2025-05-25 at 13:04:38 - station location "Home" specified in QSO's QTHID item "bakersfield" doesn't match station location "Bakersfield" selected on the QSL Configuration window's LotW tab
?
There was report of the same issue on March 14th and I followed those directions.
myQTHs Tab has Bakersfield
QSL Tab LoTW Operation has Bakersfield
TQSL Has Bakersfield
?
What am I missing?
?

+ The error message states that the QSO specifies a QTHID of "bakersfield" - note the lower case b - that specifies an LoTW Station Location of "Home". Have you defined a myQTH whose ID is "bakersfield"? If so, change the LOTW Station Location it specifies to "Bakersfield".

? ? ?73,

? ? ? ? ? ? Dave, AA6YQ

Re: TQSL on a new build isn't uploading

#229357

+ AA6YQ comments below

I'm getting the message:

Disabled QSL Queue entry for JH8ISO on 2025-05-25 at 13:04:38 - station location "Home" specified in QSO's QTHID item "bakersfield" doesn't match station location "Bakersfield" selected on the QSL Configuration window's LotW tab

?

There was report of the same issue on March 14th and I followed those directions.

myQTHs Tab has Bakersfield

QSL Tab LoTW Operation has Bakersfield

TQSL Has Bakersfield

?

What am I missing?

?

+ The error message states that the QSO specifies a QTHID of "bakersfield" - note the lower case b - that specifies an LoTW Station Location of "Home". Have you defined a myQTH whose ID is "bakersfield"? If so, change the LOTW Station Location it specifies to "Bakersfield".

? ? ?73,

? ? ? ? ? ? Dave, AA6YQ

TQSL on a new build isn't uploading

#229356

I'm getting the message:

Disabled QSL Queue entry for JH8ISO on 2025-05-25 at 13:04:38 - station location "Home" specified in QSO's QTHID item "bakersfield" doesn't match station location "Bakersfield" selected on the QSL Configuration window's LotW tab

?

There was report of the same issue on March 14th and I followed those directions.

myQTHs Tab has Bakersfield

QSL Tab LoTW Operation has Bakersfield

TQSL Has Bakersfield

?

What am I missing?

?

This was a new build and new TQSL certs because I totally lost a drive with no backup other than my logbook on a different drive.

?

Greg

NZ6E

Re: TQSL

#229355

In DXKeeper, check the "Config" button. Then "QSL Config" on the lower left corner.

In the "DXKeeper QSL Configuration" window, select the "LoTW" tab.

What is the "TQSL" area labeled? (Mine says "TQSL 2.8.1")?

What is the "TQSL exe pathname" set to?? (It should always be "C:\Program Files (x86)\TrustedQSL\tqsl.exe".)

What you're seeing is the result of having TQSL installed in more than one directory. If you install TQSL into somewhere other than the default, it's up to you to always install to that folder.

Install TQSL into the "Program Files(x86)" directory and remove any other copies of tqsl.exe.

73,

? ? -Rick

On Sun, May 25, 2025 at 4:07?AM Roger Greengrass via <roger.greengrass=[email protected]> wrote:

Show quoted text

Every time DXLab Suite starts, I get the message "A new TQSL (V2.8.1) is available".

I am already running that version.

?

Any suggstions as to how to address this?

?

Thanks,

Roger

EI8KN.

?

--

Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA

TQSL

#229354

Every time DXLab Suite starts, I get the message "A new TQSL (V2.8.1) is available".

I am already running that version.

?

Any suggstions as to how to address this?

?

Thanks,

Roger

EI8KN.

?

Re: "Bouncing" Filters Group in DX Commander

#229353

Will do, thanks!

Re: support for new radio

#229352

+ From what URL can I download documentation for this radio's CAT instruction set?There is no CAT instruction set info in any of the documentation at:
<> 

73,

   ... Joe, W4TV

On 2025-05-24 4:34 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

We are pleased to introduce the new FTX-1F and FTX-1Optima"

"FTX-1Field is a Portable 6W or 10W* HF/50MHz/VHF/UHF Multimode
Transceiver.?(*10w with 13.8VDC supply.)"

"FTX-1Optima is the FTX-1Field with a 100W on HF/6m & 50W on VHF/UHF
clip-on Linear Amplifier with built in ATU for HF/6M."

+ From what URL can I download documentation for this radio's CAT instruction set?
73,
Dave, AA6YQ

Re: support for new radio

#229351

+ AA6YQ comments below

We are pleased to introduce the new FTX-1F and FTX-1Optima"

"FTX-1Field is a Portable 6W or 10W* HF/50MHz/VHF/UHF Multimode Transceiver.?(*10w with 13.8VDC supply.)"

"FTX-1Optima is the FTX-1Field with a 100W on HF/6m & 50W on VHF/UHF clip-on Linear Amplifier with built in ATU for HF/6M."

+ From what URL can I download documentation for this radio's CAT instruction set?

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ

Re: support for new radio

#229350

The referenced yaesu link shows:

"We are pleased to introduce the new FTX-1F and FTX-1Optima"

"FTX-1Field is a Portable 6W or 10W* HF/50MHz/VHF/UHF Multimode Transceiver.?(*10w with 13.8VDC supply.)"

"FTX-1Optima is the FTX-1Field with a 100W on HF/6m & 50W on VHF/UHF clip-on Linear Amplifier with built in ATU for HF/6M."

Grin, good power for a reciever!

NU6T, Rich

Richard Hill

Show quoted text

On Sat, May 24, 2025, 12:35?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:

+ AA6YQ comments below

will dxlab support the new ftx-1?

+ I can't find any information about the FTX-1 on Yaesu's web site:

+ My understanding is that FTX-1 is a receiver that covers 30kHz through 174MHz and from 400MHz through 470MHz including SWL, FM
broadcast, and Air-band.

+ Since it has no ability to transmit, the answer to your question is "no", unless its CAT documentation - when available - shows
that it's CAT instruction set is a proper subset of that of a supported Yaesu transceiver.

? ? ? ? 73,

? ? ? ? ? ? ? ?Dave, AA6YQ

Re: support for new radio

#229349

+ AA6YQ comments below

will dxlab support the new ftx-1?

+ I can't find any information about the FTX-1 on Yaesu's web site:

+ My understanding is that FTX-1 is a receiver that covers 30kHz through 174MHz and from 400MHz through 470MHz including SWL, FM
broadcast, and Air-band.

+ Since it has no ability to transmit, the answer to your question is "no", unless its CAT documentation - when available - shows
that it's CAT instruction set is a proper subset of that of a supported Yaesu transceiver.

        73,

               Dave, AA6YQ

Re: "Bouncing" Filters Group in DX Commander

#229348

+ AA6YQ comments below

My transceiver is an IC7300.  I am on FT8 with WSJT.  A CW DX spot comes out, and I double-click in spot collector.  Commander changes to the correct frequency, mode, and filter bandwidth.  (It seem sometimes I have to stop monitoring on WSJT, and sometimes not, or it will grab me back to the FT8 frequency, but that's not what this is about).  When I return to FT8 by re-enabling the monitor in WSJT, I see that the bandwidth is 2.7 kHz.  Before that, it was 3+ kHz on the waterfall.  I then change the Filters Group setting back to Normal (or Wide), and the bandwith goes back to the 3+ kHz.  But now, the Group bandwidth display periodic bounces from normal to narrow, about 1 to 2 times per second.  I can change the filter to wide, same bouncing.  I can change it to narrow (where it was on CW immediately prior to coming back to FT8), and there is no bounce.  There is some kind of polling going on and the state it keeps trying is Narrow. I don't hear any bandwidth changes on the radio while this is going on, and I don't see any change in the WSJT spectrum.

+ So that I can see what's going on, please do the following:

1. on the Configuration window's General tab, check the "Log debugging info" box

2. terminate Commander

3. start Commander

4. replicate the misbehavior you describe above

5. on the Configuration window's General tab, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your Commander folder to an email message, and send that message to me via

aa6yq (at) ambersoft.com

     73,

             Dave, AA6YQ