开云体育

This message is sent to all new members, and to all members
every now and then. It has been revised as bounce reports have
changed a bit.

Any of us could experience no longer receiving email from the
UI-View support list. You might want to print this message and
review it if you stop receiving messages from the UI-View list.

If you stop receiving messages from the UI-View list, suspect
that either...

1) this or some other Yahoo group that you are a member of is
sending email which some spamblocker system regard as spam or
junk mail (quite a lot of these reports since summer 2009).

2) it may be that your email account has filled up with unread
messages or that the account on your mail server has ran out of
storage space. Read or delete the old messages on your mail server.

3) Some MSN or Hotmail accounts, and others such as arrl.net,
qsl.net which are used as a forwarding address from time to time
cannot forward to your primary address. When this hapens, the
Yahoo group receives an error message with something like
"impossible to relay to xxx" and you are then in the "bounced"
list. There are increasing numbers of bounces from some service
providers about messages which are blocked by them for policy
reasons.

4) You or your email provider have set up a challenge-and-response
system for those sending e-mail to you. The moderators will not
send replies to such challenges. You should select another
address for your list membership(s).

Sorry, but we cannot investigate every one of these blockings.
Please be aware that if you haven't received list messages
for some days, and reactivation requests are not reaching
you, or not answered by you, your account at the UI-View
list may be deleted. It may deleted if several bounces occur
in less than a week or two. It will also be deleted if the
bounce report says that your address is invalid, discontinued,
or unknown. Be aware that the bounce can relate to messages
from other lists than the UI-View list if you are a member
of other Yahoo groups.

If your membership is deleted, you will not be able to log
into the Yahoo group. If you try and send email to the group,
it will be rejected. However, you can subscribe again with a
valid and working email account by sending an empty email to
ui-view-subscribe@....

If you are away for some time, you might want to set your
account to temporarily receive only special messages or
even no email at all, but we recommend that still receive
special messages. You can log into the Yahoo group when you
return and change it back to daily digest or normal email.

Note: A member may send reactivation requests to himself/herself
from the Email Preferences section of My Groups.

73 and good luck - your UI-View group moderators

Been using it to promote local stuff in my area.
The problem I am having is that after the event is over getting the icon to stop coming up.


What do I need to do to delete it completely until I need to create a new one?


Seems like clearing out the data doesnt work. When I click on it and tell it to delete it it does but mysteriously comes back.


Just looking for some guidance.


Bob
W8RID

Right Click URLs can be handy. The syntax for QRZ.com changed (I believe) a time or two over the years. The following ones work for me these days. They can be added or edited in a text editor. Just close UI-View first and then edit the "right click URL" section of UIView32.INI.

The last one (APRS101) loads a copy of the APRS101.pdf file. You will need to edit the path to where it is stored on your hard drive.

[RIGHT_CLICK_URLS]
&www.findu.com="
APRS.FI="
RAW="
Messages="
APRS.LINK="
Q&RZ.COM="
FCC="
HAMDATA="
APRS101="file:///C:/Users/UserName/Downloads/Radio-Manuals/APRS/APRS101.PDF"

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

Andy G0MNI wrote...

after reviewing all the options it starts working...

It would have been nice to know what stopped it from
displaying stations, but glad to hear that it's all
working OK again!

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

The TFcard is nearly empty, the stations dont show up on the station list, exclude/include is turned off and after reviewing all the options it starts working, will have to keep my eye on it
Thanks for your help
73s Andy G0MNI

Andy G0MNI wrote...

due to memory on the 1010 I have it stored
on a TF card D\Peak Systems\UI-View32\UI-View32.exe

That establishes that it isn't a problem with
it being installed in a "protected" area.

This has been working fine up to yesterday
I haven't altered anything so am at a loss

Presumably the TF card isn't full, but it should
be checked.

Is the exclude/include list enabled? If so, do
you spot anything in there that could prevent
received stations from being displayed? As you
mentioned, you hadn't changed anything, but
something has changed.

Under options, make sure that "show symbols on
on map" is enabled. A control-F5 could have toggled
it. Of course, that would only prevent you from
seeing stations on the map. It wouldn't prevent
you from gating traffic.

I checked and you have a verified connection,
so again that wouldn't prevent you from gating
traffic.

You said the terminal window shows the received
stations. Do they show up in the station list?

