1. DXLab@groups.io
  2. Messages
   Date   
VP8ORK as VP8-F

Anthony W. DePrato
 

At 05:43 PM 1/31/2011, you wrote:
I did not see the earlier response by Joe on this subject, sorry. But
that still begs the question of how DXVIEW or SpotCollector interprets
the DXCC database as it does? I see nothing in there about all of the
VP8 calls being assigned to the Falklands.

I guess for now an override is the appropriate fix.

73
Pete K5GM



Pete
very few realize that the Post Master in Stanley is the issuing officer for ham calls. the Falklands for many years did not have telephone service between a lot of the camps and ranches on either the East or West Islands or the 20 some smaller islands surrounding them. you do not have to set a test in the Falklands but cause for years ham radio was used as the interisland telephone . many schools would hold class over the radio so that the kids out in the camps could have an education. for years i supplied crystals for a lot of the hams so they could put their radios on the interisland freq. at 2mhz. Since they figure that South Sandwich South George South Shetlands South Orkney ect. are all under the Protectant and part of VP8 one call works for all. To help keep the islands apart in your logging programs as each is a dxcc credit the programers came up with the VP8-F VP8-SG VP8-O VP8-SI VP8-SH . SO when you worked a VP8 and found out where he was you just checked which of the databases it fell into. other then base operations people on the islands that have military bases all the islands have no people living on them.
The bottom line is. if you work any VP8 it will be listed as Falklands unless you setup and exception .

73 Tony VP8BLZ
Re: DXKeeper

Marcin <maradamo@...>
 

Hi



I observe such effect, when you start DX Launcher, after start DX keeper,
and Path Finder will no start or closed after primary start

Start Path Finder over DX Launcher - the problem disappears.



Marcin SP5ES



From: dxlab@... [mailto:dxlab@...] On Behalf Of
Robert Sheskin
Sent: Wednesday, February 02, 2011 2:31 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper





I have seen that a couple of times also, stopping and restarting
Pathfinder has always worked for me.

73,
Bob N3PPH

On 2/2/2011 8:27 AM, Barry Bourgond wrote:

I keep getting the following error.

DXKeeper

Callbook error: Required version of Pathfinder not running.

I have the latest version, version 5.6.4.

Any ideas?
Re: DXKeeper

Robert Sheskin <rsheskin@...>
 

I have seen that a couple of times also, stopping and restarting
Pathfinder has always worked for me.

73,
Bob N3PPH

On 2/2/2011 8:27 AM, Barry Bourgond wrote:

I keep getting the following error.

DXKeeper

Callbook error: Required version of Pathfinder not running.

I have the latest version, version 5.6.4.

Any ideas?
DXKeeper

Barry Bourgond <barry@...>
 

I keep getting the following error.



DXKeeper

Callbook error: Required version of Pathfinder not running.



I have the latest version, version 5.6.4.



Any ideas?
WinWarbler 6.9.7 changes mode to Phone when launched

w2nra@...
 

Hi Dave,

When I launch WinWarbler 6.9.7 with FT2000D in CW and Commander showing CW-R, WinWarbler changes mode to Phone and Commander and Rig change to Phone.

If I change WinWarbler's mode to CW and close and relaunch it, it still changes mode to Phone.

WinWarbler 6.9.5 does not do this.

73, Art W2NRA
Re: my tower and the storm slightly off topic

Richard J. Fiero II W5TFW <joeyw5tfw@...>
 

I am TRULY " Shaken by the things I hear from you Guys ! "

where is your TRUST in AL Gore ! ~~~~~~~~~he has made Billions of dollars lying to all of YOU !

by the way, where IS al Gore ? surely he can explain this ?

MY NMS Button so far this year is functioning WELL !

now LAST Year,.............................................. we wont go there !


Louisiana State University !

----- Original Message -----
From: Bill
To: DXLabs List
Sent: Wednesday, February 02, 2011 4:52 AM
Subject: [dxlab] my tower and the storm slightly off topic



I had nested my crankup tower well prior to this storm hitting.
The antenna was approximately at the 35 feet level
Now it's at the 25 feet asl

