[MNAPRS] How do I connect using UI-View?

Doug Reed n0nas at amsat.org
Tue Aug 22 02:50:23 UTC 2006


Hi Jerry.

Dean's answer is short and sweet. Mine are seldom that short.<g>

You should be using WIDE2-2 (in the metro) or WIDE3-3 (out-state) at 
home for your unproto path. That supposes that you are able to hit the 
main digi sites reliably. A little more likely scenario for the mobile 
is to use an unproto path of:
    WIDE1-1,WIDE2-2

WIDE1-1 is the new replacement for RELAY. All home stations should use 
an alias of WIDE1-1 with DIGI ON and with call sign substitution 
enabled. Even a very old TNC should be able to function properly for 
APRS if you set DIGI ON and MYALIAS WIDE1-1. Standard TNC operation will 
then digipeat anytime it hears WIDE1-1 as the incoming call sign, and 
when it sends the packet it will put the call sign of the home station 
(MYCALL) in the list the way it should be. This means we'll be able to 
trace where the packets came from and the path they followed to get here.

The main WIDE digipeaters will hear the packet retransmitted from the 
home station or direct from the mobile and retransmit the packet. The 
WIDE will also put its own call sign in the packet. This is the primary 
mechanism for eliminating duplicate retransmissions of packets in the 
local area.

You can decide if you want two or three repeats from the WIDE digi's by 
choosing WIDE2-2 or WIDE3-3 for your unproto path. Since most areas with 
APRS interest also have a local station who gateways received beacons to 
FINDU.COM, there is no significant advantage to anything greater than 
WIDE2-2. You can use the example above or change to something like:
     WIDE1-1,WIDE2-1

The above option looks a little strange but allows either a home station 
or a WIDE to retransmit the packet once, followed by the next WIDE 
retransmitting it once more. Since each WIDE coverage area should be 
around 60 miles to a home station, you should get 60-120 mile radius 
coverage this way. Extending the WIDE count is actively discouraged 
because it "busies out" the channel over a wide area with duplicate 
packets. If people that far away need to know your location, show them 
how to use findu.com instead. Findu is more reliable too.

The first term in the unproto address is a code that tells what kind of 
software or hardware you are using for APRS. UIView has its own code and 
probably defaults to it. It is probably mentioned in the doc files what 
it should be. I don't remember if you have to set it separately or not.

There was one Minnesota web site that had a bit of APRS stuff but I 
don't remember the URL. The MNAPRS.COM web site went down 5 years ago 
and was lost. I've recovered part of the data but never taken the time 
to put it back together. We do host the mnaprs remailer on the 
twinslan.org site but that is about all. Another gentleman put up the 
mnaprs.org web site but it seems to be down right now.

Good luck with UIView. I've used it once or twice and the best thing 
about it is the ability to import external maps and use them. Those maps 
are something else that would be useful to have on a web site. But the 
best option is to read the maps directly from a map CDROM. Then you have 
everything and anything you might need....

73, Doug Reed, N0NAS.

-----Original Message-----
From: mnaprs-bounces at lists.twinslan.org
[mailto:mnaprs-bounces at lists.twinslan.org]On Behalf Of Jerry W
Sent: Monday, August 21, 2006 1:46 PM
To: MNAPRS
Subject: [MNAPRS] How do I connect using UI-View?


I have UI-View and have used that for ISS and PCSAT digipeaters.  What
do I put in the box "unproto address" for the twin city area
digipeaters?

Are there any web sites for Minnesota APRS, I had
http://www.mnaprs.org/ but that seems to be off?

TIA,

Jerry W - K0HZI
_______________________________________________
MNAPRS mailing list
Post msgs to MNAPRS at lists.twinslan.org
Sub/Unsub at http://lists.twinslan.org/twinslan/listinfo/mnaprs



More information about the MNAPRS mailing list