I sent an APRS message to you and got ACKed
right away.

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

Hi Keith due to memory on the 1010 I have it stored on a TFcard D\Peak Systems\UI-View32\UI-View32.exe


This has been working fine upto yesterday
I haven't altered anything so am at a loss

Andy G0MNI wrote...

my UI-View setup has just started acting oddly
in that it will digipeat heard stations but won't
display or gate them to the internet I am using
Windows 10

Where do you have UI-View installed... i.e. is it below Program Files or somewhere else like C:\UI-View32 or C:RADIO\UI-VIEW32?

--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"

Hi I my UI-View setup has just started acting oddly in that it will digipeat heard stations but won display or gate them to the internet I am using windows 10 on a Linx 1010 tablet with a Microsat Voyager tnc/radio (all was fine yesterday) (termail shows the RX'd station data) is there any setting that I should be looking at that may cause this behaviour
many Thanks Andy G0MNI

This message is sent to all new members, and to all members
every now and then. It has been revised as bounce reports have
changed a bit.

Any of us could experience no longer receiving email from the
UI-View support list. You might want to print this message and
review it if you stop receiving messages from the UI-View list.

If you stop receiving messages from the UI-View list, suspect
that either...

1) this or some other Yahoo group that you are a member of is
sending email which some spamblocker system regard as spam or
junk mail (quite a lot of these reports since summer 2009).

2) it may be that your email account has filled up with unread
messages or that the account on your mail server has ran out of
storage space. Read or delete the old messages on your mail server.

3) Some MSN or Hotmail accounts, and others such as arrl.net,
qsl.net which are used as a forwarding address from time to time
cannot forward to your primary address. When this hapens, the
Yahoo group receives an error message with something like
"impossible to relay to xxx" and you are then in the "bounced"
list. There are increasing numbers of bounces from some service
providers about messages which are blocked by them for policy
reasons.

4) You or your email provider have set up a challenge-and-response
system for those sending e-mail to you. The moderators will not
send replies to such challenges. You should select another
address for your list membership(s).

Sorry, but we cannot investigate every one of these blockings.
Please be aware that if you haven't received list messages
for some days, and reactivation requests are not reaching
you, or not answered by you, your account at the UI-View
list may be deleted. It may deleted if several bounces occur
in less than a week or two. It will also be deleted if the
bounce report says that your address is invalid, discontinued,
or unknown. Be aware that the bounce can relate to messages
from other lists than the UI-View list if you are a member
of other Yahoo groups.

If your membership is deleted, you will not be able to log
into the Yahoo group. If you try and send email to the group,
it will be rejected. However, you can subscribe again with a
valid and working email account by sending an empty email to
ui-view-subscribe@....

If you are away for some time, you might want to set your
account to temporarily receive only special messages or
even no email at all, but we recommend that still receive
special messages. You can log into the Yahoo group when you
return and change it back to daily digest or normal email.

Note: A member may send reactivation requests to himself/herself
from the Email Preferences section of My Groups.

73 and good luck - your UI-View group moderators

The UI-View Group is very active. Most already do so,
but here are some some guidelines to follow.

1. Civility... this is practiced well by our members!

2. Sign your messages with your name and callsign.

3. Only post messages and responses that are relevant to UI-View.

4. Use plain text for messages sent to the UI-View support list.
When you address some 5000 recipients, you cannot know what their
email readers do with HTML formatted messages. Some will experience
unreadability.

5. IMPORTANT: When replying to a posting (message), kindly delete
all unnecessary text including the trailing text. Only leave the
poster's name, callsign and the time stamp, and the text from
the prior message about which you are commenting, and then trim
the rest. When viewing messages in the Yahoo web based interface,
the command [Up Thread] at the top of the message can be used, and
many email clients can group messages by thread also. Some members
have slow connections or pay for bandwidth. Brevity can often
also improve the clarity of your message. Do not top post... i.e.
do not type your reply above the quoted text.

6. When replying to a post, please decide if your comment should
go to the entire group of about 5000 or directly to the author.
Please think before replying to the group... replies like "I sure
do agree with that" do not add much to the group. Send thoughts
like those directly to the poster please.

7. Postings of sale or swapping of items are not wanted.

8. New members are all moderated for a number of postings. If the
messages follow the guidelines, they are approved and the member
is changed to un-moderated status.

