Don,
Are you using a filter in Commander -> Config -> BandSpread -> Spot
Filter? If so, which filter and what is in it?
I'd bet you have defined one that specifies Mode='RTTY' ... you will
want to change that to something that better reflects the modes you
are using.
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-03-03 8:08 PM, Don Carlgren via groups.io wrote: Hi Dave,
Currently my bandspread will highlight anything I need on RTTY. I don't
use RTTY anymore and primarily use FT8 as my digital mode. Is there a way
to get the bandspread to only highlight needed countries for digi instead?
That way if I've worked a needed country on FT8 it would no longer be
highlighted if it's spotted as RTTY which frequently happens with spots
that are actually FT8 stations.
Clear as mud? :)
Thanks
73, Don
VA7ZT
<>
Virus-free.www.avg.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
|
+ AA6YQ comments below
Currently my bandspread will highlight anything I need on RTTY. I don't use RTTY anymore and primarily use FT8 as my digital mode. Is there a way to get the bandspread to only highlight needed countries for digi instead? That way if I've worked a needed country on FT8 it would no longer be highlighted if it's spotted as RTTY which frequently happens with spots that are actually FT8 stations.
+ If you only want to remove the callsigns of active stations using RTTY from Commander's Bandspread window, the click the Edit button in the "Spot Filter" sub-panel in the "DX Spots" panel on the Bandspread tab of Commander's Configuration window. In the "Commander User-defined SpotCollector filters" window, define entry whose Caption is
NoRTTY
+ and whose SQL is
Mode <> 'RTTY'
+ Then close the "Commander User-defined SpotCollector filters" window, and set the "Spot Filter sub-panel to "NoRTTY".
+ Note that active stations operating in RTTY will still appear in SpotCollector's Spot Database Display and on DXView's World Map. To remove them too, click the Mode button in the Filter panel at the bottom of SpotCollector's Main window and uncheck the "Mode Filter" window's RTTY box, and uncheck the RTTY box in the "Mode Filter" panel on the "Plot Settings" tab of DXView's Configuration window.
73,
Dave, AA6YQ
|
Re: Macros in Spotcollector
Thanks Joe,
That appears to also work.
Jim - KR9U
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Joe Subich, W4TV Sent: Monday, March 3, 2025 6:02 PM To: [email protected]Subject: Re: [DXLab] Macros in Spotcollector If I create a macro to send this command to the ARCluster node station
in Spot collector, it strips out the 'does not equal' "<>"
and sends instead: set/dx/filter Ctyk> > This also affects many other commands as well. Can this be corrected? Jim, try working from the other direction: Set/DX/Filter NOT CTY=K 73, ... Joe, W4TV On 2025-03-03 5:36 AM, Jim - KR9U via groups.io wrote: Hi Dave,
Many times, especially during contests, I filter spots at the DX Cluster.
One of the commands that ARCluster accepts if you want to only see
non-US spots is the command: set/dx/filter Cty<>k If I create a macro
to send this command to the ARCluster node station in Spot collector, it strips out the 'does not equal' "<>" and sends instead: set/dx/filter Ctyk This also affects many other commands as well. Can this be corrected?
Jim - KR9U
|
Hi Dave,
Currently my bandspread will highlight anything I need on RTTY.? I don't use RTTY anymore and primarily use FT8 as my digital mode.? Is there a way to get the bandspread to only highlight needed countries for digi instead?? That way if I've worked a needed country on FT8 it would no longer be highlighted if it's spotted as RTTY which frequently happens with spots that are actually FT8 stations.
Clear as mud?? :)
Thanks 73, Don
VA7ZT
|
Re: Macros in Spotcollector
If I create a macro to send this command to the ARCluster node station in Spot collector, it strips out the 'does not equal' "<>"
and sends instead: set/dx/filter Ctyk>
This also affects many other commands as well. Can this be corrected? Jim, try working from the other direction: Set/DX/Filter NOT CTY=K 73, ... Joe, W4TV On 2025-03-03 5:36 AM, Jim - KR9U via groups.io wrote: Hi Dave,
Many times, especially during contests, I filter spots at the DX Cluster.
One of the commands that ARCluster accepts if you want to only see non-US spots is the command:? set/dx/filter Cty<>k
If I create a macro to send this command to the ARCluster node station in Spot collector, it strips out the 'does not equal'? "<>" and sends instead:? set/dx/filter Ctyk
This also affects many other commands as well.? Can this be corrected?
Jim - KR9U
|
Re: Macros in Spotcollector
Thanks Dave,
That will certainly help.
Jim - KR9U
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Dave AA6YQ Sent: Monday, March 3, 2025 5:45 PM To: [email protected]Subject: Re: [DXLab] Macros in Spotcollector + AA6YQ comments below Many times, especially during contests, I filter spots at the DX Cluster. One of the commands that ARCluster accepts if you want to only see non-US spots is the command: set/dx/filter Cty<>k If I create a macro to send this command to the ARCluster node station in Spot collector, it strips out the 'does not equal' "<>" and sends instead: set/dx/filter Ctyk which creates an error. This also affects many other commands as well. Can this be corrected? + As you can see in + SpotCollector uses < and > to delimit its macro commands. In the current version of SpotCollector, <> is considered a no-operation, and thus is not transmitted to the connected cluster. + I have extended the next version of SpotCollector to send <> to the cluster. + In the mean-time, you can configure SpotCollector to ignore spots of US stations by clicking the "Pre-filter button along the right side of the Configuration window's "Spot Database" tab. In the "SpotCollector Pre-filtering" window that appears, use a selector in the "Discard incoming spots of stations in selected DXCC entities" panel at the bottom to discard spots from K. This has the advantage that it works independently of the flavor of software running on the DX Clusters to which you are connected. 73,
|
Re: Macros in Spotcollector
+ AA6YQ comments below
Many times, especially during contests, I filter spots at the DX Cluster.
One of the commands that ARCluster accepts if you want to only see non-US spots is the command: set/dx/filter Cty<>k If I create a macro to send this command to the ARCluster node station in Spot collector, it strips out the 'does not equal' "<>" and sends instead: set/dx/filter Ctyk which creates an error.
This also affects many other commands as well. Can this be corrected?
+ As you can see in
+ SpotCollector uses < and > to delimit its macro commands. In the current version of SpotCollector, <> is considered a no-operation, and thus is not transmitted to the connected cluster.
+ I have extended the next version of SpotCollector to send <> to the cluster.
+ In the mean-time, you can configure SpotCollector to ignore spots of US stations by clicking the "Pre-filter button along the right side of the Configuration window's "Spot Database" tab. In the "SpotCollector Pre-filtering" window that appears, use a selector in the "Discard incoming spots of stations in selected DXCC entities" panel at the bottom to discard spots from K. This has the advantage that it works independently of the flavor of software running on the DX Clusters to which you are connected.
73,
|
The "bad spotter" problem should be cured now. Here are K9IMM's responses to a 6-meter group:
?
-----Original Message-----From: [email protected] <[email protected]> On Behalf Of Edward K9IMMSent: Monday, March 03, 2025 12:07 PMTo: [email protected]Subject: Re: [FrontRange6Meter] K9IMM SkimmerUpdate on K9IMM-# 6M Bogo-spots:I think I have it fixed. It was a rogue update of WSJT-X. Somehow, a UDP port in WSJT-X got changed to one that conflicted with my HF skimmer communications with the RBN. Occasionally HF spots from the skimmer would get injected into the 6M UDP stream. Anyway...I fixed the port number and all seems well, now. It does appear, from head-to-head comparisons on the same antenna, that the RSP1A performs pretty much exactly the same as my TS-990 on 6M, despite being about 1/80th the price. Gotta love cheap SDR's.Also...Running JT Skimmer on the same computer simultaneously with WSJT-X works fine. All that is necessary is to copy JT9.exe in the WSJT-X directory to a different name. Then point JT Skimmer at the new copy in its setup dialog.Sorry for the packet QRM, and also the crushed expectations of non-existent openings.TedK9IMM-----Original Message-----From: [email protected] <[email protected]> On Behalf Of Edward K9IMMSent: Friday, February 28, 2025 8:53 AMTo: [email protected]Subject: Re: [FrontRange6Meter] K9IMM SkimmerI do know this guy. It's me! I've been trying to figure out how to run JTSkimmer on a RSP1A in parallel with WSJT-X running on a TS-990 on the same computer. I've got a splitter on the antenna input, with the goal of seeing how well the RSP1A decodes on 6M. (The RSP1A turns out to be only 2dB worse than the TS-990 on 6M on the same antenna.)It's a work in progress, and perhaps Alex could chime in to steer me straight. Both programs use JT9.exe but won't run at the same time on it. I renamed a copy of JT9.exe to something else in the WSJT-X directory and pointed JTSkimmer toward the copy. That runs, but as you point out, has some pretty bizarre interactions. ?I'm suspecting some sort of .ini confusion between the two programs. Maybe I need to install a parallel instance of WSJT-X in another directory or something.Both the TS-990 and the RSP1A are on 6M, as are WSJT-X and JTSkimmer, but somehow 20M spots, which I noticed, or 40M spots, which you did, get spotted as 6M spots on 50313. When I noticed this behavior, I was, and still am, confused. It seems to happen even when both programs are not supposed to be dumping spots to the RBN, although I've not rigorously verified that yet.Anyway...I was trying to debug this yesterday and got distracted while both programs were running and neglected to snuff one of them. I figured that out this AM and killed one of them. All works well if just one program is running.My apologies for getting folks fired up about a phantom opening that was not real. I got pretty excited when I saw my bogo-spots, too.73,TedK9IMM-----Original Message-----From: [email protected] <[email protected]> On Behalf Of Mike W0MUSent: Thursday, February 27, 2025 11:32 PMTo: [email protected]Subject: [FrontRange6Meter] K9IMM SkimmerDoes anyone know this guy? ?Apparently the middle of Wisconsin is the place to be for 6m.The skimmer is spotting 40m spots on 6m. ?Seems like all his spots are being shown as 6m.No email address listed on QRZ.
|
Re: Spectrum-Waterfall Window
Well I am not sure what I did or what happened but the selection for Spectrum-Waterfall Display is no longer grayed out.
|
I think I got tripped by the AI word changer.
I wondered whether you meant JT9 instead of FT9?
Rich, NU6T
Fellow hams,
I am starting to hear a little bit about FT9; could someone please direct me towards a good source or two to help me learn more about it, what software package revisions I need and how well they integrate with DXLab programs?
Thanks in advance!
|
toggle quoted message
Show quoted text
Fellow hams,
I am starting to hear a little bit about FT9; could someone please direct me towards a good source or two to help me learn more about it, what software package revisions I need and how well they integrate with DXLab programs?
Thanks in advance!
|
Re: DXAtlas Map with DXView
Regarding DX Atlas not working with DX View...? This morning it's working - Version 2.41.? Must be your magic, Dave.? Thanks.
--
Bruce - W4NDX
|
Thanks all; Joe, I think you are correct (I misremembered JT9 and called it FT9).
toggle quoted message
Show quoted text
On Mar 3, 2025, at 07:55, Joe Subich, W4TV via groups.io <lists@...> wrote:
The mode is JT9 and has been around for a long time. See the WSJTX Users Guide (F1 in WSJTX). 73, ??... Joe, W4TV On 2025-03-03 12:02 AM, David Reed via groups.io wrote: Fellow hams,
I am starting to hear a little bit about FT9; could someone please direct me towards a good source or two to help me learn more about it, what software package revisions I need and how well they integrate with DXLab programs?
Thanks in advance!
73 de W5SV, Dave
|
Re: Wrong Band sort in DXKeeper's User-defined sorts
You might sort by frequency instead of band.
Vy 7 3 Earl / KD5XB DM84
e e
On Monday, March 3rd, 2025 at 3:21 AM, Ludwig Hechler, DL6FBR via groups.io <L.Hechler@...> wrote:
Hi,
?
I defined this sort in the "DXKeeper Advanced Sorts, Filters & Modifieres"
window:
?
First item: STATE
Second item: Band
Third item: Mode
?
all three in ascending order. Applying this sort it seems the Band column
is in plain alphabetical order within the same STATE, like
?
12M
160M
2M
40M
80M
?
but I think it should be ordered like this
?
2M
12M
40M
80M
160M
?
as it is when I double click the Band column in DXKeepers "Log QSOs" table.
?
Or do I miss something?
?
73,
Lui, DL6FBR
|
Re: Upload to LOTW/QRZ/eQSL/Clublog after N1MM import
Thanks so much Joe for the guidance. This is exactly what I needed.
?
I did run my file through the AC1D converter prior to importing so for whatever reason those 2 callsigns weren't corrected. Thankfully it was only 7 lines to correct.
?
73,
Tim N9PN
|
The mode is JT9 and has been around for a long time.
See the WSJTX Users Guide (F1 in WSJTX).
73,
... Joe, W4TV
toggle quoted message
Show quoted text
On 2025-03-03 12:02 AM, David Reed via groups.io wrote: Fellow hams,
I am starting to hear a little bit about FT9; could someone please direct me towards a good source or two to help me learn more about it, what software package revisions I need and how well they integrate with DXLab programs?
Thanks in advance!
73 de W5SV, Dave
|
Re: Wrong Band sort in DXKeeper's User-defined sorts
Or do I miss something? Use val(Band) to sort numerically instead of alpha. The use of "val()" is not documented, AFAIK. 73, ... Joe, W4TV On 2025-03-03 5:21 AM, Ludwig Hechler, DL6FBR via groups.io wrote: Hi,
I defined this sort in the "DXKeeper Advanced Sorts, Filters & Modifieres"
window:
First item: STATE
Second item: Band
Third item: Mode
all three in ascending order. Applying this sort it seems the Band column
is in plain alphabetical order within the same STATE, like
12M
160M
2M
40M
80M
but I think it should be ordered like this
2M
12M
40M
80M
160M
as it is when I double click the Band column in DXKeepers "Log QSOs" table.
Or do I miss something?
73,
Lui, DL6FBR
|
Hi Dave,
?
Many times, especially during contests, I filter spots at the DX Cluster.
One of the commands that ARCluster accepts if you want to only see non-US spots is the command:? set/dx/filter Cty<>k?
If I create a macro to send this command to the ARCluster node station in Spot collector, it strips out the 'does not equal'? "<>" and sends instead:? set/dx/filter Ctyk which creates an error.
This also affects many other commands as well.? Can this be corrected?
?
Jim - KR9U
|
Wrong Band sort in DXKeeper's User-defined sorts
Hi,
?
I defined this sort in the "DXKeeper Advanced Sorts, Filters & Modifieres"
window:
?
First item: STATE
Second item: Band
Third item: Mode
?
all three in ascending order. Applying this sort it seems the Band column
is in plain alphabetical order within the same STATE, like
?
12M
160M
2M
40M
80M
?
but I think it should be ordered like this
?
2M
12M
40M
80M
160M
?
as it is when I double click the Band column in DXKeepers "Log QSOs" table.
?
Or do I miss something?
?
73,
Lui, DL6FBR
|
+ AA6YQ comments below
I am starting to hear a little bit about FT9
+ Where? + Neither Google nor Perplexity could find any reference to a digital mode called FT9. ? ? 73, ? ? ? ? ?Dave, AA6YQ
|
Daniel W9DGI
John Merrill N1JM
W4NDX