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
Search
Got a 404 on a link from teh help files
|
I was trying to figure out why, when I turn skimmer on, none of the entries in Spot Collector show the # as they did on my old computer.? Still looking on that one. However, using??, the link for???(toward the top of this page) gave me a 404 error. Specifically, the link goes to??and gives a 404. I did notice that??goes to??and apparently gives a page of DX spots.? (Spot Collector has spoiled me, I don't remember how to use??!? LOL!) Vy 7 3 Earl / KD5XB e e
Sent with secure email.
|
|
On my old computer, I could go to the telnet window, issue the command "SET SKIMMER" and get Reverse Beacon spots in addition to the usual.? The RBN spots would have a # in the line -- and I don't remember if it was in the callsign or the source -- but here on my new computer, that doesn't happen. Thanks, Earl / KD5XB DM84 e e
Sent with secure email.
On Tuesday, May 20th, 2025 at 11:00 AM, Dave AA6YQ <aa6yq@...> wrote:
|
|
+ AA6YQ comments below
On my old computer, I could go to the telnet window, issue the command "SET SKIMMER" and get Reverse Beacon spots in addition to the usual.? The RBN spots would have a # in the line -- and I don't remember if it was in the callsign or the source -- but here on my new computer, that doesn't happen.+ Whatever appears in one of SpotCollector's "Spot Source" windows is exclusively under control of the spot source. + Spots from the Remote Beacon Network have -# appended to their callsign. You can configure SpotCollector's Pre-filter to ignore these; check to see if you have this option enabled: ? ? 73, ? ? ? ? ? Dave, AA6YQ |
|
Thanks, Dave, but the pre-filter is not enabled.? I guess I'll have to start looking at a telnet window and see if they're sending any. 7 3 Earl / KD5XB e e
Sent with secure email.
On Tuesday, May 20th, 2025 at 4:35 PM, Dave AA6YQ <aa6yq@...> wrote:
|
|
Well that didn't take long -- set/skimmer RBN/Skimming set to ALL MODES for KD5XB KD5XB de N6WS-6 20-May-2025 2238Z dxspider > DX de WC2L-#: ? ?28180.0 ?PY2NSA ? ? ? FT4 -14dB Q:4 Z:4,5 ? ? ? ? ? ?2238Z DX de KM3T-#: ? ?14074.0 ?N8JHZ ? ? ? ?FT8 -19dB Q:4+ Z:3,4,5 ? ? ? ? 2238Z DX de HA8TKS-#: ?10136.0 ?EA1ISE ? ? ? FT8 -21dB Q:3+ Z:14,15 ? ? ? ? 2237Z DX de LZ4UX-#: ? 14074.0 ?KZ9DX ? ? ? ?FT8 -9dB Q:9+ Z:3,5,14,20 ? ? ?2238Z DX de K9LC-#: ? ? 7074.0 ?KO0V ? ? ? ? FT8 -13dB Q:9 Z:3,4,5 ? ? ? ? ?2238Z DX de SM1HEV-#: ? 7074.0 ?OE4KSF ? ? ? FT8 -14dB Q:9+ Z:3,5,14,20 ? ? 2238Z DX de SM1HEV-#: ? 7074.0 ?HB9HOG ? ? ? FT8 -12dB Q:9+ Z:5,14,20 ? ? ? 2238Z DX de YO2CK-#: ? ?7074.0 ?R5VCW ? ? ? ?FT8 -4dB Q:4+ Z:15,20 ? ? ? ? ?2238Z unset/skimmer RBN/Skimming set to NONE for KD5XB Next, I set the filter to PY2NSA as the call, and got this:
Sent with secure email.
On Tuesday, May 20th, 2025 at 4:38 PM, kd5xb@... <kd5xb@...> wrote:
|
|
Oh geez, that one got away from me! Well that didn't take long -- set/skimmer RBN/Skimming set to ALL MODES for KD5XB KD5XB de N6WS-6 20-May-2025 2238Z dxspider > DX de WC2L-#: ? ?28180.0 ?PY2NSA ? ? ? FT4 -14dB Q:4 Z:4,5 ? ? ? ? ? ?2238Z DX de KM3T-#: ? ?14074.0 ?N8JHZ ? ? ? ?FT8 -19dB Q:4+ Z:3,4,5 ? ? ? ? 2238Z DX de HA8TKS-#: ?10136.0 ?EA1ISE ? ? ? FT8 -21dB Q:3+ Z:14,15 ? ? ? ? 2237Z DX de LZ4UX-#: ? 14074.0 ?KZ9DX ? ? ? ?FT8 -9dB Q:9+ Z:3,5,14,20 ? ? ?2238Z DX de K9LC-#: ? ? 7074.0 ?KO0V ? ? ? ? FT8 -13dB Q:9 Z:3,4,5 ? ? ? ? ?2238Z DX de SM1HEV-#: ? 7074.0 ?OE4KSF ? ? ? FT8 -14dB Q:9+ Z:3,5,14,20 ? ? 2238Z DX de SM1HEV-#: ? 7074.0 ?HB9HOG ? ? ? FT8 -12dB Q:9+ Z:5,14,20 ? ? ? 2238Z DX de YO2CK-#: ? ?7074.0 ?R5VCW ? ? ? ?FT8 -4dB Q:4+ Z:15,20 ? ? ? ? ?2238Z unset/skimmer RBN/Skimming set to NONE for KD5XB PY2NSA on 28180.0 in FT4 at 5/20/2025 2238Z (PY: Brazil) Then I displayed all spots of PY2NSA near 28.180 and got 2025-05-20 22:38 de WC2L ? ? ? ? ? (NA-E) on ? 28,180.0 : FT4 -14dB Q:4 Z:4,5 It's a real puzzler.? I don't know what to do now. Thanks again, Earl
Sent with secure email.
On Tuesday, May 20th, 2025 at 4:42 PM, Earl Needham via groups.io <kd5xb@...> wrote:
|
|
As a first step, disable all pre-filtering, and then depress the CTRL key while clicking the X button in the Filter panel at the bottom of SpotCollector's Main window. Now all incoming spots will create/update Spot Database Entries that will appear in the Spot Database Display. ? ? ?73, ? ? ? ? ?Dave, AA6YQ |
|
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:
|
|
+ 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 |
|
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:
|
|
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. |
|
In the source window
Sent with secure email.
On Tuesday, May 20th, 2025 at 5:26 PM, Dave AA6YQ <aa6yq@...> wrote:
|
|
+ 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 |
|
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. |
|
# 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 |
to navigate to use esc to dismiss