http://info.aprs.net/api.php?action=feedcontributions&user=CapKE6AFE&feedformat=atomAPRSWiki - User contributions [en]2013-05-26T03:50:20ZUser contributionsMediaWiki 1.19.2http://info.aprs.net/index.php?title=PathsPaths2011-07-22T16:33:58Z<p>CapKE6AFE: /* '''''MOBILE''''' Stations in North America (VHF) */</p>
<hr />
<div>Stub for recommendations on setting digipaths (aka unproto paths)<br />
<br />
IMPORTANT : We need information on recommended settings for all regions, and links to understanding new paradigm information. <br />
RECOMMENDATION: Most of this regional info should be transferred to the new [[RegionalPages|regional info pages]] and content added there about local protocols. <br />
<br />
== Recommended Path Settings for: ==<br />
<br />
=== '''''MOBILE''''' Stations in North America (VHF) ===<br />
* WIDE1-1 :A lite option, especially if digipeater stations in your area are within earshot of one or more IGate stations. If dots on Internet maps are your target, WIDE1-1 is the courteous choice. CREDIT: [[NorCal APRS Regional Info]]<br />
* WIDE1-1,WIDE2-1 :Two hops in all directions with potential to use fill-in digis. Best routine path for mobile or portable use in most all areas.<br />
* WIDE1-1,WIDE2-2 :''Three hops'' in all directions, with potential to use fill-in digis. Please do not use this path unless you can verify that there are several intermediate digis required ''(and available)'' to traverse long distances to a mountaintop digi, or I-gate. Adding hops will not be beneficial in congested areas.<br />
<br />
There are methods and paths for special events, emergencies, and statewide messages. Please see information specific to your region.<br />
<br />
=== '''''FIXED''''' Stations in North America (VHF) ===<br />
<br />
* WIDE2-1 :One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 :Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 :Three hops in all directions... only for very sparsely populated areas far from any mountain digis or cities. Many digis in populated areas will only give one hop to paths of WIDE3-3 (and broader).<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete.<br />
<br />
For details and explanation, visit Bob WB4APR's [http://www.aprs.org/fix14439.html WIDEn-N Paradigm] web page.<br />
<br />
=== '''''HF''''' Stations, max routine===<br />
* GATE, WIDE2-1: Recommended for HF APRS, **DO NOT USE** on VHF.<br />
<br />
You can see a bad example of path overkill [[PathOverkill|here]].<br />
<br />
=== '''''Mobile''''' Stations in Australia (VK) ===<br />
<br />
* For VK8 use RELAY,WIDE2-2<br />
* For VK1, VK2, VK3, VK4, VK5 & VK6 use WIDE1-1,WIDE2-1<br />
* For VK7 use WIDE1-1,WIDE2-2 TASn-n also supported.<br />
<br />
* On HF use GATE, WIDE2-1 **DO NOT USE** on VHF.<br />
* On APRS Satellites use ARISS,SGATE,WIDE<br />
<br />
Visit the appropriate state's web page at the [http://www.aprs.net.au/ Australian APRS site] for further details.<br />
<br />
=== Republic of Ireland ===<br />
<br />
* WIDE1-1, WIDE2-2 for Mobile Stations. Three hops with support for Fill-in digis<br />
* WIDE2-2 for Base Stations. Two hops no support for Fill-in Digis. Packets should make it to an Igate.<br />
<br />
If you want to discuss/or disagree with the settings/want to try something else, Please contact either EI7IG or EI8JA.<br />
See [http://www.ei7ig.org/aprs.html http://www.ei7ig.org/aprs.html]<br />
<br />
=== UK/EU === <br />
Home Stations (UI-View Style)<br />
* APRS,WIDE2-2<br />
Mobiles (Packet Path)<br />
* WIDE1-1,WIDE2-1<br />
IGATEs (UI-View Style)<br />
* APRS,WIDE2-1 <br />
<br />
[http://www.apritch.myby.co.uk/uiview_newn-n.htm http://www.apritch.myby.co.uk/uiview_newn-n.htm]<br />
<br />
=== New Zealand ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
http://zlhams.wikidot.com/aprsrecommendations:recommendations<br />
<br />
=== Norway ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
* WIDE2-1 : Igates<br />
<br />
Bruker man UI-View:<br />
* APRS,WIDE1-1,WIDE2-2 :Mobile trackers<br />
* APRS,WIDE3-3 :Home stations<br />
<br />
[http://www.aprsla.net/aprs_tech.html#unproto http://www.aprsla.net/aprs_tech.html#unproto]<br />
<br />
=== Poland ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://www.aprs.pl/europe.htm http://www.aprs.pl/europe.htm]<br />
<br />
=== Luxembourg ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE4-4 :Home stations<br />
<br />
[http://www.rlx.lu/lx_aprs.htm http://www.rlx.lu/lx_aprs.htm]<br />
<br />
=== Czech Republic ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.hamradio.cz/aprs_new/index.php http://www.hamradio.cz]<br />
<br />
=== Germany ===<br />
<br />
* WIDE1-1,WIDE2-1 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm]<br />
<br />
=== JAPAN ===<br />
<br />
* WIDE1-1 or SSn-N :MOBILE Stations <br />
* No Path :FIXED Stations<br />
<br />
JAPRSX http://japrsx.com for further details.<br />
<br />
=== South Africa (VHF) ===<br />
<br />
* WIDE1-1,WIDE2-2 :Three hops with potential to use fill-in digis.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=IntroductionsIntroductions2011-01-23T21:39:34Z<p>CapKE6AFE: /* General */</p>
<hr />
<div>==Introductions, gentle or otherwise...==<br />
<br />
Everybody needs to get started in APRS, and different people want to start from different places. If you have written or found a good introductory article, capture it here for others to use.<br />
<br />
==General==<br />
*[[WhyAndHow|Getting Started with APRS - Why and How (by K6DBG)]]<br />
*[http://wetnet.net/~we7u/GETTING_STARTED_WITH_APRS_07041.pdf Brochure (PDF format): "GETTING_STARTED_WITH_APRS, Rev 4/1/07"]<br />
*[http://wiki.ham.fi/Aprs.fi_Troubleshooting#My_position_is_not_showing_up_on_aprs.fi My position is not showing up on aprs.fi]<br />
<br />
==Getting Into Details==<br />
*[[SymbolsAndSSIDs|Setting Symbols and SSID's]]<br />
*[[ControlOperator|Does a control operator need to "babysit" each tracker?]]<br />
*[[TacticalCallsigns|Use of Tactical Callsigns for APRS Trackers]]<br />
<br />
==SAR-Related==<br />
*[http://wetnet.net/~we7u/WASAR_2007.ppt WASAR 2007 Presentation: "Radio Tracking Your SAR Teams"]<br />
*[http://wetnet.net/~we7u/2007_SAR_Conf_Handout.pdf WASAR 2007 Handout: "Radio Tracking Your SAR Teams"]<br />
*[http://www.phillylinux.org/slides/aprs-20051003/ Where's that task team? Position mapping with xastir and amateur radio for Search and Rescue]</div>CapKE6AFEhttp://info.aprs.net/index.php?title=PathsPaths2009-02-01T21:39:26Z<p>CapKE6AFE: /* '''''FIXED''''' Stations in North America (VHF) */</p>
<hr />
<div>Stub for recommendations on setting digipaths (aka unproto paths)<br />
<br />
IMPORTANT : We need information on recommended settings for all regions, and links to understanding new paradigm information. <br />
RECOMMENDATION: Most of this regional info should be transferred to the new [[RegionalPages|regional info pages]] and content added there about local protocols. <br />
<br />
== Recommended Path Settings for: ==<br />
<br />
=== '''''MOBILE''''' Stations in North America (VHF) ===<br />
<br />
* WIDE1-1,WIDE2-1 :Two hops in all directions with potential to use fill-in digis. Best path for mobile use in most all areas.<br />
* WIDE1-1,WIDE2-2 :Three hops with potential to use fill-in digis. Use only if truly needed while very far from any mountain digis or cities.<br />
<br />
=== '''''FIXED''''' Stations in North America (VHF) ===<br />
<br />
* WIDE2-1 :One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 :Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 :Three hops in all directions... only for very sparsely populated areas far from any mountain digis or cities. Many digis in populated areas will only give one hop to paths of WIDE3-3 (and broader).<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete.<br />
<br />
For details and explanation, visit Bob WB4APR's [http://www.aprs.org/fix14439.html WIDEn-N Paradigm] web page.<br />
<br />
=== '''''HF''''' Stations, max routine===<br />
* GATE, WIDE2-1: Recommended for HF APRS, **DO NOT USE** on VHF.<br />
<br />
You can see a bad example of path overkill [[PathOverkill|here]].<br />
<br />
=== '''''Mobile''''' Stations in Australia (VK) ===<br />
<br />
* For VK6 & VK8 use RELAY,WIDE2-2<br />
* For VK1, VK2, VK3, VK4 & VK5 use WIDE1-1,WIDE2-1<br />
* For VK7 use WIDE1-1,WIDE2-2 TASn-n also supported.<br />
<br />
* On HF use GATE, WIDE2-1 **DO NOT USE** on VHF.<br />
* On APRS Satellites use ARISS,SGATE,WIDE<br />
<br />
Visit the appropriate state's web page at the [http://www.aprs.net.au/ Australian APRS site] for further details.<br />
<br />
=== Ireland (EI) ===<br />
<br />
* WIDE1-1, WIDE2-2 for Mobile Stations. Two hops with support for Fill-in digis<br />
* WIDE2-2 for Base Stations. Two hops no support for Fill-in Digis. Packets should make it to an Igate.<br />
<br />
If you want to discuss/or disagree with the settings/want to try something else, Please contact either EI7IG or EI8JA.<br />
<br />
=== UK/EU === <br />
Home Stations (UI-View Style)<br />
* APRS,WIDE2-2<br />
Mobiles (Packet Path)<br />
* WIDE1-1,WIDE2-1<br />
IGATEs (UI-View Style)<br />
* APRS,WIDE2-1 <br />
<br />
[http://www.apritch.myby.co.uk/uiview_newn-n.htm http://www.apritch.myby.co.uk/uiview_newn-n.htm]<br />
<br />
=== New Zealand ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
=== Norway ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://tf8bk.famutne.net/aprs_tech.html#unproto http://tf8bk.famutne.net/aprs_tech.html#unproto]<br />
<br />
=== Poland ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://www.aprs.pl/europe.htm http://www.aprs.pl/europe.htm]<br />
<br />
=== Luxembourg ===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE4-4 :Home stations<br />
<br />
[http://www.rlx.lu/lx_aprs.htm http://www.rlx.lu/lx_aprs.htm]<br />
<br />
=== Germany ===<br />
<br />
* WIDE1-1,WIDE2-1 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm]</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:54:57Z<p>CapKE6AFE: /* Summary Information */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390 MHz<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, parts of the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc.<br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic, reducing throughput. Exceptions to this may be in urban canyons, pocket valleys, or remote areas along the coast where it can be demonstrated that a mobile station's packets do not otherwise reach the network. A special event occurring in such remote "shaded areas" may benefit from a temporary "fill-in or event" digi (which only responds to packets addressed via WIDE1-1 or it's own callsign) sited overlooking the operating area for the event duration. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed routinely, you could join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to consider establishing ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets heard on RF to the Internet via [[InternetSystem|APRS-IS]] but do not add duplicate packets to the VHF airwaves as another digi could.<br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this, high-level network "S overlay" digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region. Fill-in digis do not respond to packets addressed via NCA1-1 so a mobile station ''could'' use a path of WIDE1-1,NCA1-1 instead of the routine WIDE1-1,WIDE2-1 mobile path.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. Not normally required; use is discouraged.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed, non-moving''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* ''NCA1-1 or NCA2-2 may be used.'' NCA1-1 is equivalent to WIDE2-1.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:51:08Z<p>CapKE6AFE: /* Solution: Localizing Paths */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/ Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, parts of the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc.<br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic, reducing throughput. Exceptions to this may be in urban canyons, pocket valleys, or remote areas along the coast where it can be demonstrated that a mobile station's packets do not otherwise reach the network. A special event occurring in such remote "shaded areas" may benefit from a temporary "fill-in or event" digi (which only responds to packets addressed via WIDE1-1 or it's own callsign) sited overlooking the operating area for the event duration. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed routinely, you could join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to consider establishing ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets heard on RF to the Internet via [[InternetSystem|APRS-IS]] but do not add duplicate packets to the VHF airwaves as another digi could.<br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this, high-level network "S overlay" digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region. Fill-in digis do not respond to packets addressed via NCA1-1 so a mobile station ''could'' use a path of WIDE1-1,NCA1-1 instead of the routine WIDE1-1,WIDE2-1 mobile path.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. Not normally required; use is discouraged.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed, non-moving''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* ''NCA1-1 or NCA2-2 may be used.'' NCA1-1 is equivalent to WIDE2-1.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:40:09Z<p>CapKE6AFE: /* Solution: Digipeater Siting Strategy */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/ Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, parts of the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc.<br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic, reducing throughput. Exceptions to this may be in urban canyons, pocket valleys, or remote areas along the coast where it can be demonstrated that a mobile station's packets do not otherwise reach the network. A special event occurring in such remote "shaded areas" may benefit from a temporary "fill-in or event" digi (which only responds to packets addressed via WIDE1-1 or it's own callsign) sited overlooking the operating area for the event duration. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed routinely, you could join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to consider establishing ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets heard on RF to the Internet via [[InternetSystem|APRS-IS]] but do not add duplicate packets to the VHF airwaves as another digi could.<br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this all digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. Not normally required; use is discouraged.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed, non-moving''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* ''NCA1-1 or NCA2-2 may be used.'' NCA1-1 is equivalent to WIDE2-1.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:28:40Z<p>CapKE6AFE: /* Overview */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/ Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, parts of the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc.<br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic. Exceptions to this are in urban canyons, pocket valleys, or remote areas along the coast. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed you should join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to consider establishing ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets heard on RF to the Internet via [[InternetSystem|APRS-IS]] but do not add duplicate packets to the VHF airwaves as another digi could.<br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this all digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. Not normally required; use is discouraged.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed, non-moving''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* ''NCA1-1 or NCA2-2 may be used.'' NCA1-1 is equivalent to WIDE2-1.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:27:13Z<p>CapKE6AFE: /* Solution: Receive-Only IGate Strategy */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/ Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc. <br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic. Exceptions to this are in urban canyons, pocket valleys, or remote areas along the coast. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed you should join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to consider establishing ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets heard on RF to the Internet via [[InternetSystem|APRS-IS]] but do not add duplicate packets to the VHF airwaves as another digi could.<br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this all digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. Not normally required; use is discouraged.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed, non-moving''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* ''NCA1-1 or NCA2-2 may be used.'' NCA1-1 is equivalent to WIDE2-1.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:20:09Z<p>CapKE6AFE: /* Recommended path settings for '''''fixed''''' stations */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/ Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc. <br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic. Exceptions to this are in urban canyons, pocket valleys, or remote areas along the coast. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed you should join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to run ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets from RF to the Internet via [[InternetSystem|APRS-IS]] where they are in turn re-transmitted by the high-level digipeaters. <br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this all digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. Not normally required; use is discouraged.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed, non-moving''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. ''Not normally required, use is discouraged''<br />
* ''NCA1-1 or NCA2-2 may be used.'' NCA1-1 is equivalent to WIDE2-1.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:11:50Z<p>CapKE6AFE: /* Recommended path settings for '''''mobile''''' stations */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/ Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc. <br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic. Exceptions to this are in urban canyons, pocket valleys, or remote areas along the coast. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed you should join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to run ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets from RF to the Internet via [[InternetSystem|APRS-IS]] where they are in turn re-transmitted by the high-level digipeaters. <br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this all digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.<br />
* WIDE1-1,WIDE2-2 : Three hops in all directions. Not normally required; use is discouraged.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : ''Not normally required, use is discouraged'' <br />
* ''NCA2-1 or NCA2-2 should be used. Don't use NCA3-3.''<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=NorCal_APRS_Regional_InfoNorCal APRS Regional Info2008-09-16T08:02:48Z<p>CapKE6AFE: /* Recommended path settings for '''''mobile''''' stations */</p>
<hr />
<div>== San Francisco Bay Area ==<br />
<br />
=== Summary Information ===<br />
* Operating Frequency: 144.390<br />
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.<br />
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]<br />
* Local Monitoring and Info: [http://www.norcalaprs.net/ Northern California APRS Information]<br />
<br />
=== Overview ===<br />
The San Francisco Bay Area is home to many radio amateurs and has an active APRS network. The San Francisco Bay Area terrain offers some of the best [[Digipeater|digipeater]] siting in the world. From almost anywhere in the central Bay Area you will have line-of-sight and clear reception to at least one high-level mountain-top digipeater. Exceptions to this are of course in areas such as the "urban canyon" of San Francisco, the western side of the Coastal Range mountains from Santa Cruz north to Pescadero, the eastern side of the Diablo Range from Mt Hamilton north to Pleasanton, etc. <br />
<br />
=== Challenges ===<br />
Due to the large number of APRS users, the 144.390 APRS frequency is almost constantly in use and efforts are always being made to reduce excessive or redundant packets. Use of "old paradigm" {paths|digipaths] (RELAY and WIDE and TRACE and TRACEn-N) is ''strongly'' discouraged and most if not all San Francisco Bay Area digipeaters will no longer respond to these paths. <br />
<br />
==== Solution: Digipeater Siting Strategy ====<br />
The near-ideal geographic layout of the region implies there is usually no reason for an APRS user to set up and run low-level, supplemental, or fill-in digipeaters within the central Bay Area. Doing so will almost always generate redundant packets which increases collisions and channel traffic. Exceptions to this are in urban canyons, pocket valleys, or remote areas along the coast. <br />
<br />
If you have reason to believe that a supplemental or fill-in digipeater is needed you should join the [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group] (hosted on Yahoo Groups) and post a proposal detailing where and why. The folks there will help you determine proper settings to ensure that your digipeater is beneficial to the local users.<br />
<br />
==== Solution: Receive-Only IGate Strategy ====<br />
FM capture effect at Bay Area digipeaters is an issue; distance and channel congestion often results in a higher-powered station (mobile or base) covering packets from a lower-power mobile or handheld. Therefore those wishing to contribute to the local APRS system are encouraged to run ''receive-only'' [[IGate|IGates]] instead of supplemental or fill-in digipeaters. These receive-only IGates pass packets from RF to the Internet via [[InternetSystem|APRS-IS]] where they are in turn re-transmitted by the high-level digipeaters. <br />
<br />
==== Solution: Localizing Paths ====<br />
Even with the "new paradigm" paths (WIDEn-N) being implemented there are still occasionally cases where local traffic will wander in or out of the Northern California region. To reduce this all digipeaters (and some stations) have started using the NCAn-N in place of WIDEn-N paths. This ensures that packets intended for Northern California users remain within the region.<br />
<br />
=== Recommended path settings for '''''mobile''''' stations ===<br />
<br />
* WIDE1-1,WIDE2-1 : Two hops in all directions with potential to use fill-in digis.<br />
* "Commuters" may find that a mobile path of only WIDE1-1 is adequate for their needs.<br />
* ''NCA1-1 or NCA2-2 can be used if you don't travel outside the Northern California (NCA) region.''<br />
<br />
=== Recommended path settings for '''''fixed''''' stations ===<br />
<br />
* WIDE2-1 : One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 : Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 : ''Not normally required, use is discouraged'' <br />
* ''NCA2-1 or NCA2-2 should be used. Don't use NCA3-3.''<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.</div>CapKE6AFEhttp://info.aprs.net/index.php?title=PathsPaths2007-11-21T02:52:59Z<p>CapKE6AFE: /* '''''MOBILE''''' Stations in North America (VHF) */</p>
<hr />
<div>Stub for [[Digipeater|digipeater]] paths - need information on recommended settings for all regions, and new paradigm information.<br />
<br />
==== Recommended Path Settings for: ====<br />
=== '''''MOBILE''''' Stations in North America (VHF) ===<br />
<br />
* WIDE1-1,WIDE2-1 :Two hops in all directions with potential to use fill-in digis. Best path for mobile use in most all areas.<br />
* WIDE1-1,WIDE2-2 :Three hops with potential to use fill-in digis. Use only if truly needed while very far from any mountain digis or cities.<br />
<br />
=== '''''FIXED''''' Stations in North America (VHF) ===<br />
<br />
* WIDE2-1 :One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 :Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 :Three hops in all directions... only for very sparsely populated areas far from any mountain digis or cities. Many digis in populated areas will only give one hop to paths of WIDE3-3 (and broader).<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete.<br />
<br />
For details and explanation, visit Bob WB4APR's [http://www.ew.usna.edu/~bruninga/aprs/fix14439.html NEWn-N Paradigm] web page, also available as the [http://131.122.80.201/~bruninga/aprs/fix14439.html "fix14439"] site.<br />
<br />
=== '''''HF''''' Stations, max routine===<br />
* GATE, WIDE2-1: Recommended for HF APRS, **DO NOT USE** on VHF.<br />
<br />
You can see a bad example of path overkill [[PathOverkill|here]].<br />
<br />
You can see a really detailed discussion of paths and hop counts at [http://webs.lanset.com/wa8lmf/DigiPaths/ http://webs.lanset.com/wa8lmf/DigiPaths/ ].<br />
<br />
=== '''''Mobile''''' Stations in Australia (VK) ===<br />
<br />
* For VK6 & VK8 use RELAY,WIDE2-2<br />
* For VK1, VK2, VK3, VK4 & VK5 use WIDE1-1,WIDE2-1<br />
* For VK7 use WIDE1-1,WIDE2-2 TASn-n also supported.<br />
<br />
* On HF use GATE, WIDE2-1 **DO NOT USE** on VHF.<br />
* On APRS Satellites use ARISS,SGATE,WIDE<br />
<br />
Visit the appropriate state's web page at the [http://www.aprs.net.au/ Australian APRS site] for further details.<br />
<br />
=== Ireland (EI) ===<br />
<br />
* WIDE1-1, WIDE2-2 for Mobile Stations. Two hops with support for Fill-in digis<br />
* WIDE2-2 for Base Stations. Two hops no support for Fill-in Digis. Packets should make it to an Igate.<br />
<br />
If you want to discuss/or disagree with the settings/want to try something else, Please contact either EI7IG or EI8JA.<br />
<br />
=== UK/EU === <br />
<br />
* Mobiles -> RELAY,TRACE2-2 <- (Kenwood Style)<br />
* Home Stations -> APRS,TRACE3-3 <- (UI-View Style)<br />
* IGATE's -> APRS,TRACE1-1 <- (UI-View Style) <br />
<br />
[http://www.apritch.myby.co.uk/uiview_neweu.htm http://www.apritch.myby.co.uk/uiview_neweu.htm]<br />
<br />
===New Zealand===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
=== Norway===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://tf8bk.famutne.net/aprs_tech.html#unproto http://tf8bk.famutne.net/aprs_tech.html#unproto]<br />
<br />
===Poland===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://www.aprs.pl/europe.htm http://www.aprs.pl/europe.htm]<br />
<br />
===Luxembourg===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE4-4 :Home stations<br />
<br />
[http://www.rlx.lu/lx_aprs.htm http://www.rlx.lu/lx_aprs.htm]<br />
<br />
===Germany===<br />
<br />
* WIDE1-1,WIDE2-1 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm]</div>CapKE6AFEhttp://info.aprs.net/index.php?title=PathsPaths2007-11-21T01:49:58Z<p>CapKE6AFE: /* '''''FIXED''''' Stations in North America (VHF) */</p>
<hr />
<div>Stub for [[Digipeater|digipeater]] paths - need information on recommended settings for all regions, and new paradigm information.<br />
<br />
==== Recommended Path Settings for: ====<br />
=== '''''MOBILE''''' Stations in North America (VHF) ===<br />
<br />
* WIDE1-1,WIDE2-1 :Two hops in all directions with potential to use fill-in digis. Best path for mobile use in most all areas.<br />
* WIDE1-1,WIDE2-2 :Three hops with potential to use fill-in digis. Use only while needed if very far from any mountain digis or cities.<br />
<br />
=== '''''FIXED''''' Stations in North America (VHF) ===<br />
<br />
* WIDE2-1 :One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 :Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 :Three hops in all directions... only for very sparsely populated areas far from any mountain digis or cities. Many digis in populated areas will only give one hop to paths of WIDE3-3 (and broader).<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete.<br />
<br />
For details and explanation, visit Bob WB4APR's [http://www.ew.usna.edu/~bruninga/aprs/fix14439.html NEWn-N Paradigm] web page, also available as the [http://131.122.80.201/~bruninga/aprs/fix14439.html "fix14439"] site.<br />
<br />
=== '''''HF''''' Stations, max routine===<br />
* GATE, WIDE2-1: Recommended for HF APRS, **DO NOT USE** on VHF.<br />
<br />
You can see a bad example of path overkill [[PathOverkill|here]].<br />
<br />
You can see a really detailed discussion of paths and hop counts at [http://webs.lanset.com/wa8lmf/DigiPaths/ http://webs.lanset.com/wa8lmf/DigiPaths/ ].<br />
<br />
=== '''''Mobile''''' Stations in Australia (VK) ===<br />
<br />
* For VK6 & VK8 use RELAY,WIDE2-2<br />
* For VK1, VK2, VK3, VK4 & VK5 use WIDE1-1,WIDE2-1<br />
* For VK7 use WIDE1-1,WIDE2-2 TASn-n also supported.<br />
<br />
* On HF use GATE, WIDE2-1 **DO NOT USE** on VHF.<br />
* On APRS Satellites use ARISS,SGATE,WIDE<br />
<br />
Visit the appropriate state's web page at the [http://www.aprs.net.au/ Australian APRS site] for further details.<br />
<br />
=== Ireland (EI) ===<br />
<br />
* WIDE1-1, WIDE2-2 for Mobile Stations. Two hops with support for Fill-in digis<br />
* WIDE2-2 for Base Stations. Two hops no support for Fill-in Digis. Packets should make it to an Igate.<br />
<br />
If you want to discuss/or disagree with the settings/want to try something else, Please contact either EI7IG or EI8JA.<br />
<br />
=== UK/EU === <br />
<br />
* Mobiles -> RELAY,TRACE2-2 <- (Kenwood Style)<br />
* Home Stations -> APRS,TRACE3-3 <- (UI-View Style)<br />
* IGATE's -> APRS,TRACE1-1 <- (UI-View Style) <br />
<br />
[http://www.apritch.myby.co.uk/uiview_neweu.htm http://www.apritch.myby.co.uk/uiview_neweu.htm]<br />
<br />
===New Zealand===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
=== Norway===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://tf8bk.famutne.net/aprs_tech.html#unproto http://tf8bk.famutne.net/aprs_tech.html#unproto]<br />
<br />
===Poland===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://www.aprs.pl/europe.htm http://www.aprs.pl/europe.htm]<br />
<br />
===Luxembourg===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE4-4 :Home stations<br />
<br />
[http://www.rlx.lu/lx_aprs.htm http://www.rlx.lu/lx_aprs.htm]<br />
<br />
===Germany===<br />
<br />
* WIDE1-1,WIDE2-1 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm]</div>CapKE6AFEhttp://info.aprs.net/index.php?title=PathsPaths2007-11-21T01:45:42Z<p>CapKE6AFE: /* '''''FIXED''''' Stations in North America (VHF) */</p>
<hr />
<div>Stub for [[Digipeater|digipeater]] paths - need information on recommended settings for all regions, and new paradigm information.<br />
<br />
==== Recommended Path Settings for: ====<br />
=== '''''MOBILE''''' Stations in North America (VHF) ===<br />
<br />
* WIDE1-1,WIDE2-1 :Two hops in all directions with potential to use fill-in digis. Best path for mobile use in most all areas.<br />
* WIDE1-1,WIDE2-2 :Three hops with potential to use fill-in digis. Use only while needed if very far from any mountain digis or cities.<br />
<br />
=== '''''FIXED''''' Stations in North America (VHF) ===<br />
<br />
* WIDE2-1 :One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 :Two hops in all directions... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 :Three hops in all directions... only for very sparsely populated areas far from any mountain digis or cities. Many digis in populated areas will only give one hop to paths of WIDE3-3 (and longer).<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete.<br />
<br />
For details and explanation, visit Bob WB4APR's [http://www.ew.usna.edu/~bruninga/aprs/fix14439.html NEWn-N Paradigm] web page, also available as the [http://131.122.80.201/~bruninga/aprs/fix14439.html "fix14439"] site.<br />
<br />
=== '''''HF''''' Stations, max routine===<br />
* GATE, WIDE2-1: Recommended for HF APRS, **DO NOT USE** on VHF.<br />
<br />
You can see a bad example of path overkill [[PathOverkill|here]].<br />
<br />
You can see a really detailed discussion of paths and hop counts at [http://webs.lanset.com/wa8lmf/DigiPaths/ http://webs.lanset.com/wa8lmf/DigiPaths/ ].<br />
<br />
=== '''''Mobile''''' Stations in Australia (VK) ===<br />
<br />
* For VK6 & VK8 use RELAY,WIDE2-2<br />
* For VK1, VK2, VK3, VK4 & VK5 use WIDE1-1,WIDE2-1<br />
* For VK7 use WIDE1-1,WIDE2-2 TASn-n also supported.<br />
<br />
* On HF use GATE, WIDE2-1 **DO NOT USE** on VHF.<br />
* On APRS Satellites use ARISS,SGATE,WIDE<br />
<br />
Visit the appropriate state's web page at the [http://www.aprs.net.au/ Australian APRS site] for further details.<br />
<br />
=== Ireland (EI) ===<br />
<br />
* WIDE1-1, WIDE2-2 for Mobile Stations. Two hops with support for Fill-in digis<br />
* WIDE2-2 for Base Stations. Two hops no support for Fill-in Digis. Packets should make it to an Igate.<br />
<br />
If you want to discuss/or disagree with the settings/want to try something else, Please contact either EI7IG or EI8JA.<br />
<br />
=== UK/EU === <br />
<br />
* Mobiles -> RELAY,TRACE2-2 <- (Kenwood Style)<br />
* Home Stations -> APRS,TRACE3-3 <- (UI-View Style)<br />
* IGATE's -> APRS,TRACE1-1 <- (UI-View Style) <br />
<br />
[http://www.apritch.myby.co.uk/uiview_neweu.htm http://www.apritch.myby.co.uk/uiview_neweu.htm]<br />
<br />
===New Zealand===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
=== Norway===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://tf8bk.famutne.net/aprs_tech.html#unproto http://tf8bk.famutne.net/aprs_tech.html#unproto]<br />
<br />
===Poland===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://www.aprs.pl/europe.htm http://www.aprs.pl/europe.htm]<br />
<br />
===Luxembourg===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE4-4 :Home stations<br />
<br />
[http://www.rlx.lu/lx_aprs.htm http://www.rlx.lu/lx_aprs.htm]<br />
<br />
===Germany===<br />
<br />
* WIDE1-1,WIDE2-1 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm]</div>CapKE6AFEhttp://info.aprs.net/index.php?title=PathsPaths2007-11-21T01:43:26Z<p>CapKE6AFE: /* '''''MOBILE''''' Stations in North America (VHF) */</p>
<hr />
<div>Stub for [[Digipeater|digipeater]] paths - need information on recommended settings for all regions, and new paradigm information.<br />
<br />
==== Recommended Path Settings for: ====<br />
=== '''''MOBILE''''' Stations in North America (VHF) ===<br />
<br />
* WIDE1-1,WIDE2-1 :Two hops in all directions with potential to use fill-in digis. Best path for mobile use in most all areas.<br />
* WIDE1-1,WIDE2-2 :Three hops with potential to use fill-in digis. Use only while needed if very far from any mountain digis or cities.<br />
<br />
=== '''''FIXED''''' Stations in North America (VHF) ===<br />
<br />
* WIDE2-1 :One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 :Two hops... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 :Three hops... only for very sparsely populated areas far from any mountain digis or cities. Many digis in populated areas will only give one hop to paths of WIDE3-3 and longer.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete.<br />
<br />
For details and explanation, visit Bob WB4APR's [http://www.ew.usna.edu/~bruninga/aprs/fix14439.html NEWn-N Paradigm] web page, also available as the [http://131.122.80.201/~bruninga/aprs/fix14439.html "fix14439"] site.<br />
<br />
=== '''''HF''''' Stations, max routine===<br />
* GATE, WIDE2-1: Recommended for HF APRS, **DO NOT USE** on VHF.<br />
<br />
You can see a bad example of path overkill [[PathOverkill|here]].<br />
<br />
You can see a really detailed discussion of paths and hop counts at [http://webs.lanset.com/wa8lmf/DigiPaths/ http://webs.lanset.com/wa8lmf/DigiPaths/ ].<br />
<br />
=== '''''Mobile''''' Stations in Australia (VK) ===<br />
<br />
* For VK6 & VK8 use RELAY,WIDE2-2<br />
* For VK1, VK2, VK3, VK4 & VK5 use WIDE1-1,WIDE2-1<br />
* For VK7 use WIDE1-1,WIDE2-2 TASn-n also supported.<br />
<br />
* On HF use GATE, WIDE2-1 **DO NOT USE** on VHF.<br />
* On APRS Satellites use ARISS,SGATE,WIDE<br />
<br />
Visit the appropriate state's web page at the [http://www.aprs.net.au/ Australian APRS site] for further details.<br />
<br />
=== Ireland (EI) ===<br />
<br />
* WIDE1-1, WIDE2-2 for Mobile Stations. Two hops with support for Fill-in digis<br />
* WIDE2-2 for Base Stations. Two hops no support for Fill-in Digis. Packets should make it to an Igate.<br />
<br />
If you want to discuss/or disagree with the settings/want to try something else, Please contact either EI7IG or EI8JA.<br />
<br />
=== UK/EU === <br />
<br />
* Mobiles -> RELAY,TRACE2-2 <- (Kenwood Style)<br />
* Home Stations -> APRS,TRACE3-3 <- (UI-View Style)<br />
* IGATE's -> APRS,TRACE1-1 <- (UI-View Style) <br />
<br />
[http://www.apritch.myby.co.uk/uiview_neweu.htm http://www.apritch.myby.co.uk/uiview_neweu.htm]<br />
<br />
===New Zealand===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
=== Norway===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://tf8bk.famutne.net/aprs_tech.html#unproto http://tf8bk.famutne.net/aprs_tech.html#unproto]<br />
<br />
===Poland===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://www.aprs.pl/europe.htm http://www.aprs.pl/europe.htm]<br />
<br />
===Luxembourg===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE4-4 :Home stations<br />
<br />
[http://www.rlx.lu/lx_aprs.htm http://www.rlx.lu/lx_aprs.htm]<br />
<br />
===Germany===<br />
<br />
* WIDE1-1,WIDE2-1 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm]</div>CapKE6AFEhttp://info.aprs.net/index.php?title=PathsPaths2007-11-20T00:25:18Z<p>CapKE6AFE: /* '''''FIXED''''' Stations in North America (VHF) */</p>
<hr />
<div>Stub for [[Digipeater|digipeater]] paths - need information on recommended settings for all regions, and new paradigm information.<br />
<br />
==== Recommended Path Settings for: ====<br />
=== '''''MOBILE''''' Stations in North America (VHF) ===<br />
<br />
* WIDE1-1,WIDE2-1 :Two hops in all directions and potential for fill-in digis. Best path for mobile use in most all areas.<br />
* WIDE1-1,WIDE2-2 :Three hops and potential for fill-in digis. Use only while needed if far from any mountain digis or cities.<br />
<br />
=== '''''FIXED''''' Stations in North America (VHF) ===<br />
<br />
* WIDE2-1 :One hop... suitable if you are within earshot of a "high" WIDEn-N digi with a large footprint.<br />
* WIDE2-2 :Two hops... recommended maximum for routine and courteous use in most areas.<br />
* WIDE3-3 :Three hops... only for very sparsely populated areas far from any mountain digis or cities. Many digis in populated areas will only give one hop to paths of WIDE3-3 and longer.<br />
<br />
RELAY and WIDE and TRACE and TRACEn-N are obsolete.<br />
<br />
For details and explanation, visit Bob WB4APR's [http://www.ew.usna.edu/~bruninga/aprs/fix14439.html NEWn-N Paradigm] web page, also available as the [http://131.122.80.201/~bruninga/aprs/fix14439.html "fix14439"] site.<br />
<br />
=== '''''HF''''' Stations, max routine===<br />
* GATE, WIDE2-1: Recommended for HF APRS, **DO NOT USE** on VHF.<br />
<br />
You can see a bad example of path overkill [[PathOverkill|here]].<br />
<br />
You can see a really detailed discussion of paths and hop counts at [http://webs.lanset.com/wa8lmf/DigiPaths/ http://webs.lanset.com/wa8lmf/DigiPaths/ ].<br />
<br />
=== '''''Mobile''''' Stations in Australia (VK) ===<br />
<br />
* For VK6 & VK8 use RELAY,WIDE2-2<br />
* For VK1, VK2, VK3, VK4 & VK5 use WIDE1-1,WIDE2-1<br />
* For VK7 use WIDE1-1,WIDE2-2 TASn-n also supported.<br />
<br />
* On HF use GATE, WIDE2-1 **DO NOT USE** on VHF.<br />
* On APRS Satellites use ARISS,SGATE,WIDE<br />
<br />
Visit the appropriate state's web page at the [http://www.aprs.net.au/ Australian APRS site] for further details.<br />
<br />
=== Ireland (EI) ===<br />
<br />
* WIDE1-1, WIDE2-2 for Mobile Stations. Two hops with support for Fill-in digis<br />
* WIDE2-2 for Base Stations. Two hops no support for Fill-in Digis. Packets should make it to an Igate.<br />
<br />
If you want to discuss/or disagree with the settings/want to try something else, Please contact either EI7IG or EI8JA.<br />
<br />
=== UK/EU === <br />
<br />
* Mobiles -> RELAY,TRACE2-2 <- (Kenwood Style)<br />
* Home Stations -> APRS,TRACE3-3 <- (UI-View Style)<br />
* IGATE's -> APRS,TRACE1-1 <- (UI-View Style) <br />
<br />
[http://www.apritch.myby.co.uk/uiview_neweu.htm http://www.apritch.myby.co.uk/uiview_neweu.htm]<br />
<br />
===New Zealand===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
=== Norway===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://tf8bk.famutne.net/aprs_tech.html#unproto http://tf8bk.famutne.net/aprs_tech.html#unproto]<br />
<br />
===Poland===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE3-3 :Home stations<br />
<br />
[http://www.aprs.pl/europe.htm http://www.aprs.pl/europe.htm]<br />
<br />
===Luxembourg===<br />
<br />
* WIDE1-1,WIDE2-2 :Mobile trackers<br />
* WIDE4-4 :Home stations<br />
<br />
[http://www.rlx.lu/lx_aprs.htm http://www.rlx.lu/lx_aprs.htm]<br />
<br />
===Germany===<br />
<br />
* WIDE1-1,WIDE2-1 :Mobile trackers<br />
* WIDE2-2 :Home stations<br />
<br />
[http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm http://www.aprs-dl.de/index.php?Umstellung_NEWn-N:NEWn-N-Paradigm]</div>CapKE6AFE