This is a partially moderated list, i.e., only the user's first
messages are moderated, but all messages are monitored after posting.
If an un-moderated posting is found by the moderators to have a
problem, then the poster is changed to moderated status and in
most cases also contacted directly to resolve whatever has caused
the problem.

Actions are taken against those that chronically violate the rules.
The reason for this form of moderation is to block spammers from the
list and it is working well.

9. Do not add disclaimers to your posts that (1) restrict the ability
of other members to use the information you post, (2) claim a copyright
to your post, or (3) to claim any type of "rights" as a consequence of
another member replying to your post either directly to you or to the group.

10. Do not use anti-spam tools like challenge/response; the moderators
will not respond, and since messages to you then will bounce, you most
probably will be removed as a user of the group.

If you use UIVIEW to log the current stations available before the hurricane hits....you will have a great resource to use (and compare with) affected stations after the storm has passed. The difference can indirectly depict power failures, Internet failure, and of course Amateur RF network status by comparing the data logged "before vs. after" the storm.

Hello group,

I'm seeing this error almost daily now...

Run-time error "11"
Division by zero

This causes the program to stop.

OS is XP I know sorry let's not talk about that if possible. Uiview keeps running fine along with other legacy programs.

I'm not sure where to start debugging, it's been running without errors for 10 years or more until recently.

Thanks everyone,

Regards,

Ross kc7rjk

The UI-View Group is very active. Most already do so,
but here are some some guidelines to follow.

1. Civility... this is practiced well by our members!

2. Sign your messages with your name and callsign.

3. Only post messages and responses that are relevant to UI-View.

4. Use plain text for messages sent to the UI-View support list.
When you address some 5000 recipients, you cannot know what their
email readers do with HTML formatted messages. Some will experience
unreadability.

5. IMPORTANT: When replying to a posting (message), kindly delete
all unnecessary text including the trailing text. Only leave the
poster's name, callsign and the time stamp, and the text from
the prior message about which you are commenting, and then trim
the rest. When viewing messages in the Yahoo web based interface,
the command [Up Thread] at the top of the message can be used, and
many email clients can group messages by thread also. Some members
have slow connections or pay for bandwidth. Brevity can often
also improve the clarity of your message. Do not top post... i.e.
do not type your reply above the quoted text.

6. When replying to a post, please decide if your comment should
go to the entire group of about 5000 or directly to the author.
Please think before replying to the group... replies like "I sure
do agree with that" do not add much to the group. Send thoughts
like those directly to the poster please.

7. Postings of sale or swapping of items are not wanted.

8. New members are all moderated for a number of postings. If the
messages follow the guidelines, they are approved and the member
is changed to un-moderated status.

This is a partially moderated list, i.e., only the user's first
messages are moderated, but all messages are monitored after posting.
If an un-moderated posting is found by the moderators to have a
problem, then the poster is changed to moderated status and in
most cases also contacted directly to resolve whatever has caused
the problem.

Actions are taken against those that chronically violate the rules.
The reason for this form of moderation is to block spammers from the
list and it is working well.

9. Do not add disclaimers to your posts that (1) restrict the ability
of other members to use the information you post, (2) claim a copyright
to your post, or (3) to claim any type of "rights" as a consequence of
another member replying to your post either directly to you or to the group.

10. Do not use anti-spam tools like challenge/response; the moderators
will not respond, and since messages to you then will bounce, you most
probably will be removed as a user of the group.

This message is sent to all new members, and to all members
every now and then. It has been revised as bounce reports have
changed a bit.

Any of us could experience no longer receiving email from the
UI-View support list. You might want to print this message and
review it if you stop receiving messages from the UI-View list.

If you stop receiving messages from the UI-View list, suspect
that either...

1) this or some other Yahoo group that you are a member of is
sending email which some spamblocker system regard as spam or
junk mail (quite a lot of these reports since summer 2009).

2) it may be that your email account has filled up with unread
messages or that the account on your mail server has ran out of
storage space. Read or delete the old messages on your mail server.

3) Some MSN or Hotmail accounts, and others such as arrl.net,
qsl.net which are used as a forwarding address from time to time
cannot forward to your primary address. When this hapens, the
Yahoo group receives an error message with something like
"impossible to relay to xxx" and you are then in the "bounced"
list. There are increasing numbers of bounces from some service
providers about messages which are blocked by them for policy
reasons.

