No subject
Sun Aug 23 09:03:27 EST 2009
http://www.aprs.pl/europe.htm
144.800 MHz is the APRS Network Frequency in Europe
WIDEn-n for base stations and WIDE1-1,WIDEn-n for mobile stations are the
most recommended packet paths for APRS activity in Europe. Keep n number in
WIDEn-n as low as possible, i.e. WIDE2-2 or WIDE3-3. Then you do not become
the source of QRM for the network.
Visiting Poland you can use in your mobile the European standard
packet path WIDE1-1,WIDEn-n. In some areas n is restricted to n≤3 or even
n≤2. Moreover, in the entire country you can use WIDE1-1,SPn-n which is not
restricted to n value.
Switching WIDEn-n to be fully traceable path is in the progress.
Check the dynamic coverage map with tracks sent on RF in the last 31
days. Red points are sent on the air, yellow ones came directly to the
server.
Another from Italy was also suggestig the same as above.
Mike, VK2INT.
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 23 Oct 2006 11:57:44 -0400
> From: "Robert Bruninga" <bruninga at usna.edu>
> Subject: Re: [OZAPRS] European v US new paradigm
> To: "'VK / ZL APRS Users'" <ozaprs at aprs.net.au>
> Message-ID: <200610231558.ALR43377 at usna.edu>
> Content-Type: text/plain; charset="us-ascii"
>
>> digis will accept only paths set to the following;
>>
>> RELAY,WIDE
>> RELAY,WIDE2-2
>> WIDE1-1,WIDE2-2
>>
>> Using the EU version of the new paradigm will mean
>> that 90% of stations will not have to do anything to
>> their Tracker and Home station settings. This
>> will save a lot of confusion for Operators.
>
> A very minor point to followup on that...
>
> Since one of the purposes of the New-N paradigm was to eliminate
> confusion, retaining RELAY and WIDE and WIDEn-N seems like it
> retains the "confusion" for 90% of the users since they "don't
> have to change" and does nothing to get users simplified up to
> the new simplified approach.
>
> I fully understand a desire to be backwards compatible to
> existing users that use WIDE by iteself, but then if you
> continue to support it, then they will continue to use it and so
> your docs, your network, and your future system will also still
> use it. So the flip side is to just go cold turkey and make the
> change and then let the WIDE users also change. And if you are
> making these changes and getting everyone ton consider the
> future, why not drop RELAY too so that if someone does want to
> use a KPC-3 TNC down there, that it wont cause the RELAY dupe
> problem.
>
> But again, please dissregard this kibitzing from afar, since
> your network is smaller and more limited. But the above was
> some of the discussion we had back here in the USA when we all
> decided to go with the New-N system...
>
> Good luck!
> Bob, WB4APR
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Ozaprs mailing list
> Ozaprs at aprs.net.au
> http://aprs.net.au/mailman/listinfo/ozaprs
>
>
> End of Ozaprs Digest, Vol 14, Issue 20
> **************************************
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.408 / Virus Database: 268.13.11/493 - Release Date:
> 23/10/2006
>
>
_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs
------=_NextPart_000_BB90_01C8BF68.3E113C00
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dutf-8">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
08.00.0681.000">
<TITLE>Re: [OZAPRS] Ozaprs Digest, Vol 14, Issue 20</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>I would tend to agree with our American friend on =
changing to the New-N </FONT>
<BR><FONT SIZE=3D2>paradigm . A "European new n-n paradigm" =
Google search came up with these </FONT>
<BR><FONT SIZE=3D2>examples of suggested EU path settings.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>From Norway,</FONT>
</P>
<P><FONT SIZE=3D2><A =
HREF=3D"http://tf8bk.famutne.net/aprs_tech.html#gen">http://tf8bk.famutne=
.net/aprs_tech.html#gen</A></FONT>
<BR><FONT SIZE=3D2>General notes on new APRS setup</FONT>
</P>
<P><FONT SIZE=3D2>Prior to continuing with more detailed instructions on =
different setups, I </FONT>
<BR><FONT SIZE=3D2>just want to mention that there has been some =
discussions lately on what is </FONT>
<BR><FONT SIZE=3D2>the best setup for APRS. After extensive =
communication with both Bob </FONT>
<BR><FONT SIZE=3D2>Bruninga (WB4APR) and Sysops within Norway, we are =
now left with a </FONT>
<BR><FONT SIZE=3D2>recommended common structure for APRS setup:</FONT>
</P>
<P><FONT SIZE=3D2> a.. WIDE3-3 for relay via stand-alone =
Digipeaters</FONT>
<BR><FONT SIZE=3D2> b.. WIDE1-1 for relay via Fill-in Digis</FONT>
<BR><FONT SIZE=3D2> c.. NORn-N (as SSn-N) which may be used =
nationally for relay via </FONT>
<BR><FONT SIZE=3D2>stand-alone Digipeaters</FONT>
<BR><FONT SIZE=3D2> d.. This also means that TRACEn-N is no longer =
available for use</FONT>
<BR><FONT SIZE=3D2>Some may wonder what happened to RELAY after general =
implementation of </FONT>
<BR><FONT SIZE=3D2>WIDEn-N? Well, you will actually benefit from not =
using RELAY, as any </FONT>
<BR><FONT SIZE=3D2>Digipeater type will immediately recognize WIDE1-1 in =
the future, both </FONT>
<BR><FONT SIZE=3D2>Fill-in and stand-alone Digipeaters. In this way, you =
as a user need only to </FONT>
<BR><FONT SIZE=3D2>remember one single parameter for all kinds of relay, =
namely WIDEn-N.</FONT>
</P>
<P><FONT SIZE=3D2>This solution demands correct contents of two unique =
Digipeater parameters </FONT>
<BR><FONT SIZE=3D2>(UIFLOOD and UITRACE) in order for us to obtain the =
expected effect, namely </FONT>
<BR><FONT SIZE=3D2>reduced traffic strain on the frequency (traffic =
volume and unnecessary </FONT>
<BR><FONT SIZE=3D2>QRM), without loss of data.</FONT>
</P>
<P><FONT =
SIZE=3D2>----------------------------------------------------------------=
-------------------------------------------------------------</FONT></P>
<P><FONT SIZE=3D2>From Poland</FONT>
</P>
<P><FONT SIZE=3D2><A =
HREF=3D"http://www.aprs.pl/europe.htm">http://www.aprs.pl/europe.htm</A><=
/FONT>
</P>
<P><FONT SIZE=3D2>144.800 MHz is the APRS Network Frequency in =
Europe</FONT>
</P>
<P><FONT SIZE=3D2>WIDEn-n for base stations and WIDE1-1,WIDEn-n for =
mobile stations are the </FONT>
<BR><FONT SIZE=3D2>most recommended packet paths for APRS activity in =
Europe. Keep n number in </FONT>
<BR><FONT SIZE=3D2>WIDEn-n as low as possible, i.e. WIDE2-2 or WIDE3-3. =
Then you do not become </FONT>
<BR><FONT SIZE=3D2>the source of QRM for the network.</FONT>
</P>
<P><FONT SIZE=3D2> Visiting Poland you can =
use in your mobile the European standard </FONT>
<BR>packet path WIDE1-1,WIDEn-n. In some areas n is restricted to =
n=E2=89=A43 or even=20
<BR>n=E2=89=A42. Moreover, in the entire country you can use =
WIDE1-1,SPn-n which is not=20
<BR><FONT SIZE=3D2>restricted to n value.</FONT>
</P>
<P><FONT SIZE=3D2> Switching WIDEn-n to be =
fully traceable path is in the progress.</FONT>
</P>
<P><FONT SIZE=3D2> Check the dynamic =
coverage map with tracks sent on RF in the last 31 </FONT>
<BR><FONT SIZE=3D2>days. Red points are sent on the air, yellow ones =
came directly to the </FONT>
<BR><FONT SIZE=3D2>server.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Another from Italy was also suggestig the same as =
above.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Mike, VK2INT.</FONT>
</P>
<P><FONT SIZE=3D2>> =
----------------------------------------------------------------------</F=
ONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Message: 1</FONT>
<BR><FONT SIZE=3D2>> Date: Mon, 23 Oct 2006 11:57:44 -0400</FONT>
<BR><FONT SIZE=3D2>> From: "Robert Bruninga" =
<bruninga at usna.edu></FONT>
<BR><FONT SIZE=3D2>> Subject: Re: [OZAPRS] European v US new =
paradigm</FONT>
<BR><FONT SIZE=3D2>> To: "'VK / ZL APRS Users'" =
<ozaprs at aprs.net.au></FONT>
<BR><FONT SIZE=3D2>> Message-ID: =
<200610231558.ALR43377 at usna.edu></FONT>
<BR><FONT SIZE=3D2>> Content-Type: text/plain; =
charset=3D"us-ascii"</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>>> digis will accept only paths set to the =
following;</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>> RELAY,WIDE</FONT>
<BR><FONT SIZE=3D2>>> RELAY,WIDE2-2</FONT>
<BR><FONT SIZE=3D2>>> WIDE1-1,WIDE2-2</FONT>
<BR><FONT SIZE=3D2>>></FONT>
<BR><FONT SIZE=3D2>>> Using the EU version of the new paradigm =
will mean</FONT>
<BR><FONT SIZE=3D2>>> that 90% of stations will not have to do =
anything to</FONT>
<BR><FONT SIZE=3D2>>> their Tracker and Home station settings. =
This</FONT>
<BR><FONT SIZE=3D2>>> will save a lot of confusion for =
Operators.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> A very minor point to followup on that...</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Since one of the purposes of the New-N paradigm =
was to eliminate</FONT>
<BR><FONT SIZE=3D2>> confusion, retaining RELAY and WIDE and WIDEn-N =
seems like it</FONT>
<BR><FONT SIZE=3D2>> retains the "confusion" for 90% of the =
users since they "don't</FONT>
<BR><FONT SIZE=3D2>> have to change" and does nothing to get =
users simplified up to</FONT>
<BR><FONT SIZE=3D2>> the new simplified approach.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> I fully understand a desire to be backwards =
compatible to</FONT>
<BR><FONT SIZE=3D2>> existing users that use WIDE by iteself, but =
then if you</FONT>
<BR><FONT SIZE=3D2>> continue to support it, then they will continue =
to use it and so</FONT>
<BR><FONT SIZE=3D2>> your docs, your network, and your future system =
will also still</FONT>
<BR><FONT SIZE=3D2>> use it. So the flip side is to just go =
cold turkey and make the</FONT>
<BR><FONT SIZE=3D2>> change and then let the WIDE users also =
change. And if you are</FONT>
<BR><FONT SIZE=3D2>> making these changes and getting everyone ton =
consider the</FONT>
<BR><FONT SIZE=3D2>> future, why not drop RELAY too so that if =
someone does want to</FONT>
<BR><FONT SIZE=3D2>> use a KPC-3 TNC down there, that it wont cause =
the RELAY dupe</FONT>
<BR><FONT SIZE=3D2>> problem.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> But again, please dissregard this kibitzing from =
afar, since</FONT>
<BR><FONT SIZE=3D2>> your network is smaller and more limited. =
But the above was</FONT>
<BR><FONT SIZE=3D2>> some of the discussion we had back here in the =
USA when we all</FONT>
<BR><FONT SIZE=3D2>> decided to go with the New-N system...</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Good luck!</FONT>
<BR><FONT SIZE=3D2>> Bob, WB4APR</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> ------------------------------</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>> Ozaprs mailing list</FONT>
<BR><FONT SIZE=3D2>> Ozaprs at aprs.net.au</FONT>
<BR><FONT SIZE=3D2>> <A =
HREF=3D"http://aprs.net.au/mailman/listinfo/ozaprs">http://aprs.net.au/ma=
ilman/listinfo/ozaprs</A></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> End of Ozaprs Digest, Vol 14, Issue 20</FONT>
<BR><FONT SIZE=3D2>> **************************************</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> -- </FONT>
<BR><FONT SIZE=3D2>> No virus found in this incoming message.</FONT>
<BR><FONT SIZE=3D2>> Checked by AVG Free Edition.</FONT>
<BR><FONT SIZE=3D2>> Version: 7.1.408 / Virus Database: 268.13.11/493 =
- Release Date: </FONT>
<BR><FONT SIZE=3D2>> 23/10/2006</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> </FONT>
</P>
<P><FONT SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Ozaprs mailing list</FONT>
<BR><FONT SIZE=3D2>Ozaprs at aprs.net.au</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://aprs.net.au/mailman/listinfo/ozaprs">http://aprs.net.au/ma=
ilman/listinfo/ozaprs</A></FONT>
</P>
</BODY>
</HTML>
------=_NextPart_000_BB90_01C8BF68.3E113C00--
More information about the Ozaprs
mailing list