that's 'Above Snow Level'.

Dave, can you convert that 'Improve SFI button' to a NMS button?

NMS = No More Snow....
worst storm in my 66 years

and it's not expected to stop for at least 8 more hours

--
---------------------------
If you were using OS/2, you'd probably be home by now.
---------------------------
Bill H. in Chicagoland
webcams at http://w9ol-towercam.webhop.org
weather at http://hhweather.webhop.org
live weathercam chat hhweather.chatango.com
my tower and the storm slightly off topic

Bill <w9ol@...>
 

I had nested my crankup tower well prior to this storm hitting.
The antenna was approximately at the 35 feet level
Now it's at the 25 feet asl

that's 'Above Snow Level'.

Dave, can you convert that 'Improve SFI button' to a NMS button?


NMS = No More Snow....
worst storm in my 66 years

and it's not expected to stop for at least 8 more hours


--
---------------------------
If you were using OS/2, you'd probably be home by now.
---------------------------
Bill H. in Chicagoland
webcams at http://w9ol-towercam.webhop.org
weather at http://hhweather.webhop.org
live weathercam chat hhweather.chatango.com
Re: Clublog

Laurent Ferracci
 

If you choose to upload each & every QSO when it's logged, clublog qill get
all the infos available at logging time.

Later, when that already-uploaded QSO gets confirmed (either LotW or QSL
card), its "QSL status" (i should have said, rather that "QSL info")
changes.

Will that "QSL status" change be uploaded to Clublog ? In my understanding,
it won't
--

Laurent F1JKJ


2011/2/2 Dave <aa6yq@...>

+++ AA6YQ comments below

--- In dxlab@..., Laurent FERRACCI <laurent@...> wrote:

Hmm, that wouldn't update uploaded QSO's QSL info, would it ?

+++ What do you mean by "QSL info". Laurent?

+++ DXKeeper could upload whatever information the user recorded in the QSO
that ClubLog can accept.

73,

Dave, AA6YQ



2011/2/2 Dave AA6YQ <aa6yq@...>

AA6YQ comments below
-----Original Message-----
From: Michael Wells [mailto:michael@...]
Sent: Tuesday, February 01, 2011 5:34 PM
To: iain macdonnell - N6ML
Cc: Dave AA6YQ; dxlab@...
Subject: Re: [dxlab] Clublog


Hi chaps

Thanks for your copy of this thread Iain.

Dave, I'd be very happy to help if there's anything you'd like to try.
Club
Log is pretty adaptable and any kind of logging suite integration is
certainly something I'm keen to do, including helping sort out the idea
of
incremental uploads if you wish.

If you provide a fast web service that accepts an uploaded QSO and
confirms its acceptance, then DXKeeper could provide an "automatically
upload each QSO to ClubLog" option that when enabled sends each QSO to
ClubLog as its logged; the user would only be notified if a connection
to
ClubLog could not be established, or if ClubLog rejected the uploaded
QSO.
After a user uploaded all existing QSOs, this capability would make
uploading automatic for all subsequently-logged QSOs.

73,

Dave, AA6YQ




------------------------------------

Yahoo! Groups Links








------------------------------------

Yahoo! Groups Links
Re: Clublog

Steve GW4BKG
 

As a DXK & ClubLog user I upload my complete ADIF log to ClubLog about once a month & delete the existing one to enable it to pick up any QSLs received & recorded in the intervening period.
ClubLog has an option to enable me to do this very easily.
Steve
GW4BKG

----- Original Message -----
From: Dave
To: dxlab@...
Sent: Wednesday, February 02, 2011 9:55 AM
Subject: [dxlab] Re: Clublog



+++ AA6YQ comments below

--- In dxlab@..., Laurent FERRACCI <laurent@...> wrote:

Hmm, that wouldn't update uploaded QSO's QSL info, would it ?

+++ What do you mean by "QSL info". Laurent?

+++ DXKeeper could upload whatever information the user recorded in the QSO that ClubLog can accept.

73,

Dave, AA6YQ

