Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
Re: Spots per minute
+ AA6YQ comments below
So it's 0715Z, I just woke up and checked Spot Collector. I'm receiving about 37 spots per minute with all skimmers turned off. Is this normal? Seems kinda low. + At 2033Z, I'm receiving 11.4 spots per minute from K1RFI, N6WS, JH1RFM, DH8WR, and DX Summit + With the solar flux index at 119, this isn't surprising. Re-enabling my local instance of WSJT-X on 20m will significantly increase the number of spots, as it's decoding ~50 signals every 15 seconds. 73, Dave, AA6YQ |
|
Re: appending the log
I tried by TCP/IP.? Current log4OM manual says to use with slicemaster.? Unable to get it to work.? Using Omnirig was the only way I could get it to work. Greg AB7R
Sent with secure email.
On Wednesday, May 21st, 2025 at 6:31 PM, Dave AA6YQ <aa6yq@...> wrote:
-- ?
73,
Greg - AB7R
?
Flex 8600
PGXL & TGXL
AG |
|
Re: Fat-finger problem in Spot Collector
Good idea. I meant to include this in my original message, but forgot -- my checklist is at?? Vy 7 3 Earl / KD5XB e e
Sent with secure email.
On Wednesday, May 21st, 2025 at 2:23 PM, Dave AA6YQ <aa6yq@...> wrote:
|
|
Re: DXKEEPER NOT POPULATING ALL QSO DATA
+ AA6YQ comments below
+ When you are making QSOs with WSJT-X, you must log them by clicking WSJT-X's Log button - not by using DXKeeper's Capture window. If you've been doing this in the past, then you either have configured SpotCollector to use WSJT-X as a spot source (which sends the QSO information to DXKeeper when you click the WSJT-X Log button) or you've been using JTAlert, which also sends the QSO information to DXKeeper when you click the WSJT-X Log button. ? ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ
|
|
Re: Fat-finger problem in Spot Collector
+ AA6YQ comment sbelow
Once I got it going again, I started going through ALL the config settings in Spot Collector, one-by-one like a checklist.? I had a hit on the first one!? Apparently, some time in the past, I meant to set "Maximum Separation in Time) to 60, which is reasonable, but I found it set to 600!!!?+ With that setting, each time a new spot arrived that was not a duplicate of a recently-received spot (e.g. from another cluster), SpotCollector was searching through the last 600 minutes (10 hours) of Spot Database Entries looking for an existing Spot Database Entry matching that new spot. If your Spot Database contains only an hour's worth of spots, this would have no adverse impact, but with a larger Spot Database, a lot of CPU time would be spent needlessly searching. + When you have a DXLab application working they way you want it, terminate it and direct the Launcher to save its settings to a Workspace. Then if you experience an unexpected change in the future, you can direct the Launcher to restore those setting to quickly recover from an inadvertent setting change. ? ? ?73, ? ? ? ? ? ?Dave, AA6YQ |
|
DXKEEPER NOT POPULATING ALL QSO DATA
HI THERE, I AM USING DXLAB FROM 2007 AND IT IS FOR ME THE BEST. A FEW DAYS AGO AND I AM NOT SURE IF IT WAS AFTER THE INSTALATION OF THE LATEST VERSION OF DXKEEPER 18.1.4 DXKEEPER STARTED DOING THIS, AND IT DRIVES ME NUTS.?
THIS IS HAPPENING IS WHEN I CONCLUDE A QSO ONLY FROM WSJT-X RUNNING FT8 OR FT4. WHEN I ENTER A CALLSIGN AT THE? DXKEEPERS CAPTURE WINDOW AND PRESS LOG ALL THE DATA ARE THERE. BUT NOT FROM WSJT-X.
IT IS NOT FILLING UP (THE QTH TAB THE TX FREQUENCY TAB THE ADDRESS TAB THE CONTINENT TAB CQ TAB ITU TAB) WHAT IS CAUSING THAT I HAD NO PROBLEM BEFORE IT STARTEDBAS I SAID A FEW DAYS AGO.
YOUR HELP WILL BE GREATLY APPRECIATED. |
|
Fat-finger problem in Spot Collector
For MONTHS now, I've been having an on-again off-again problem.? If I let my spot database get too large (around 10,000 entries is when I start noticing it), it gets slower & slower processing spots, until it finally just stops doing ANYTHING and I usually have to use Task Manager to kill the program before staring over. Well, this morning, it happened again.? I had let it run overnight, and the database had around 20,000 entries, and when I first came into the radio room this morning, the Q said 842 and was just sitting there, not processing. Once I got it going again, I started going through ALL the config settings in Spot Collector, one-by-one like a checklist.? I had a hit on the first one!? Apparently, some time in the past, I meant to set "Maximum Separation in Time) to 60, which is reasonable, but I found it set to 600!!!? My finger must have bounced on the 0 key and I never noticed.? Spot |Collector sure seems to run better now that it's changed to 60, with my current database at ~11,300 and all Telnet sources are turned on with skimmer turned on throughout.? Oops, now we're at ~11,350... A fat-fingered wrod ot teh wsie... Vy 7 3 Earl / KD5XB DM84 e e
Sent with secure email.
|
|
Re: Got a 404 on a link from teh help files
# more AA6YQ comments below
+ I strongly disagree. The core principle underlying SpotCollector is that there is exactly one Spot Database Entry for a station operating in a specific mode near a specific frequency - no matter how many times that station has recently been spotted, and no matter the locations of the spotting stations. That one Spot Database Entry contains information harvested from all relevant spots.Square that with the display I get when I right click on a spot database entry and click "Display spots of XX#YYY near 14###.## in MM"? I see multiple spots from multiple spotters. Those spots should differentiate between a human source and a Skimmer source ... or between station W4TV and W4TV-4 if I'm running two rigs with two versions of SC. # The "Display spots of XX#YYY near 14###.## in MM" command shows you all spots that contributed to the Spot Database Entry you right-clicked - including the spotting stations. # The callsigns of spotted stations are displayed with appendages like -# and -4 removed. # As you just pointed out via email, there is an unintentional regression in SpotCollector 9.9.2: spotting station callsigns are displayed with appendages like -# and -4 removed; in previous versions of SpotCollector, they were displayed. # I have sent you and Earl KD5XB a new version of SpotCollector with this defect corrected. 73, Dave, AA6YQ |
|
Re: Got a 404 on a link from teh help files
On 2025-05-20 7:30 PM, Dave AA6YQ wrote:
+ I strongly disagree. The core principle underlying SpotCollector isthat there is exactly one Spot Database Entry for a station operating in a specific mode near a specific frequency - no matter how many times that station has recently been spotted, and no matter the locations of the spotting stations. That one Spot Database Entry contains information harvested from all relevant spots. Square that with the display I get when I right click on a spot database entry and click "Display spots of XX#YYY near 14###.## in MM"? I see multiple spots from multiple spotters. Those spots should differentiate between a human source and a Skimmer source ... or between station W4TV and W4TV-4 if I'm running two rigs with two versions of SC. 73, ... Joe, W4TV On 2025-05-20 7:30 PM, Dave AA6YQ wrote: + AA6HQ comments below+ I strongly disagree. The core principle underlying SpotCollector is that there is exactly one Spot Database Entry for a station operating in a specific mode near a specific frequency - no matter how many times that station has recently been spotted, and no matter the locations of the spotting stations. That one Spot Database Entry contains information harvested from all relevant spots. |
|
Re: Got a 404 on a link from teh help files
+ AA6HQ comments below
It's not the Spotted station in question - it's the *Spotting Station*+ I strongly disagree. The core principle underlying SpotCollector is that there is exactly one Spot Database Entry for a station operating in a specific mode near a specific frequency - no matter how many times that station has recently been spotted, and no matter the locations of the spotting stations. That one Spot Database Entry contains information harvested from all relevant spots. + The specific definitions of "near" and "recently" are user-configurable. ? ? ? 73, ? ? ? ? ? ?Dave, AA6YQ |
|
Re: Got a 404 on a link from teh help files
In the source window
Sent with secure email.
On Tuesday, May 20th, 2025 at 5:26 PM, Dave AA6YQ <aa6yq@...> wrote:
|
|
Re: Got a 404 on a link from teh help files
On 2025-05-20 7:08 PM, Dave AA6YQ wrote:
You wouldn't want two different Spot Database Entries for the same station because it was conveyed by a DX Cluster and by the RemoteIt's not the Spotted station in question - it's the *Spotting Station* (Source). You most certainly would want two database entries if W1XX (human) and W1XX-# skimmer generated independent spots of P5DX. Further, *all* skimmer spots are conveyed by the DX Cluster network even though they are originated by the Remote Beacon Network. 73, ... Joe, W4TV On 2025-05-20 7:08 PM, Dave AA6YQ wrote: + AA6YQ comments below+ That's correct behavior. You wouldn't want two different Spot Database Entries for the same station because it was conveyed by a DX Cluster and by the Remote Beacon Network. |
|
Re: Got a 404 on a link from teh help files
OK, but I get NO #'s at all. Earl
Sent with secure email.
On Tuesday, May 20th, 2025 at 5:08 PM, Dave AA6YQ <aa6yq@...> wrote:
|
|
Re: Got a 404 on a link from teh help files
+ AA6YQ comments below
I've also disabled all but one of my spot sources to make it easier for me to keep up.? Still getting the same effect, the # shows in the telnet window but not in the database display.+ That's correct behavior. You wouldn't want two different Spot Database Entries for the same station because it was conveyed by a DX Cluster and by the Remote Beacon Network. ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ |
|
Re: Qsl's Question
+ AA6YQ comments below
Hello all, have a Question is there a way on the Qsl card you design that you can move the Qso report grid lines further up or down by itself or it always have to move together with the Station Callsign ?\+ The relative positions of the components on generated QSL cards and labels are fixed. DXKeeper's QSL-generating capability is intentionally utilitarian, aimed at generating cards or labels that request needed confirmations. If you need more flexibility, DXKeeper can generate an ADIF or tab-delimited file from the QSL Queue that can be used to drive a more flexible QSL generating application. See ? ? ?73, ? ? ? ? ? ? ?Dave, AA6YQ |
|
Re: Got a 404 on a link from teh help files
Done -- I've also disabled all but one of my spot sources to make it easier for me to keep up.? Still getting the same effect, the # shows in the telnet window but not in the database display. Earl / KD5XB
Sent with secure email.
On Tuesday, May 20th, 2025 at 4:54 PM, Dave AA6YQ <aa6yq@...> wrote:
|
to navigate to use esc to dismiss