I realized that when I pushed send. HE not a consideration here. No chance. ?.
Well maybe if I put all of my stocks into antennas. Oh wait, market down over 1000 today.
Sent from my Verizon, Samsung Galaxy smartphone
Get
toggle quoted message
Show quoted text
Honor Roll
?
?
Example of part of a DXCC progress report
?
?
??? HR Mixed???????? 176???????? 153
?
What does the HR mean?
?
Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb
?
--
W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
-- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
|
|
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of Gilbert Baron W0MN
Sent: Monday, February 24, 2020 7:45 PM
To: [email protected]
Subject: [DXLab] DXCC Progress? Example of part of a DXCC progress report ? ? ??? HR Mixed???????? 176???????? 153 ? What does the HR mean? ? Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb ?
--
W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
|
Example of part of a DXCC progress report ? ? ??? HR Mixed???????? 176???????? 153 ? What does the HR mean? ? Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb ? -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
Re: Filter Band and Mode Confusion
As another option, I can tell my really good friend Shin JA1NUT to quit spotting on 20 meters.
(just a joke)
Don
WB6BEE
|
Re: Filter Band and Mode Confusion
Tnx Dave, very informative. Hard to get used to a new way of thinking. I have gone to the PropView approach. Much more powerful
...and I have been searching/reading as much as I can, but the docs are so extensive that it takes quite a bit of study to absorb what is needed, even for the most elementary process.
One more question, but will put it into a separate message. 73, N0AN
On Mon, Feb 24, 2020 at 3:25 PM Dave AA6YQ < aa6yq@...> wrote: + AA6YQ comments below
Call: VP8SJ
Filter: Band and Origin and Call=VP8PJ
Band Filter: All HF (and a few select others 6m)
Origin Filter: NA-E NA-M and NA-W
Why are spots from:
EA3AGQ
F4HAU
Showing up in the SpotCollector Table view?
+ That view displays active DX stations, not spots. As you have it filtered, it will display any active DX station that's been spotted from NA-E, NA-M, or NA-W.? The fact that a station spotted from NA-E, NA-M, or NA-W has also been spotted by EA3AGW or F4HAU does prevent that station's entry from being displayed.
+ Consider this scenario:
1. your next-door neighbor spots P5DX on 14005 CW with the comment "begging"
2. JA1NUT spots P5 on 14005 CW
+ Should the Spot Database Entry for P5CW be hidden because P5CW was last spotted by JA1NUT?
+ Using SpotCollector's ability to obtain a propagation forecast from PropView for each active station (or each needed active station, if you prefer) makes it possible to filter the? Spot Database Display based on "probability of an opening"; this is generally a more reliable way to hide active stations that you are unlikely to be able to work; see
<>
+ If you check the "Record individual spot information" box in the Controls panel on the Configuration window's "Spot Database" tab, then you can right-click a Spot Database Entry and select "Display Spots". A window will appear containing each spot of the Entry's station, in chronological order with the spotter's location indicated. This window is live, meaning new spots of the station will be appended in real time. This makes it easy to see the locations from which an active station are being spotted. The "spot notes" can also provide information useful in breaking a pileup, e.g. the last frequency worked or the pattern.
+ If you haven't yet reviewed
<>
+ I suggest that you do so.
? ? ?73,
? ? ? ? ? ? Dave, AA6YQ
|
Re: Filter Band and Mode Confusion
+ AA6YQ comments below
Call: VP8SJ
Filter: Band and Origin and Call=VP8PJ
Band Filter: All HF (and a few select others 6m)
Origin Filter: NA-E NA-M and NA-W
Why are spots from:
EA3AGQ
F4HAU
Showing up in the SpotCollector Table view?
+ That view displays active DX stations, not spots. As you have it filtered, it will display any active DX station that's been spotted from NA-E, NA-M, or NA-W. The fact that a station spotted from NA-E, NA-M, or NA-W has also been spotted by EA3AGW or F4HAU does prevent that station's entry from being displayed.
+ Consider this scenario:
1. your next-door neighbor spots P5DX on 14005 CW with the comment "begging"
2. JA1NUT spots P5 on 14005 CW
+ Should the Spot Database Entry for P5CW be hidden because P5CW was last spotted by JA1NUT?
+ Using SpotCollector's ability to obtain a propagation forecast from PropView for each active station (or each needed active station, if you prefer) makes it possible to filter the Spot Database Display based on "probability of an opening"; this is generally a more reliable way to hide active stations that you are unlikely to be able to work; see
<>
+ If you check the "Record individual spot information" box in the Controls panel on the Configuration window's "Spot Database" tab, then you can right-click a Spot Database Entry and select "Display Spots". A window will appear containing each spot of the Entry's station, in chronological order with the spotter's location indicated. This window is live, meaning new spots of the station will be appended in real time. This makes it easy to see the locations from which an active station are being spotted. The "spot notes" can also provide information useful in breaking a pileup, e.g. the last frequency worked or the pattern.
+ If you haven't yet reviewed
<>
+ I suggest that you do so.
73,
Dave, AA6YQ
|
Filter Band and Mode Confusion
Call: VP8SJ Filter: Band and Origin and Call=VP8PJ
Band Filter: All HF (and a few select others 6m)
Origin Filter: NA-E NA-M and NA-W
Why are spots from: EA3AGQ F4HAU Showing up in the SpotCollector Table view?
73, N0AN
|
Re: Network Local Spots Overwhelming N6WS
Bill, Thanks! That was it. I assume I leave WSJT-X Enable unchecked in SpotCollector Config?
Now if I can just get an audio alert from SpotCollector whenever VP8PJ is spotted from North America on any band and any mode, I'll be set.
I have JTA alerting on VP8PJ , but of course, that is from WSJX-X decodes in real time.
73, N0AN
On Mon, Feb 24, 2020 at 7:52 AM g4wjs < bill.8@...> wrote:
On 24/02/2020 13:48, Hasan Schiers N0AN
wrote:
Forest for
the Trees Problem
I'm using
WSJT-X . I do not want it's decoded stations as spot sources
for the Spot Collector Display.
I only want
to see spots sourced from N6WS
I have gone
into :
SpotCollector
Configuration and Unchecked:WSJT-X Enable.
SpotCollector
Tabular Display continues to be saturated with Spots from my
WSJT-X Decodes. (and the N6WS spots get lost in the ridiculous
volume of my own decodes.
I want
HamApps to to my Alerting, so I can't turn off the UDP
connection.
2nd Problem:
If I use
VP8PJ as the Callsign Filter, even though I have set Origin
Filter to NA-E, M and W, I still see spots? sourced from all
over the world, which are not of any interest to me.
The goal here
is to see spots of VP8PJ that only originated in North America
I"ve used
search and read what I can, but I cannot find the obvious. It
seems to me that NOT enabled WSJT-X in the SpotCollector
config should do it, but it doesn't. Maybe I have to close
SpotCollector and restart it?
Thanks In
Advance
73, N0AN
Hi Hasan,
sounds like you have turned on the option in JTAlert to post
decodes as local spots in SpotCollector.
--
73
Bill
G4WJS.
|
Re: Network Local Spots Overwhelming N6WS
On 24/02/2020 13:48, Hasan Schiers N0AN
wrote:
Forest for
the Trees Problem
I'm using
WSJT-X . I do not want it's decoded stations as spot sources
for the Spot Collector Display.
I only want
to see spots sourced from N6WS
I have gone
into :
SpotCollector
Configuration and Unchecked:WSJT-X Enable.
SpotCollector
Tabular Display continues to be saturated with Spots from my
WSJT-X Decodes. (and the N6WS spots get lost in the ridiculous
volume of my own decodes.
I want
HamApps to to my Alerting, so I can't turn off the UDP
connection.
2nd Problem:
If I use
VP8PJ as the Callsign Filter, even though I have set Origin
Filter to NA-E, M and W, I still see spots? sourced from all
over the world, which are not of any interest to me.
The goal here
is to see spots of VP8PJ that only originated in North America
I"ve used
search and read what I can, but I cannot find the obvious. It
seems to me that NOT enabled WSJT-X in the SpotCollector
config should do it, but it doesn't. Maybe I have to close
SpotCollector and restart it?
Thanks In
Advance
73, N0AN
Hi Hasan,
sounds like you have turned on the option in JTAlert to post
decodes as local spots in SpotCollector.
-- 73
Bill
G4WJS.
|
Network Local Spots Overwhelming N6WS
Forest for the Trees Problem
I'm using WSJT-X . I do not want it's decoded stations as spot sources for the Spot Collector Display. I only want to see spots sourced from N6WS
I have gone into : SpotCollector Configuration and Unchecked:WSJT-X Enable.
SpotCollector Tabular Display continues to be saturated with Spots from my WSJT-X Decodes. (and the N6WS spots get lost in the ridiculous volume of my own decodes.
I want HamApps to to my Alerting, so I can't turn off the UDP connection.
2nd Problem:
If I use VP8PJ as the Callsign Filter, even though I have set Origin Filter to NA-E, M and W, I still see spots? sourced from all over the world, which are not of any interest to me.
The goal here is to see spots of VP8PJ that only originated in North America
I"ve used search and read what I can, but I cannot find the obvious. It seems to me that NOT enabled WSJT-X in the SpotCollector config should do it, but it doesn't. Maybe I have to close SpotCollector and restart it?
Thanks In Advance 73, N0AN
|
toggle quoted message
Show quoted text
On Sun, Feb 23, 2020 at 10:26 AM, w5ec wrote:
OK, this is not a button. It is now enabled so I should never have to do it again.
+ When you have DXKeeper and your other DXLab applications configured to your taste, terminate all of them except the Launcher, direct the Launcher to create and populate a Workspace:
<
+ and place a backup copy of that Workspace someplace safe (e.g. on a thumb drive, or in DropBox or OneDrive).
+ Then when you next experience a catastrophic hardware or software failure - which is pretty much guaranteed to happen at some point --? you'll be able to quickly recover all of your DXLab application settings.
? ? ? ?73,
? ? ? ? ? ? ?Dave, AA6YQ
?
|
updated eQSL AG and LoTW databases are available...
...via the Databases tab on DXView's Configuration window.
73,
Dave, AA6YQ
|
toggle quoted message
Show quoted text
On Sun, Feb 23, 2020 at 10:22 AM, w5ec wrote:
I've never done that before but I certainly will from now on.
+ Take a look at all of the import options, as there my be others you wish to enable:
<
? ? ? ? ? 73,
? ? ? ? ? ? ? ?Dave, AA6YQ
|
OK, this is not a button. It is now enabled so I should never have to do it again.
Bill W5EC
|
I've never done that before but I certainly will from now on.
Bill W5EC
|
+ AA6YQ comments below
Simply amazing! I've never done that before--never had to.
I went through the whole updating and syncing process and there it was.
About 99.9% of the new QSOs were LOTW users and all in yellow.
+ Had you enabled the "Update LoTW Membership" option on the "Import QSOs" tab before clicking the Start button, your imported QSOs would be been updated to reflect LotW participation.
73,
Dave, AA6YQ
|
+ AA6YQ comments below
My DXKeeper log has thousands of QSOs and of those QSOs the LOTW users are colored yellow.
I have recently imported my FT8 QSOs into DXKeeper and not a single one of hundreds of FT8 QSOs are colored any color. It seems like they are ignored by DXKeeper. I can't believe that none of them are not LOTW users.
Any ideas?
+ Before you clicked the Start button on DXKeeper's Main window's "Import QSOs" tab, did you enable the "Update LoTW membership" option in the upper-left corner of that tab?
73,
Dave, AA6YQ
|
Simply amazing! I've never done that before--never had to.
I went through the whole updating and syncing process and there it was.
About 99.9% of the new QSOs were LOTW users and all in yellow.
Thanks.
Bill W5EC
|
|
|
Gilbert Baron W0MN
wb6bee