> 2011/2/2 Dave AA6YQ <aa6yq@...>
>
> > >>>AA6YQ comments below
> >
> > -----Original Message-----
> > From: Michael Wells [mailto:michael@...]
> > Sent: Tuesday, February 01, 2011 5:34 PM
> > To: iain macdonnell - N6ML
> > Cc: Dave AA6YQ; dxlab@...
> > Subject: Re: [dxlab] Clublog
> >
> >
> > Hi chaps
> >
> > Thanks for your copy of this thread Iain.
> >
> > Dave, I'd be very happy to help if there's anything you'd like to try. Club
> > Log is pretty adaptable and any kind of logging suite integration is
> > certainly something I'm keen to do, including helping sort out the idea of
> > incremental uploads if you wish.
> >
> > >>>If you provide a fast web service that accepts an uploaded QSO and
> > confirms its acceptance, then DXKeeper could provide an "automatically
> > upload each QSO to ClubLog" option that when enabled sends each QSO to
> > ClubLog as its logged; the user would only be notified if a connection to
> > ClubLog could not be established, or if ClubLog rejected the uploaded QSO.
> > After a user uploaded all existing QSOs, this capability would make
> > uploading automatic for all subsequently-logged QSOs.
> >
> > 73,
> >
> > Dave, AA6YQ
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
>
>
Re: Clublog

Dave AA6YQ
 

+++ AA6YQ comments below

--- In dxlab@..., Laurent FERRACCI <laurent@...> wrote:

Hmm, that wouldn't update uploaded QSO's QSL info, would it ?

+++ What do you mean by "QSL info". Laurent?

+++ DXKeeper could upload whatever information the user recorded in the QSO that ClubLog can accept.

73,

Dave, AA6YQ



2011/2/2 Dave AA6YQ <aa6yq@...>

AA6YQ comments below
-----Original Message-----
From: Michael Wells [mailto:michael@...]
Sent: Tuesday, February 01, 2011 5:34 PM
To: iain macdonnell - N6ML
Cc: Dave AA6YQ; dxlab@...
Subject: Re: [dxlab] Clublog


Hi chaps

Thanks for your copy of this thread Iain.

Dave, I'd be very happy to help if there's anything you'd like to try. Club
Log is pretty adaptable and any kind of logging suite integration is
certainly something I'm keen to do, including helping sort out the idea of
incremental uploads if you wish.

If you provide a fast web service that accepts an uploaded QSO and
confirms its acceptance, then DXKeeper could provide an "automatically
upload each QSO to ClubLog" option that when enabled sends each QSO to
ClubLog as its logged; the user would only be notified if a connection to
ClubLog could not be established, or if ClubLog rejected the uploaded QSO.
After a user uploaded all existing QSOs, this capability would make
uploading automatic for all subsequently-logged QSOs.

73,

Dave, AA6YQ




------------------------------------

Yahoo! Groups Links
Re: Clublog

Laurent Ferracci
 

Hmm, that wouldn't update uploaded QSO's QSL info, would it ?
--

Laurent F1JKJ


2011/2/2 Dave AA6YQ <aa6yq@...>

AA6YQ comments below
-----Original Message-----
From: Michael Wells [mailto:michael@...]
Sent: Tuesday, February 01, 2011 5:34 PM
To: iain macdonnell - N6ML
Cc: Dave AA6YQ; dxlab@...
Subject: Re: [dxlab] Clublog


Hi chaps

Thanks for your copy of this thread Iain.

Dave, I'd be very happy to help if there's anything you'd like to try. Club
Log is pretty adaptable and any kind of logging suite integration is
certainly something I'm keen to do, including helping sort out the idea of
incremental uploads if you wish.

If you provide a fast web service that accepts an uploaded QSO and
confirms its acceptance, then DXKeeper could provide an "automatically
upload each QSO to ClubLog" option that when enabled sends each QSO to
ClubLog as its logged; the user would only be notified if a connection to
ClubLog could not be established, or if ClubLog rejected the uploaded QSO.
After a user uploaded all existing QSOs, this capability would make
uploading automatic for all subsequently-logged QSOs.

73,

Dave, AA6YQ




------------------------------------

