Can I utilize User Defined Controls in Commander to control an SPE amplifier driven by a Flex 3000?

#229376

Can I utilize User Defined Controls in Commander to control an SPE amplifier driven by a Flex 3000 run by PowerSDR software? The SPE amp is on COM17.

I want to be able to change from Antenna 1 to Antenna 2 on the SPE amplifier. I already have a Kenwood receiver tracking with the main radio as the Secondary. Also, in a Multi radio setting I have a yaesu FTDX101D set as radio #2.

?

The SPE command set is 0x04????

Re: "15m pse"

#229375

Thanks, Tom.? I'll give that a try.

(I was bogged down in teh command references trying to figure out how comments and info fields compare.)

7 3

Earl / KD5XB

Sent with secure email.

On Monday, May 26th, 2025 at 3:32 PM, TOM-KQ5S via groups.io <kq5stom@...> wrote:

Show quoted text

According to Perplexity:

DXSpider Command to Reject Spots with “pse” in Comments
To reject DX spots containing the word “pse” in the comments (the information section) on a DXSpider node, you use a reject filter targeting the spot’s info field.
The correct command is:

reject/spots info pse

Tom - KQ5S

On May 26, 2025, at 16:21, Earl Needham via groups.io <kd5xb@...> wrote:

On Monday, May 26th, 2025 at 3:02 PM, Joe Subich, W4TV <lists@...> wrote:

It is most effective to filter spots of that ilk directly on
the cluster but the filter commands vary depending on which
of the three major cluster software packages is being used.

Do you already have the command built for DXSpider?

Thanks,
Earl / KD5XB

Sent with Proton Mail secure email.

--
Tom-KQ5S

Re: "15m pse"

#229374

开云体育

According to Perplexity:

DXSpider Command to Reject Spots with “pse” in Comments

To reject DX spots containing the word “pse” in the comments (the information section) on a DXSpider node, you use a reject filter targeting the spot’s info field.

The correct command is:

reject/spots info pse

Tom - KQ5S

Show quoted text

On May 26, 2025, at 16:21, Earl Needham via groups.io <kd5xb@...> wrote:

On Monday, May 26th, 2025 at 3:02 PM, Joe Subich, W4TV <lists@...> wrote:

It is most effective to filter spots of that ilk directly on
the cluster but the filter commands vary depending on which
of the three major cluster software packages is being used.

Do you already have the command built for DXSpider?

Thanks,
Earl / KD5XB

Sent with Proton Mail secure email.

--

Tom-KQ5S

Re: "15m pse"

#229373

On Monday, May 26th, 2025 at 3:02 PM, Joe Subich, W4TV <lists@...> wrote:

It is most effective to filter spots of that ilk directly on
the cluster but the filter commands vary depending on which
of the three major cluster software packages is being used.Do you already have the command built for DXSpider?

Thanks,
Earl / KD5XB

Sent with Proton Mail secure email.

Re: "15m pse"

#229372

It is most effective to filter spots of that ilk directly on
the cluster but the filter commands vary depending on which
of the three major cluster software packages is being used.

However, it can be done in SpotCollector using the SQL filter
capability.  In general one would want to add:

   "and not notes like '*pse*'"

to any other SQL filter in use.  If you are not using an SQL
filter, create a pair like:

<standardfilter> and (not notes like '*pse*')

<standardfilter> and <needfilter> and (not notes like '*pse*')

The first duplicates SpotCollector's normal ('X') filtering with
the added exclusion of the "begging" spots"

The second duplicates SpotCollector's normal "Need" filter with
the added exclusion of the "begging spots"

For maximum effectiveness you will probably need to discontinue
use of IRC or prefilter/discard DXSummit Spots since the DX Summit
feed is full of non-amateur "callsigns" wiht all manner of "junk"
like the "begging spots" (and worse).

Details on SpotCollector filters can be found in
  .../DXLab/SpotCollector/Help/SpotDatabase.htm#Filtering with SQL Expressions

73,

   ... Joe, W4TV

Show quoted text

On 2025-05-26 4:25 PM, Earl Needham via groups.io wrote:
Is there some way of filtering out (from Spot Collector) the so-called spots begging a DX station something like "15m pse"? I really don't need to have this pop up in Spot Collector and try to find him, just to find out it's someone BEGGING the DX to go to 15 meters on a medium most DX stations don't see anyway.
Thanks,
Earl / KD5XB
DM84
e e
Sent with [Proton Mail]() secure email.

"15m pse"

#229371

Is there some way of filtering out (from Spot Collector) the so-called spots begging a DX station something like "15m pse"?? I really don't need to have this pop up in Spot Collector and try to find him, just to find out it's someone BEGGING the DX to go to 15 meters on a medium most DX stations don't see anyway.

Thanks,

Earl / KD5XB

DM84

e e

Sent with secure email.

Re: Upload QSO to Club Log timed out

#229370

It's a transient connection issue.  I've seen it on and off
over the last weekend.

73,

   ... Joe, W4TV

Show quoted text

On 2025-05-26 12:07 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
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.
+ I just tried a single-QSO upload to Clublog here and it worked correctly. Please try again.
73,
Dave, AA6YQ

Re: Upload QSO to Club Log timed out

#229369

+ AA6YQ comments below

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.

+ I just tried a single-QSO upload to Clublog here and it worked correctly. Please try again.

       73,

               Dave, AA6YQ

Re: Upload QSO to Club Log timed out

#229368

I did a complete upload of all qso's to club log, now all is good.? dxkeepper is auto uploading to clublog now

?

Joe- K4JKB

?

Upload QSO to Club Log timed out

#229367

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