4) You or your email provider have set up a challenge-and-response
system for those sending e-mail to you. The moderators will not
send replies to such challenges. You should select another
address for your list membership(s).

Sorry, but we cannot investigate every one of these blockings.
Please be aware that if you haven't received list messages
for some days, and reactivation requests are not reaching
you, or not answered by you, your account at the UI-View
list may be deleted. It may deleted if several bounces occur
in less than a week or two. It will also be deleted if the
bounce report says that your address is invalid, discontinued,
or unknown. Be aware that the bounce can relate to messages
from other lists than the UI-View list if you are a member
of other Yahoo groups.

If your membership is deleted, you will not be able to log
into the Yahoo group. If you try and send email to the group,
it will be rejected. However, you can subscribe again with a
valid and working email account by sending an empty email to
ui-view-subscribe@....

If you are away for some time, you might want to set your
account to temporarily receive only special messages or
even no email at all, but we recommend that still receive
special messages. You can log into the Yahoo group when you
return and change it back to daily digest or normal email.

Note: A member may send reactivation requests to himself/herself
from the Email Preferences section of My Groups.

73 and good luck - your UI-View group moderators

Stephen,
A fine job on experiments with HF APRS. I just completed a 2800 mile road trip to Canada. I wish I had HF mobile but for know it's at the base station only.
I ran 2 meter APRS using an Yaesu 2800 at 40 watts to a quarter wave mag mount on the roof of the GMC Terrain. At the same time I ran the APRS.FI mobile app with the beacon rate set to 6 minutes. The trip up was through Kansas city, Des Moines, Minneapolis, International Falls to Souix Narrows, Ca.. Returning on a more easterly route through Deluth, La Crosse, Davenport, Jefferson City, and Springfield Mo.
To my surprise the 2 meter coverage was almost constant even in very rural areas. The longest gap was 44 miles near Debuque Iowa. The Internet coverage seemed to be a little less. We were using AT&T and had no service in areas where there were plenty of cell towers. The towers must have been for another carrier. It was interesting to watch WA5LUY-9 and WA5LUY-I on the map chasing each other and see who was in the lead.
I would like to thank the many hams in the central US for providing systems that keep this service alive and well.


Wayne
WA5LUY

On 8/28/2018 5:04 PM, Keith VE7GDH ve7gdh@... [ui-view] wrote:

Bill KI4FZT wrote…

I tried to register there and twice it said it could not successfully register my call sign.

Look again. I believe there is an email link for Andy on the page.

--
73 Keith VE7GDH

If you filled your name in as anything other than John W Farnham it will fail. You must register the same name that shows on your license.

Bill KI4FZT wrote…

I tried to register there and twice it said it could not successfully register my call sign.

Look again. I believe there is an email link for Andy on the page.

--
73 Keith VE7GDH
“ I may be lost, but I know exactly where I am!”

The link in the UI-View page to register to enable use of the UI-View software - I followed that link to



I tried to register there and twice it said it could not successfully register my call sign. My call sign is 100% valid, but I can see no place on the above website where I can address them to see why my call sign was rejected.



What gives? How else can I register UI-View?


Bill
KI4FZT

Stephen, You are a rock star of APRS usage and things to make us go Hmmmmm
I wonder??

Thanks for documenting your travels and findings.

KO4L Lloyd

On Wed, Aug 22, 2018 at 2:01 PM, 'Stephen H. Smith' wa8lmf@...
[ui-view] <ui-view@...> wrote:

For many decades now, long-range HF APRS operation has been done almost
exclusively on 30 meters. It will beam APRS posits over long distances
(2000
miles/3000 Km or more), but it does have a problem. At 10 MHz, there is
little to no NVIS (high angle) propagation. As a result, 30 meters has a
skip
zone of 250-300 miles (400-500 Km) most of the time. In other words, you
normally DON'T HEAR stations closer than this on 30M.