Yahoo! Groups Links
Re: Clublog

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: Michael Wells [mailto:michael@...]
Sent: Tuesday, February 01, 2011 5:34 PM
To: iain macdonnell - N6ML
Cc: Dave AA6YQ; dxlab@...
Subject: Re: [dxlab] Clublog


Hi chaps

Thanks for your copy of this thread Iain.

Dave, I'd be very happy to help if there's anything you'd like to try. Club
Log is pretty adaptable and any kind of logging suite integration is
certainly something I'm keen to do, including helping sort out the idea of
incremental uploads if you wish.

If you provide a fast web service that accepts an uploaded QSO and
confirms its acceptance, then DXKeeper could provide an "automatically
upload each QSO to ClubLog" option that when enabled sends each QSO to
ClubLog as its logged; the user would only be notified if a connection to
ClubLog could not be established, or if ClubLog rejected the uploaded QSO.
After a user uploaded all existing QSOs, this capability would make
uploading automatic for all subsequently-logged QSOs.

73,

Dave, AA6YQ
Re: Feedback on upload for N6ML

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Laurent FERRACCI
Sent: Wednesday, February 02, 2011 3:51 AM
To: dxlab@...
Subject: Re: [dxlab] Fwd: Feedback on upload for N6ML


That's what it would be great to see DxLab use ClubLog by querying its
database in real-time, as it does for QRZ.com (mutatis mutandis).

DXKeeper queries QRZ.com over the internet when logging a QSO -- and some
users find this unacceptably slow.

Querying ClubLog over the internet whenever it's necessary to determine a
callsign's DXCC entity -- e.g. when a DX spot arrives -- would result in a
large reduction in performance.

73,

Dave, AA6YQ
Re: VP8ORK

Laurent Ferracci
 

http://www.clublog.org/test.php?call=vp8ork&&api=1
<http://www.clublog.org/test.php?call=vp8ork&&api=1>
http://www.clublog.org/test.php?call=vp8ssi&api=1
<http://www.clublog.org/test.php?call=vp8ssi&api=1>
http://www.clublog.org/test.php?call=vp8lp&api=1

<http://www.clublog.org/test.php?call=vp8lp&api=1>;-)

--

Laurent F1JKJ


2011/1/31 Anthony W. DePrato <wa4jqs@...>


I still don't understand why the VP8-O fails to match up with VP8ORK. Why
include VP8-O if it won't match up with any VP8 whose suffix begins with
O?
Surely, no call will be issued with a hyphen in it, therefore my
assumption
that such mdb entries are meant to match up with any call whose suffix
begins with the letter after the hyphen. Otherwise, why include such
hyphenated "examples" in the mdb file?

73,
--
Ken - K4XL
ken first of all there are no calls issued from Stanley for just
south sandwich ,Orkney, south Georgia ect. all VP8 calls are issued
in the Falklands and can be used on any of the islands. so there is
really no way to tell where the station is until he tells you. my
VP8BZL call has been used on the ICE,
Falklands,S.Georgia,S.Shetlands. VP8-O ect is just for setting up
exceptions.
73 Tony
WA4JQS/ VP8SSI/ VP8BZL



------------------------------------

Yahoo! Groups Links
Re: Feedback on upload for N6ML

Laurent Ferracci
 

That's what it would be great to see DxLab use ClubLog by querying its
database in real-time, as it does for QRZ.com (mutatis mutandis).

Of course that would work only if the "ClubLog exception" already exists,
but in that case it would help the DXer the way he needs.

73

--

Laurent F1JKJ


2011/2/1 Dave AA6YQ <aa6yq@...>

An after-the-fact correction is better than no correction, but a DXer needs
to know where CE9/VE3LYC before the QSO is logged, not after it's logged
and
uploaded.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
iain macdonnell - N6ML
Sent: Tuesday, February 01, 2011 4:34 PM
To: dxlab
Subject: [dxlab] Fwd: Feedback on upload for N6ML


Here's an example of the power of ClubLog....

~iain / N6ML


---------- Forwarded message ----------
From: <upload@...>
Date: Tue, Feb 1, 2011 at 9:30 PM
Subject: Feedback on upload for N6ML
To: ar@...


Dear N6ML,

While processing your ADIF for Club Log, the following possible
problems were detected. Your log may be correct, but if necessary you
can resolve these problems and create a new ADIF. If you make changes,
it's recommended that on your next upload you use the option to clear
your existing log, to avoid leaving prior records in Club Log.

If you would like to discuss these problems, then please open a
discussion on the reflector, or contact Alan 5B4AHJ who maintains the
Club log exceptions list. You can disable these emails from the
Settings page if you prefer.

Google Groups Reflector: http://groups.google.com/group/clublog
Alan 5B4AHJ: g3pmr@...

73 de Michael G7VJR

Callsign: CE9/VE3LYC Date: 2011-01-11 04:31:02 Band: 30
QSL:
No
Your log claims ANTARCTICA. Club Log has a specific exception for
CE9/VE3LYC and will use CHILE.
See http://www.clublog.org/t.php?c=CE9/VE3LYC&t=1294720262 for details.
Note: There are comments about CE9/VE3LYC in the Club Log database,
which may provide further details. See
http://www.clublog.org/t.php?c=CE9/VE3LYC&t=1294720262.


------------------------------------

Yahoo! Groups Links



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1435/3416 - Release Date: 02/01/11



------------------------------------

Yahoo! Groups Links
Re: Using Filters

Jim Brown <jwbro@...>
 

Thanks Dave.
73, Jim K9YC

As you can see, most items are of data type
"text string", but there are
a few exceptions.
Re: DXKeeper bug?

martyn1ht
 

Ok. I missed that ctrl-key thing. Thanks, Dave.
73,
Marty, N1HT

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

+++ more AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
martyn1ht
Sent: Tuesday, February 01, 2011 6:58 PM
To: dxlab@...
Subject: [dxlab] Re: DXKeeper bug?

When you generated the outgoing spot from the Capture window, where did
you specify your comment?

In the box labeled "comment" right above the contest mode check box.

+++That box is exclusively used to record a comment with the QSO. To specify
notes to be included with an outgoing spot generated from the Capture
window, depress the CTRL key while clicking the Capture window's Spot
button, and you'll be prompted to specify your notes.

73,

Dave, AA6YQ
Skimmers (WAS: K1TTT Cluster Node in SpotCollector)

Paul M Dunphy
 

At 10:05 PM 2/1/2011, you wrote:
You're right, Paul... I never trust spots completely, and I never log a call
unless I've personally verified it on the air... a habit I've gotten into
after getting burnt a few times. We're having an ice storm here but as soon
as I can I'll give your suggestions a try. Thanks, OM.

73, Jerry K3BZ
First of all, I must apologize to the group for my typos in the precious message. I actually can spell and type, and I'm not under the influence of any drugs or alcohol. I just type too fast and don't proof read my message. :-)

With respect to Skimmers, Lee, VE7CC and I are both collecting spots from the full RBN (Reverse Beacon Network) as well as half a dozen individual Skimmers. Lee's Cluster software removes replicates, and there are many, because multiple Skimmers will pick up the same station calling CQ. If you use VE7CC or VE1DXI as a spot source, you *will not* see this unless you issue the SET/SKIMMER command (and SET/NOSKIMMER to disable it.) You will just get regular spots from humans.

With Skimmers enabled, you will get 3-4 times the volume of spots. The extra ones will all be CW, and will be from Skimmers that catch stations calling CQ. It is a fast way to know they are there.

I have been feeding SpotCollector for over 2 weeks with SET/SKIMMER enabled, as well as having 3 other "traditional" nodes connected. It has never given me any trouble in terms of performance. It can handle the additional spots well. I should add that my VE1DX "account" on the VE1DXI node is set to reject K spots. This is not because I do not like US stations, but because I am unsure if SpotCollecter can handle all of them (and because I am a DXer and have the USA confirmed on all bands and modes.) This is done with the following command on CC Clusters:

SET/FILTER DXCTY/REJECT K