For some time now, I have felt that NVIS (Near-Vertical Incidence Skywave)
propagation (high take-off angles that will bounce signals back to earth
close
to the originating station (but on the other sides of mountains) would be
useful in large areas of the Great Basin/inter-mountain west. During
numerous
trips between Los Angeles and the mid-west over the past several decades,
I
have frequently noted the difficulty in being heard out of deep canyons
and
from secondary roads on the other side of mountain ridge lines from major
Interstate highways.

Propagation on 60 meters is almost the exact opposite of 30 meters in this
respect. 60 meters does NVIS propagation very well, and will provide
coverage
from 0 to 300 miles (500 Km) most of the day quite consistently. This
summer,
I tested the potential of 60 for APRS applications on two road trips. The
first was from my QTH in central Michigan (East Lansing) to Rice Lake,
Wisconsin about 400 miles (640 Km) to the northwest. The other was the
annual 1100 mile (1700 Km) trek to the Evergreen (Colorado) Jazz Festival.

The mobile setup was a Yaesu FT-891 transceiver running into a MFJ
monoband
whip for 60M (that appears to be a rebranded HamStick) mounted on a
split-ball
body mount on the left-rear part of the body of my 2006 Jetta TDI. The
transmit
power was about 15 watts. [I could have run the FT-891 at a full 100
watts
output.. However, since the 60-meter channels are shared ham/non-ham use,
I
wanted to keep the ERP low enough that others could talk over my beacons
if
necessary.]

The APRS application running on the mobile Panasonic Toughbook was G4HYG's
"APRS Messenger". This soundcard modem application can function as a
mobile
tracker, beaconing alternately on 300-baud classic AX.25 HF packet, and on
MFSK16. Messenger's MFSK mode actually sends the payload of an APRS-style
AX.25
packet, including the packet-style path headers and checksum at the end,
over
MFSK16. For an additional comparison, I had a TinyTrack 3 set for HF
300-baud mode and MIc-E format to evaluate the relative effectiveness of
the
longer plain-text posits sent by Messenger and the shorter Mic-e packets
sent
by the TinyTrack. The callsigns were WA8LMF-6 for the AX.25 mode,
WA8LMF-66
for the MFSK mode and WA8LMF-2 for the TinyTrack Mic-E beacons. [I was
also
beaconing WA8LMF (no SSID) on conventional 144.39 two-meters APRS with my
Kenwood D700.]

The fixed station/igate at my East Lansing QTH was a Yaesu FT-857D
connected to
a 105' (32 meter) center-fed dipole fed by 450-ohm ladder line and an Icom
AH-2
auto-coupler. The software was identical to the mobile (APRS Messenger and
UIview) running on an Acer E3-111 "netbook" mini-laptop that runs Win 7 on
a
dual-core Pentium 4. [I like these mini-laptops for APRS applications,
where
you leave computers running 24/7 for weeks at a time, because they consume
only
9-10 watts.] I also had the TightVNC remote control program running on
the
Acer so I could view the machine's screen and and tweak settings remotely
while
on the road. The beacons successfully found their way to findu.com and
APRS.fi, courtesy of my igate.

These tests took place on US "Channel 5" of the fixed-frequency
channelized
60-meter band. This is 5403.5 KHz USB. Partly because it is the shortest
wavelength channel on 60M so the mobile whip is the "least inefficient".
And
partly because by informal convention, "Channel 5" is the "data channel"
on
60. [There is no segregation between voice and non-voice modes on 60 as
there
is on the other HF bands. You can legally use any mode on any of the 5
channels.]

__________________________________________________________

The results more than met my expectations. The trip to Rice Lake, WI was a
loop
- outbound "over the top" of Lake Michigan via Michigan's Upper Peninsula,
while the return was via Madison WI and Chicago around the "bottom" of
Lake
Michigan. The 60-meter coverage was essentially continuous. In remoter
parts
of the Michigan UP and north-eastern Wisconsin, where two meters heard
nothing,
the 60-meter posits just kept coming in.

Another variable comes into play. Propagation on 60M does change with the
time
of day and day vs night. On the outbound trip, the shortest hops from the
mobile to the igate were in daylight, starting at about 0800 EDT (local
time).
I arrived in Rice Lake (greatest distance) at about 2100 EDT; i.e. just
after
dusk. On the return trip, exactly the opposite with the longest hops in
the
AM daylight, and the shorter hops well after after dark as I approached
home.
The closer hops (under about 150 miles/240 Km) started failing on the
return
trip because it was now well after sunset; i.e. 2200 - 2400 hrs EDT.

The trip to Colorado was perhaps more interesting because 1) It was a
much
greater distance from home and 2) The route was much closer to being a
constant
latitude. [Since HF propagation is the result of the upper atmosphere
being
ionized by solar radiation and particles, and because those particles are
deflected by the earth's magnetic field, HF propagation effects are quite
sensitive to latitude north or south. By driving a nearly straight
east-west
line, one keeps at least one variable in the test more-or-less constant.]
After driving from central Michigan to Chicago and joining I-80, the rest
of
the trip was almost due west along I-80 to the Colorado border.