As was discussed with K3BZ, Skimmer spots are not perfect. Some rough statistics we've come up with indicate up to 10% of the Skimmer spots can be busted calls. Some Skimmers are better than others. VE7CC's software does everything possible to check for obvious errors (looking the US ones up in the FCC database before forwarding them, for example, and numerous other sanity checks.) Nevertheless, some busted calls will get through. As Jerry, K3BZ, and I have said, verify what the DX Cluster says. In particular watch out for Skimmer spots (they are identified as the spotter having a call ending in -#)

I feel, after 2-3 weeks use, that the benefits of Skimmer spots far outweigh the false positives of the busted calls. After all, if anything really rare is activated, we'll know. A P5 or 7O anything coming out of the blue is extremely unlikely to be real. However, right now, knowing VP8ORK is calling CQ on 18.074 MHz (before he finishes!) will be an advantage to you over those waiting for someone to manually spot it.

As I said before, use either the VE7CC-1 or VE1DXI node (we are linked so you will get identical spots from either) and experiment with the Skimmers and SpotCollector. It may not be for you; it may cause problems on your particular system in terms of resource utilization, etc. All I can say is it works for me, and works well with SpotCollector.

73, Paul VE1DX (ve1dxi.no-ip.com:23)
Re: Path View Suggestion

chuckstalkie
 

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
chuckstalkie
Sent: Tuesday, February 01, 2011 9:05 PM
To: dxlab@...
Subject: [dxlab] Path View Suggestion


Good Day...

Suggestion: In CQ Magazine, February 2011, on page 54, another propagation
prediction tool is discussed.

One feature they have, which I personally like, is the ability (I believe)
to put in a country or continent, instead of a longitude or lattitude.

Can a field be added to Path View, which uses a country or continent,
instead of the longitude or lattitude. Too many times, we do not know the
longitude or lattitude.

It would make the tool more useful.

If you have DXView running alongside PropView, you can select a location
- by entering a callsign or callsign fragment, entering a DXCC country code,
entering a grid square, or entering an IOTA tag and then striking the Enter
key

- by selecting a DXCC prefix or by selecting a DXCC entity

- by clicking on the world map

Whatever location you select in DXView is what PropView will use when you
direct it to generate a propagation forecast.

You can also right click an entry in SpotCollector's Spot Database
Display and select the "Predict Propagation" menu item; SpotCollector will
direct PropView to generate a propagation forecast from you QTH to the
select entry's station.

In
<http://www.dxlabsuite.com/propview/Help/Operation.htm>

Note that the descriptions of "Latitude" and "Longitude" in the "DX
Station panel" section say

"if DXView is installed, PropView sets this component to its
currently-selected location"

73,

Dave, AA6YQ
Thanks Dave!!!

DXLabs really has everything. I'm going to try it right now.

Thanks again!

73 Chuck KI4HJH
Re: Path View Suggestion

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
chuckstalkie
Sent: Tuesday, February 01, 2011 9:05 PM
To: dxlab@...
Subject: [dxlab] Path View Suggestion


Good Day...

Suggestion: In CQ Magazine, February 2011, on page 54, another propagation
prediction tool is discussed.

One feature they have, which I personally like, is the ability (I believe)
to put in a country or continent, instead of a longitude or lattitude.

Can a field be added to Path View, which uses a country or continent,
instead of the longitude or lattitude. Too many times, we do not know the
longitude or lattitude.

It would make the tool more useful.

If you have DXView running alongside PropView, you can select a location
- by entering a callsign or callsign fragment, entering a DXCC country code,
entering a grid square, or entering an IOTA tag and then striking the Enter
key

- by selecting a DXCC prefix or by selecting a DXCC entity

- by clicking on the world map

Whatever location you select in DXView is what PropView will use when you
direct it to generate a propagation forecast.

You can also right click an entry in SpotCollector's Spot Database
Display and select the "Predict Propagation" menu item; SpotCollector will
direct PropView to generate a propagation forecast from you QTH to the
select entry's station.

In
<http://www.dxlabsuite.com/propview/Help/Operation.htm>

Note that the descriptions of "Latitude" and "Longitude" in the "DX
Station panel" section say

"if DXView is installed, PropView sets this component to its
currently-selected location"

73,

Dave, AA6YQ
120601 - 120620 of 209599