The 1100 mile trip from MI to Denver takes two days. The mid-point of the
trip
is at the west side of Des Moines, Iowa, where I always spend the first
night
about 550 miles (880 Km) from home. All along the route, I would
periodically
stop to connect to WiFi at gas stations and fast-food joints to check my
own
UI-Webserver via VNC and APRS.fi to see if I was reaching my solitary
60-meter
igate in Michigan. [The ultimate convenience is in Iowa,, where every
rest
area on the Interstate has free WiFi beamed into the parking lot from a 9'
fiberglass 2.4 GHz collinear whip on top of the building. You can easily
get
WiFi from a laptop inside your parked car.]

I had expected that the signal would start dropping out at 300-400 miles (
500-650 Km) from home, but I had constant coverage on 60M for the entire
day's
drive.. To my surprise, the signals were still booming into my Michigan
igate
when I arrived in Des Moines at about 1900 hrs EDT. After check-in, I
left the
gear running in the parked car, while I played with the Internet in my
motel
room. [I have 110 AH of sealed AGM batteries in the trunk of the car,
isolated
from the starting battery, so I can safely leave electronics on for many
hours
after engine-off.] The Michigan igate's reception started failing about
2300
hrs EDT. (At this point I was in US Central time where it was 2200 hrs
local.)
Most striking, I noticed the AX.25 beacons starting to fail about 45
minutes
earlier than the MFSK16 ones. It dramatically demonstrated the enormous
superiority (10-15 dB advantage) of MFSK16 over classic two-tone FSK
300-baud
packet under weak-signal conditions.

I had assumed that I would be out of range of my home station on 60 meters
well
before the end of the first day, and had intended to switch the mobile
setup to
30 meters that evening, for the rest of the trip. (I had an identical
HamStick
for 30 meters stowed in the car.) Instead, I kept the setup on 60 meters
the
morning of the second day. When I departed after breakfast at 0900 hrs
EDT
(0800 local), no beacons were being heard by my Michigan igate. By the
time I
stopped at another Iowa WiFi rest stop about an hour down the road, in the
Avoca, Iowa area, the MFSK beacons were coming in again. By the time I
arrived
in the Omaha, Nebraska area, the AX.25 FSK beacons were coming in also.
Both
formats continued to be received until I reached the Lincoln, NE area,
about an
hour west of Omaha. At this point, I did switch to 30 meters.

On the return trip, the last night on the road was in Avoca, Iowa where I
switched from 30 meters back to 60. Again, I saw no evidence of my beacons
reaching my igate in the morning until about 0090 hrs local (1000 hrs
EDT). .
Again, the MFSK16 beacons "opened the band" with the AX.25 ones starting
to
appear about an hour later.

_________________________________________________________

The final conclusions are: 1) 60 meters CAN provide quite consistent
APRS
coverage from 0 to 400 miles (640 Km) or so. 2) The MFSK mode has a
huge
advantage over classic 300-baud FSK, providing nearly two more hours a day
of
usable progation. Sometime this fall, I will be making a trip EASTWARD
on
I-80 crossing the Appalachian Mountains to Philadelphia. This will be an
opportunity to try NVIS propagation out of some smallish valleys in the
eastern
mountains. Ultimately, I would like to try absolutely maximizing the
NVIS
receive performance by building a turnstile antenna consisting of two
60-meter
dipoles crossed, supported as inverted-Vs on the same mast, and fed in
quadrature with coax phasing lines. Stay tuned!

__________________________________________________________

Stephen H. Smith wa8lmf (at) aol.com
Skype: WA8LMF
EchoLink: Node # 14400 [Think bottom of the 2-meter band]
Home Page:

Live Off-The-Air APRS Activity Maps
<>

Long-Range APRS on 30 Meters HF
<>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]