APRSWiki - User contributions [en]

NorCal APRS Regional Info

2011-05-30T03:25:31Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater Sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is increased by "low value" timed beacons from stations that beacon the same info 24/7 using multiple hop paths. Some Sysops have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path.
(KPC Settings: UIDIGI ON WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to "cellularize" a geographic area. This example of a modified "S" Digi would still forward fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI ON WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

Many "S" wide area Digis are set to trap large paths. High level "S" Digis that are heard directly by several I-gates could be set to limit network load by trapping common multi-hop paths. The wide area Digi is set to Trap WIDE2-2. This Digi would replace the WIDE2-2 with MyCall then Digipeat it. The WIDE2-2 would be treated as a single hop packet going out over the wide area Digi. (KPC Settings: UIDIGI ON WIDE2-2,WIDE3-3,WIDE3-2,WIDE4-4)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT=0 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2011-05-30T03:24:53Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater Sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is increased by "low value" timed beacons from stations that beacon the same info 24/7 using multiple hop paths. Some Sysops have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path.
(KPC Settings: UIDIGI ON WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to "cellularize" a geographic area. This example of a modified "S" Digi would still forward fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI ON WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

Many "S" wide area Digis are set to trap large paths. High level "S" Digis that are heard directly by several I-gates could be set to limit network load by trapping common multi-hop paths. The wide area Digi is set to Trap WIDE2-2. This Digi would replace the WIDE2-2 with MyCall then Digipeat it. The WIDE2-2 would be treated as a single hop packet going out over the wide area Digi. (KPC Settings: UIDIGI ON WIDE2-2,WIDE3-3,WIDE3-2,WIDE4-4)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT 0 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T02:04:01Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater Sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is increased by "low value" timed beacons from stations that beacon the same info 24/7 using multiple hop paths. Some Sysops have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path.
(KPC Settings: UIDIGI ON WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to "cellularize" a geographic area. This example of a modified "S" Digi would still forward fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI ON WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

Many "S" wide area Digis are set to trap large paths. High level "S" Digis that are heard directly by several I-gates could be set to limit network load by trapping common multi-hop paths. The wide area Digi is set to Trap WIDE2-2. This Digi would replace the WIDE2-2 with MyCall then Digipeat it. The WIDE2-2 would be treated as a single hop packet going out over the wide area Digi. (KPC Settings: UIDIGI ON WIDE2-2,WIDE3-3,WIDE3-2,WIDE4-4)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T01:56:21Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater Sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is increased by "low value" timed beacons from stations that beacon the same info 24/7 using multiple hop paths. Some Sysops have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path.
(KPC Settings: UIDIGI ON WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to cellularize a geographic area. This example of a modified "S" Digi would still forward fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI ON WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

Many "S" Digis are set to trap large paths. High level "S" Digis that are heard directly by several I-gates could be set to limit network load by trapping common multi-hop paths. The wide area Digi is set to Trap WIDE2-2. This Digi would replace the WIDE2-2 with MyCall then Digipeat it. The WIDE2-2 would be treated as a single hop packet going out over the wide area Digi. (KPC Settings: UIDIGI ON WIDE2-2,WIDE3-3,WIDE3-2,WIDE4-4)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T00:51:35Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is caused by low value timed beacons from distant stations that beacon the same info 24/7, using multiple hops. Some have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 in their first digi path without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path.
(KPC Settings: UIDIGI WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to cellularize a geographic area. This example of a modified "S" Digi would still forward most fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T00:50:17Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is caused by low value timed beacons from distant stations that beacon the same info 24/7, using multiple hops. Some have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 in their first digi path without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path.
Home stations with broadband can greatly help the network by setting up an I-gate rather than a Digi.
(KPC Settings: UIDIGI WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to cellularize a geographic area. This example of a modified "S" Digi would still forward most fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T00:49:46Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is caused by low value timed beacons from distant stations that beacon the same info 24/7, using multiple hops. Some have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 in their first digi path without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path.
Home stations with broadband can greatly help the network by setting up an I-gate rather than a Digi.
(KPC Settings: UIDIGI WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to cellularize a geographic area. This example of a modified "S" Digi would still forward most fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T00:47:58Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is caused by low value timed beacons from distant stations that beacon the same info 24/7, using multiple hops. Some have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 in their first digi path without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path. Home stations with broadband can greatly help the network by setting up an I-gate rather than a Digi.
(KPC Settings: UIDIGI WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" Digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to cellularize a geographic area. This example of a modified "S" Digi would still forward most fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(KPC Settings: UIDIGI WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T00:45:57Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Attentive Digipeater sysops have determined that there are too many "S" Digis in California. Network overload occurs daily during peak hours. Much of the overload is caused by low value timed beacons from distant stations that beacon the same info 24/7, using multiple hops. Some have successfully reduced network traffic in their areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain tops. This design can light up an area for moving objects that use WIDE1-1 in their first digi path without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path. Home stations with broadband can greatly help the network by setting up an I-gate rather than a Digi.
(UIDIGI WIDE1-1 || UITRACE OFF || UIFLOOD OFF)

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to cellularize a geographic area. This example of a modified "S" Digi would still forward most fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed WIDE2-1, or NCAn-N".
(UIDIGI WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-19T00:20:45Z

Radionerd: /* Solution: Digipeater Siting Strategy */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

Digi sysops have successfully reduced Network traffic in some areas by reconfiguring their "S" Digis to Fill-in Digis. California Fill-in Digis are often located on high level Mountain Tops. This design can light up an area for moving objects that use WIDE1-1 in their first digi path without greatly increasing network load. Fill-in Digis listen quietly, waiting for first hop fresh packets from properly configured mobiles. Stale packets, and non-moving objects are ignored. Courteous Fill-ins beacon without a path. Home stations with broadband can greatly help the network by setting up an I-gate rather than a Digi.

Digis that habitually import stale WIDE2-2, or higher, packets into a localized RF area can be modified to only react on specific paths. An "S" digi could be reconfigured to only react to WIDE1-1 WIDE2-1 and NCAn-N. These measures can be used to cellularize a geographic area. (UIDIGI WIDE1-1,WIDE2-1 || UITRACE NCA,30 ||UIFLOOD OFF)This modified "S" Digi would still forward most fresh traffic using the recommended paths. These Modified Digis are encouraged to beacon the locally recommended path. "Mobiles Please use WIDE1-1, Fixed use WIDE2-1 or NCAn-N".

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-18T23:23:38Z

Radionerd: /* Solution: Localizing Paths */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most Digis trap abusive paths, many trap WIDE3-3, and some high level Digis even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-18T23:10:58Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''', if available, is recommended on Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-18T23:08:27Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. Some High level Digis never beacon with any path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This allows users one additional hop via the trapping Digi. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one additional hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with individual hop limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring potential abusive paths.

NorCal APRS Regional Info

2010-09-18T22:38:11Z

Radionerd: /* San Francisco Bay Area */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.

NorCal APRS Regional Info

2010-09-18T22:33:27Z

Radionerd: /* Recommended path settings for ''''RF Only'''' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some stations have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions. The Routine two hop paths work good for most users that rely on the RF network.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T22:26:23Z

Radionerd: /* Recommended path settings for ''''RF Only'''' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some users have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions.
* '''SSn-N''' is usually not trapped by digis. NCA2-2 can blanket Norcal.
* '''DigiCall''' Directed paths via Digi callsigns are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T22:20:36Z

Radionerd: /* San Francisco Bay Area */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended path settings for ''''RF Only'''' stations ===
Some users have intended targets that they reach directly over RF. It is up to the individual to test different paths that will suffice. The routine mobile or fixed two hop path can propagate out several hundred miles in all directions.
* SSn-N is usually not trapped by digis. NCA2-2 can blanket Norcal.
* DigiCall Directed paths via Digi callsign are very courteous when sending RF messages (Path:DIGI1,DIGI2,WIDE2-1). An APRS message can be sent from Redding to Southern Cal via a directed Path: N6RZR-3,W6PKT-5,WR6ABD,W6BXN-3,SCA2-2. Directed paths reduce potential for fratricide collisions, but also often need multiple retries to complete long paths.
*'''RFONLY''' added to the end of the path can block packets from being forwarded to the internet via I-Gates. (Path:NCA2-2,RFONLY). Many I-gates are setup to ignore packets with RFONLY or NOGATE set in the last path.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T21:15:52Z

Radionerd: /* Recommended path settings for '''''fixed, non-moving''''' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 use is discouraged, three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T21:06:22Z

Radionerd: /* Recommended path settings for '''''fixed, non-moving''''' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* WIDE3-3 '''use is discouraged'''Three hops in all directions. Not normally required, many digis trap WIDE3-3 and higher''
* WIDE1-1 Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T21:02:02Z

Radionerd: /* Recommended path settings for '''''mobile stations''''' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3, or higher, is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, '''use is discouraged''', many digis trap WIDE3-3 and higher''
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T21:00:46Z

Radionerd: /* Recommended path settings for '''''mobile stations''''' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)
* WIDE3-3 or higher WIDEn-N is not recommended since many Digis trap or ignore WIDE3-3 and above.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, '''use is discouraged''', many digis trap WIDE3-3 and higher''
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T20:54:11Z

Radionerd: /* Recommended path settings for '''''mobile stations''''' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network. If internet maps are your target, WIDE1-1 is the courteous choice.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, '''use is discouraged''', many digis trap WIDE3-3 and higher''
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T20:39:34Z

Radionerd: /* Recommended path settings for '''''fixed, non-moving''''' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)

=== Recommended path settings for '''''fixed, non-moving''''' stations ===
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous to our neighbors, and is equivalent to WIDE2-1.
* '''WIDE2-1''' : One hop... Recommended if you are within earshot of a "high" WIDEn-N digi with a large footprint. Avoids use of all fill-in digis.
* '''WIDE2-2''' : Two hops in all directions... maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, '''use is discouraged''', many digis trap WIDE3-3 and higher''
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-09-18T20:32:23Z

Radionerd: /* Recommended path settings for '''''mobile stations''''' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===
* '''WIDE1-1''' : "Commuters" may find that a short, single hop, mobile path of WIDE1-1 is adequate for their needs. This "Tracker" path works well throughout California since most Digis are within direct earshot of one or more I-Gates. Single hop paths are light and polite on the RF network.
* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; '''use is discouraged'''. (Potential for packets to be propagated into neighboring States, activating up to 36 distant digipeaters).
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-07-11T22:00:43Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects TX rate should be similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-07-11T21:34:49Z

Radionerd: /* Solution: Localizing Paths */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap WIDE3-3, and some high level Digies even trap WIDE2-2. Fill-in digis usually only respond to WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-07-11T21:15:13Z

Radionerd: /* Recommended path settings for '''''mobile stations''''' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path, or no path when at high altitude. (WIDE1-1, or WIDE2-1, or NCA1-1 in NORCAL)

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

ToCall

2010-07-10T09:47:36Z

Radionerd: /* Identifying APRS Software Version */

==Specifying Symbols==

If you are sending a packet that can't include the normal icon code embedded in the lat/lon position (/$), you can add one of these special beacon-style ToCalls to the address string of your packet.

Both nn and xy are placeholders to the APRS Symbol Table, while z is a placeholder for an optional symbol overlay.

* GPSxyz
* GPSCnn
* GPSEnn
* SPCxyz
* SYMxyz

==Identifying APRS Software Version==

If you want to include the name and version of the software being used, you can add one of these ToCalls to the destination address, replacing the xx or xxx with the software version number.

This table is from the APRS 1.01 specification and [http://eng.usna.navy.mil/~bruninga/aprs/tocalls.txt]:
{| border="1"
|APAGWx
|SV2AGW's AGWtracker
|-
|APCxxx
|APRS/CE, Windows CE
|-
|APDPRS
|D-Star originated posits
|-
|APDxxx
|Linux aprsd server
|-
|APExxx
|PIC-Encoder
|-
|APIxxx
|Icom DSTAR (xxx=1st 3 of model #)
|-
|APICxx
|ICQ messaging
|-
|APK0xx
|Kenwood TH-D7s
|-
|APK1xx
|Kenwood TM-D700/D710s
|-
|APMxxx
|MacAPRS
|-
|APN3xx
|Kantronics KPC-3 (APN383 & above 3+)
|-
|APN9xx
|Kantronics KPC-9612
|-
|APNDxx
|Digi_Ned
|-
|APNMxx
|MFJ TNC
|-
|APNTxx
|SV2AGW's TNT tnc as a digi
|-
|APNXxx
|TNC-X (K6DBG)
|-
|APOxxx
|APRSPoint
|-
|APOT01
|Open Track
|-
|APOT03
|Open Track + (OT+)
|-
|APOT21
|Open Tracker 2 (OT2)
|-
|APOTW1
|ADS-WS1 WX
|-
|APOD1w
|Open Track with 1 wire WX
|-
|APOU2k
|Open Track for Ultimeter
|-
|APPxxx
|pocketAPRS
|-
|AP4Rxx
|APRS4R
|-
|APRxxx
|APRSdos
|-
|APRS
|older versions of APRSdos
|-
|APRSM
|older versions of MacAPRS
|-
|APRSW
|older versions of WinAPRS
|-
|APSxxx
|APRS+SA
|-
|APTIGR
|TigerTrack
|-
|APTTxx
|Tiny Track
|-
|APT2xx
|Tiny Track II
|-
|APT3xx
|Tiny Track III
|-
|APTT4
|Tiny Track IV
|-
|APTAxx
|K4ATM's Tiny Track
|-
|APTW01
|APTWxx Byonics WXTrac
|-
|APU1xx
|UIview-16
|-
|APU2xx
|UIview-32
|-
|APU3xx
|UIview Terminal Program
|-
|APWxxx
|WinAPRS
|-
|APXxxx
|Xastir version x.x.x (historically also X-APRS)
|-
|APYxxx
|Yaesu radios (future)
|-
|APY008
|Yeasu VX-8
|-
|APY350
|Yeasu FTM-350
|-
|APWWxx
|APRSISCE/32
|-
|APZxxx
|Experimental
|}

Other strings which have been heard on the air, but that are not documented in the APRS Spec version 1.01, include:
{| border="1"
|APIB10
|
|}

These calls are instead documented in Bob Bruninga's updated [[http://www.ew.usna.edu/~bruninga/aprs/tocalls.txt tocalls.txt file]].

==Generic Beacon-Style ToCalls==

* AIR* †
* ALL* To All stations.
* AP*
* BEACON
* CQ* Calling CQ
* GPS Specifically intended for use by trackers sending lat/long positions via digipeaters which have the capability of converting positions to compressed data format.
* GPS* For specifying a symbol when unable to do so in the position report (e.g. NMEA strings)
* DF* Direction Finding Report.
* DGPS* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* DRILL* Training Drill or Exercise
* DX* DX Spot
* ID*
* JAVA*
* MAIL*
* MICE* Mic-E Report
* QST* News Announcement
* QTH*
* RTCM* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* SKY* Used for SkyWarn stations.
* SPACE*
* SPC* For specifying a Special Event Station symbol
* SYM* For specifying a symbol, but reserved for future use
* TEL* Telemetry station.
* TEST*
* TLM* Telemetry station.
* WX*
* ZIP* †

The asterisk is a wildcard, allowing the address to be extended (up to a total
of 6 alphanumeric characters).
† The AIR* and ZIP* addresses are deprecated.

These addresses are copied by everyone. All APRS software must accept
packets with these destination addresses.
The address GPS (i.e. the 3-letter address GPS,

ToCall

2010-07-10T09:29:26Z

Radionerd: /* Identifying APRS Software Version */

==Specifying Symbols==

If you are sending a packet that can't include the normal icon code embedded in the lat/lon position (/$), you can add one of these special beacon-style ToCalls to the address string of your packet.

Both nn and xy are placeholders to the APRS Symbol Table, while z is a placeholder for an optional symbol overlay.

* GPSxyz
* GPSCnn
* GPSEnn
* SPCxyz
* SYMxyz

==Identifying APRS Software Version==

If you want to include the name and version of the software being used, you can add one of these ToCalls to the destination address, replacing the xx or xxx with the software version number.

This table is from the APRS 1.01 specification and [http://eng.usna.navy.mil/~bruninga/aprs/tocalls.txt]:
{| border="1"
|APAGWx
|SV2AGW's AGWtracker
|-
|APCxxx
|APRS/CE, Windows CE
|-
|APDPRS
|D-Star originated posits
|-
|APDxxx
|Linux aprsd server
|-
|APExxx
|PIC-Encoder
|-
|APIxxx
|Icom radios (future)
|-
|APICxx
|ICQ messaging
|-
|APK0xx
|Kenwood TH-D7s
|-
|APK1xx
|Kenwood TM-D700/D710s
|-
|APMxxx
|MacAPRS
|-
|APN3xx
|Kantronics KPC-3 (APN383 & above 3+)
|-
|APN9xx
|Kantronics KPC-9612
|-
|APNDxx
|Digi_Ned
|-
|APNMxx
|MFJ TNC
|-
|APNTxx
|SV2AGW's TNT tnc as a digi
|-
|APNXxx
|TNC-X (K6DBG)
|-
|APOxxx
|APRSPoint
|-
|APOT01
|Open Track
|-
|APOT03
|Open Track + (OT+)
|-
|APOT21
|Open Tracker 2 (OT2)
|-
|APOTW1
|ADS-WS1 WX
|-
|APOD1w
|Open Track with 1 wire WX
|-
|APOU2k
|Open Track for Ultimeter
|-
|APPxxx
|pocketAPRS
|-
|AP4Rxx
|APRS4R
|-
|APRxxx
|APRSdos
|-
|APRS
|older versions of APRSdos
|-
|APRSM
|older versions of MacAPRS
|-
|APRSW
|older versions of WinAPRS
|-
|APSxxx
|APRS+SA
|-
|APTIGR
|TigerTrack
|-
|APTTxx
|Tiny Track
|-
|APT2xx
|Tiny Track II
|-
|APT3xx
|Tiny Track III
|-
|APTT4
|Tiny Track IV
|-
|APTAxx
|K4ATM's Tiny Track
|-
|APTW01
|APTWxx Byonics WXTrac
|-
|APU1xx
|UIview-16
|-
|APU2xx
|UIview-32
|-
|APU3xx
|UIview Terminal Program
|-
|APWxxx
|WinAPRS
|-
|APXxxx
|Xastir version x.x.x (historically also X-APRS)
|-
|APYxxx
|Yaesu radios (future)
|-
|APY008
|Yeasu VX-8
|-
|APY350
|Yeasu FTM-350
|-
|APWWxx
|APRSISCE/32
|-
|APZxxx
|Experimental
|}

Other strings which have been heard on the air, but that are not documented in the APRS Spec version 1.01, include:
{| border="1"
|APIB10
|
|}

These calls are instead documented in Bob Bruninga's updated [[http://www.ew.usna.edu/~bruninga/aprs/tocalls.txt tocalls.txt file]].

==Generic Beacon-Style ToCalls==

* AIR* †
* ALL* To All stations.
* AP*
* BEACON
* CQ* Calling CQ
* GPS Specifically intended for use by trackers sending lat/long positions via digipeaters which have the capability of converting positions to compressed data format.
* GPS* For specifying a symbol when unable to do so in the position report (e.g. NMEA strings)
* DF* Direction Finding Report.
* DGPS* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* DRILL* Training Drill or Exercise
* DX* DX Spot
* ID*
* JAVA*
* MAIL*
* MICE* Mic-E Report
* QST* News Announcement
* QTH*
* RTCM* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* SKY* Used for SkyWarn stations.
* SPACE*
* SPC* For specifying a Special Event Station symbol
* SYM* For specifying a symbol, but reserved for future use
* TEL* Telemetry station.
* TEST*
* TLM* Telemetry station.
* WX*
* ZIP* †

The asterisk is a wildcard, allowing the address to be extended (up to a total
of 6 alphanumeric characters).
† The AIR* and ZIP* addresses are deprecated.

These addresses are copied by everyone. All APRS software must accept
packets with these destination addresses.
The address GPS (i.e. the 3-letter address GPS,

ToCall

2010-07-10T09:19:01Z

Radionerd: /* Identifying APRS Software Version */

==Specifying Symbols==

If you are sending a packet that can't include the normal icon code embedded in the lat/lon position (/$), you can add one of these special beacon-style ToCalls to the address string of your packet.

Both nn and xy are placeholders to the APRS Symbol Table, while z is a placeholder for an optional symbol overlay.

* GPSxyz
* GPSCnn
* GPSEnn
* SPCxyz
* SYMxyz

==Identifying APRS Software Version==

If you want to include the name and version of the software being used, you can add one of these ToCalls to the destination address, replacing the xx or xxx with the software version number.

This table is from the APRS 1.01 specification and [http://eng.usna.navy.mil/~bruninga/aprs/tocalls.txt]:
{| border="1"
|APAGWx
|SV2AGW's AGWtracker
|-
|APCxxx
|APRS/CE, Windows CE
|-
|APDPRS
|D-Star originated posits
|-
|APDxxx
|Linux aprsd server
|-
|APExxx
|PIC-Encoder
|-
|APIxxx
|Icom radios (future)
|-
|APICxx
|ICQ messaging
|-
|APK0xx
|Kenwood TH-D7s
|-
|APK1xx
|Kenwood TM-D700/D710s
|-
|APMxxx
|MacAPRS
|-
|APN3xx
|Kantronics KPC-3 (APN383 & above 3+)
|-
|APN9xx
|Kantronics KPC-9612
|-
|APNDxx
|Digi_Ned
|-
|APNMxx
|MFJ TNC
|-
|APNTxx
|SV2AGW's TNT tnc as a digi
|-
|APNXxx
|TNC-X (K6DBG)
|-
|APOxxx
|APRSPoint
|-
|APOT01
|Open Track
|-
|APOT03
|Open Track + (OT+)
|-
|APOT21
|Open Tracker 2 (OT2)
|-
|APOTW1
|ADS-WS1 WX
|-
|APOD1w
|Open Track with 1 wire WX
|-
|APOU2k
|Open Track for Ultimeter
|-
|APPxxx
|pocketAPRS
|-
|AP4Rxx
|APRS4R
|-
|APRxxx
|APRSdos
|-
|APRS
|older versions of APRSdos
|-
|APRSM
|older versions of MacAPRS
|-
|APRSW
|older versions of WinAPRS
|-
|APSxxx
|APRS+SA
|-
|APTIGR
|TigerTrack
|-
|APTTxx
|Tiny Track
|-
|APT2xx
|Tiny Track II
|-
|APT3xx
|Tiny Track III
|-
|APTT4
|Tiny Track IV
|-
|APTAxx
|K4ATM's Tiny Track
|-
|APTW01
|APTWxx Byonics WXTrac
|-
|APU1xx
|UIview-16
|-
|APU2xx
|UIview-32
|-
|APU3xx
|UIview Terminal Program
|-
|APWxxx
|WinAPRS
|-
|APXxxx
|Xastir version x.x.x (historically also X-APRS)
|-
|APYxxx
|Yaesu radios (future)
|-
|APY008
|Yeasu VX-8
|-
|APWWxx
|APRSISCE/32
|-
|APZxxx
|Experimental
|}

Other strings which have been heard on the air, but that are not documented in the APRS Spec version 1.01, include:
{| border="1"
|APIB10
|
|}

These calls are instead documented in Bob Bruninga's updated [[http://www.ew.usna.edu/~bruninga/aprs/tocalls.txt tocalls.txt file]].

==Generic Beacon-Style ToCalls==

* AIR* †
* ALL* To All stations.
* AP*
* BEACON
* CQ* Calling CQ
* GPS Specifically intended for use by trackers sending lat/long positions via digipeaters which have the capability of converting positions to compressed data format.
* GPS* For specifying a symbol when unable to do so in the position report (e.g. NMEA strings)
* DF* Direction Finding Report.
* DGPS* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* DRILL* Training Drill or Exercise
* DX* DX Spot
* ID*
* JAVA*
* MAIL*
* MICE* Mic-E Report
* QST* News Announcement
* QTH*
* RTCM* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* SKY* Used for SkyWarn stations.
* SPACE*
* SPC* For specifying a Special Event Station symbol
* SYM* For specifying a symbol, but reserved for future use
* TEL* Telemetry station.
* TEST*
* TLM* Telemetry station.
* WX*
* ZIP* †

The asterisk is a wildcard, allowing the address to be extended (up to a total
of 6 alphanumeric characters).
† The AIR* and ZIP* addresses are deprecated.

These addresses are copied by everyone. All APRS software must accept
packets with these destination addresses.
The address GPS (i.e. the 3-letter address GPS,

ToCall

2010-07-10T08:59:39Z

Radionerd: /* Identifying APRS Software Version */

==Specifying Symbols==

If you are sending a packet that can't include the normal icon code embedded in the lat/lon position (/$), you can add one of these special beacon-style ToCalls to the address string of your packet.

Both nn and xy are placeholders to the APRS Symbol Table, while z is a placeholder for an optional symbol overlay.

* GPSxyz
* GPSCnn
* GPSEnn
* SPCxyz
* SYMxyz

==Identifying APRS Software Version==

If you want to include the name and version of the software being used, you can add one of these ToCalls to the destination address, replacing the xx or xxx with the software version number.

This table is from the APRS 1.01 specification and [http://eng.usna.navy.mil/~bruninga/aprs/tocalls.txt]:
{| border="1"
|APAGWx
|SV2AGW's AGWtracker
|-
|APCxxx
|APRS/CE, Windows CE
|-
|APDPRS
|D-Star originated posits
|-
|APDxxx
|Linux aprsd server
|-
|APExxx
|PIC-Encoder
|-
|APIxxx
|Icom radios (future)
|-
|APICxx
|ICQ messaging
|-
|APK0xx
|Kenwood TH-D7s
|-
|APK1xx
|Kenwood TM-D700/D710s
|-
|APMxxx
|MacAPRS
|-
|APN3xx
|Kantronics KPC-3
|-
|APN9xx
|Kantronics KPC-9612
|-
|APNDxx
|Digi_Ned
|-
|APNMxx
|MFJ TNC
|-
|APNTxx
|SV2AGW's TNT tnc as a digi
|-
|APNXxx
|TNC-X (K6DBG)
|-
|APOxxx
|APRSPoint
|-
|APOT01
|Open Track
|-
|APOT03
|Open Track + (OT+)
|-
|APOT21
|Open Tracker 2 (OT2)
|-
|APOTW1
|ADS-WS1 WX
|-
|APOD1w
|Open Track with 1 wire WX
|-
|APOU2k
|Open Track for Ultimeter
|-
|APPxxx
|pocketAPRS
|-
|AP4Rxx
|APRS4R
|-
|APRxxx
|APRSdos
|-
|APRS
|older versions of APRSdos
|-
|APRSM
|older versions of MacAPRS
|-
|APRSW
|older versions of WinAPRS
|-
|APSxxx
|APRS+SA
|-
|APTIGR
|TigerTrack
|-
|APTTxx
|Tiny Track
|-
|APT2xx
|Tiny Track II
|-
|APT3xx
|Tiny Track III
|-
|APTT4
|Tiny Track IV
|-
|APTAxx
|K4ATM's Tiny Track
|-
|APTW01
|APTWxx Byonics WXTrac
|-
|APU1xx
|UIview-16
|-
|APU2xx
|UIview-32
|-
|APU3xx
|UIview Terminal Program
|-
|APWxxx
|WinAPRS
|-
|APXxxx
|Xastir version x.x.x (historically also X-APRS)
|-
|APYxxx
|Yaesu radios (future)
|-
|APY008
|Yeasu VX-8
|-
|APWWxx
|APRSISCE/32
|-
|APZxxx
|Experimental
|}

Other strings which have been heard on the air, but that are not documented in the APRS Spec version 1.01, include:
{| border="1"
|APIB10
|
|}

These calls are instead documented in Bob Bruninga's updated [[http://www.ew.usna.edu/~bruninga/aprs/tocalls.txt tocalls.txt file]].

==Generic Beacon-Style ToCalls==

* AIR* †
* ALL* To All stations.
* AP*
* BEACON
* CQ* Calling CQ
* GPS Specifically intended for use by trackers sending lat/long positions via digipeaters which have the capability of converting positions to compressed data format.
* GPS* For specifying a symbol when unable to do so in the position report (e.g. NMEA strings)
* DF* Direction Finding Report.
* DGPS* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* DRILL* Training Drill or Exercise
* DX* DX Spot
* ID*
* JAVA*
* MAIL*
* MICE* Mic-E Report
* QST* News Announcement
* QTH*
* RTCM* Used by differential GPS correction stations. Most software will not make use of packets using this address, other than to pass them on to an attached GPS unit.
* SKY* Used for SkyWarn stations.
* SPACE*
* SPC* For specifying a Special Event Station symbol
* SYM* For specifying a symbol, but reserved for future use
* TEL* Telemetry station.
* TEST*
* TLM* Telemetry station.
* WX*
* ZIP* †

The asterisk is a wildcard, allowing the address to be extended (up to a total
of 6 alphanumeric characters).
† The AIR* and ZIP* addresses are deprecated.

These addresses are copied by everyone. All APRS software must accept
packets with these destination addresses.
The address GPS (i.e. the 3-letter address GPS,

NorCal APRS Regional Info

2010-02-23T05:27:44Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings, or Position timing to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 or 15 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-01-23T01:08:17Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=0 Quiet=0
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-01-10T07:09:35Z

Radionerd: /* Solution: Localizing Paths */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. Northern California's [http://www.norcalaprs.net/usagex.html APRS HOGS] web site can help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. Check to see if your call shows up on the [http://www.findu.com/cgi-bin/errors.cgi APRS Errors] list (It's a big list, put the callsign in your browser's find/search tab to parse). These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-01-10T06:16:51Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many uninformed users to overload our precious frequency, that we all have to share. Ultimately it's up to each individual to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. This technique is more channel efficient than simple time based beaconing, as it dynamically reduces the number of packets being sent as the unit velocity decreases. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to a rate that adversely affects the RF network.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep an object on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging CornerPegging™]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of with every position beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to [http://www.aprs-is.net/ APRS-IS]. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-01-10T05:40:54Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to an abusive rate.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while [http://info.aprs.net/index.php/CornerPegging corner pegging]. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-01-06T05:31:46Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to an abusive rate.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2010-01-06T05:30:35Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing, when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous. Changing the default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to an abusive rate.
* '''Stationary Mobile''' : Non moving objects should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altitude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-29T02:40:22Z

Radionerd: /* Solution: Localizing Paths */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the settings that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing, when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec). Changing default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to an abusive rate.
* '''Stationary Mobile''' : Should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altititude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-24T00:57:04Z

Radionerd: /* Recommended path settings for '''''fixed, non-moving''''' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
* RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing, when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec). Changing default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to an abusive rate.
* '''Stationary Mobile''' : Should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altititude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-24T00:55:59Z

Radionerd: /* Recommended path settings for '''''mobile stations''''' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''
* Aircraft are recommended to use a single hop path WIDEn-N, or no path when at high altitude.

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing, when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec). Changing default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to an abusive rate.
* '''Stationary Mobile''' : Should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altititude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-24T00:49:16Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing, when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec). Changing default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon settings to an abusive rate.
* '''Stationary Mobile''' : Should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altititude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-24T00:46:24Z

Radionerd: /* Recommended timing settings for ''mobile'' */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path (WIDE1-1) would be about the fastest TX rate a local network could handle. Many courteous users set 3 to 10 minute beacons, with a routine two hop path (WIDE1-1,WIDE2-1). Smart Beaconing is recommended over timed beaconing, when available. Powering Trackers from the Ignition switch or using a Power off timer is recommended. Leaving a mobile tracker on while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs], several "ob-users" (Oblivious-Users) let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individuals to decide what settings are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec). Changing default settings could be detrimental to the network. If the [http://aprs.fi/?lat=37.7164&lng=-121.6846&mt=m&z=9&timerange=10800 Bay Area APRS.FI] map shows someone's tracks as a constant red line, they might have changed smart beacon setting to an abusive rate.
* '''Stationary Mobile''' : Should TX similar to fixed stations, once or twice an hour is courteous, and will keep you on the maps. A stationary mobile that's beacon rate is at once every 10 minutes could be considered a spammer, that's 144 worthless beacons in 24Hrs. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting APRS DC power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS. Trimming long messages, telemetry, Altititude, TX delays... Can also increase successful packets.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-23T23:41:08Z

Radionerd: /* Solution: Localizing Paths */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, many trap down to WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby. Hopefully not at the expense of others.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-22T08:13:21Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, some high level digis even trap WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-22T02:19:47Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, some high level digis even trap WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a '''S#''' to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn-N, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-22T02:17:03Z

Radionerd: /* Recommended timing settings for ''fixed, non-moving'' stations */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, some high level digis even trap WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a S# to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn-N, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-22T02:16:08Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, some high level digis even trap WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended no more than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off, set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended not more often than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a S# to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn-N, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-21T08:30:33Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, some high level digis even trap WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended no more than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. WIDE2-1 or NCA1-1 is adequate for high level Digis. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended no more than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : WIDEn-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a S# to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn-N, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-21T06:22:49Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, some high level digis even trap WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended no more than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended no more than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : Widen-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a S# to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn-N, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State could trap it to one more hop by using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit=2, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.

NorCal APRS Regional Info

2009-12-21T05:48:36Z

Radionerd: /* Recommended settings for Digipeaters */

== San Francisco Bay Area ==

=== Summary Information ===
* Operating Frequency: 144.390 MHz
* SSID Protocol: Most users follow the "new protocol"; refer to [[SymbolsAndSSIDs|Symbols and SSIDs]] page.
* Local Coordination: Informal, mostly via [http://groups.yahoo.com/group/ca_aprs/ California APRS Users Group (Yahoo group)]
* Local Monitoring and Info: [http://www.norcalaprs.net/usagex.html Northern California APRS Information]

=== Overview ===
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.

=== Challenges ===
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.

==== Solution: Digipeater Siting Strategy ====
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.

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.

==== Solution: Receive-Only IGate Strategy ====
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.

==== Solution: Localizing Paths ====
Even with the [http://www.aprs.org/fix14439.html "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. Digis and other fixed stations are encouraged to beacon local information locally, with no path, and beacon position with a path once an hour. Most digies trap abusive paths, some high level digis even trap WIDE3-3. Fill-in digis usually only respond to only WIDE1-1, and 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. Commuters in areas that have I-gates and digis nearby ''could'' simply use WIDE1-1. Taming paths and timing to our intended audience shows good amateur practice, and can help alleviate network overload. We have helpful web sites like [http://aprs.fi/?c=raw&call=&limit=1000 APRS.FI RAW] that make it easy to examine our own settings. And [http://www.norcalaprs.net/usagex.html APRS HOGS] to help those of us within it's ear shot to attempt to stay off the top of the "Hogs" list. These tools can help us find the settings that work best for our own needs. Ultimately each individual chooses the setting that they require for their own enjoyment of the hobby.

=== Recommended path settings for '''''mobile stations''''' stations ===

* '''WIDE1-1,WIDE2-1''' : Two hops in all directions with potential to use fill-in digis. Best routine, and for events.
* '''WIDE1-1,WIDE2-2''' : Three hops in all directions. Not normally required; use is discouraged. (Potential to be propagated out a thousand miles, by up to 36 distant digipeaters).
* '''WIDE1-1''' : "Commuters" may find that a short mobile path of WIDE1-1 is adequate for their needs.
* '''NCA1-1''' : ''or NCA2-2'' can be used if you don't travel outside the Northern California (NCA) region. No access to fill-ins''

=== Recommended path settings for '''''fixed, non-moving''''' stations ===

* '''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.
* '''WIDE2-2''' : Two hops in all directions... recommended maximum for routine use in most areas.
* '''WIDE3-3''' : Three hops in all directions. ''Not normally required, use is discouraged, many digis trap WIDE3-3 and higher''
* '''NCA1-1''' : ''or NCA2-2 may be used.'' NCA1-1 is more courteous, and is equivalent to WIDE2-1.
* '''WIDE1-1''' : Use is discouraged for fixed stations unless your target is a fillin digi.
RELAY and WIDE and TRACE and TRACEn-N are obsolete and ''strongly'' discouraged.

=== Recommended timing settings for ''mobile'' ===
* '''Position Beacon''' : While moving, a beacon rate of once a minute, with a single hop path, would be about the minimum required for most users. Many courteous users set 3 to 10 minutes, with a routine two hop path. Power to Ignition switch or timer is recommended. Leaving a mobile tracker on, while stationary, with a TX rate of more than once or twice an hour can cause a great load on our RF network over time. Look at the top few users at [http://www.norcalaprs.net/usagex.html APRS Hogs] , several users let their TNC's transmit at a rapid rate, 24/7. It wouldn't take many ab''users'' to overload our precious frequency, that we all have to share. Ultimately it's up to individual users to decide what setting are required for their intended audience.
* '''Smart Beacon''' : [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits beacons depending on speed and direction. The [http://info.aprs.net/index.php/SmartBeaconing default] settings are courteous: (Slow 5mph, Slow TX 1800sec, Fast 60mph, Fast TX 90sec, Min turn angle 30, Turn slope 255, Min turn time 5 sec)
* '''Stationary Mobile''' : Should be similar to fixed stations, once every 10 minutes is about the minimum, that's 144 beacons in 24Hrs. Once or twice an hour is courteous, and will keep you on the maps. Properly setup [http://www.hamhud.net/hh2/smartbeacon.html SmartBeaconing™] transmits a packet once every 30 minutes while stationary, which compensates for the sometimes "spastic" beaconing while corner pegging. Setting power to vehicle's ignition switch, or use of a timed power off relay is advised to limit needless QRM.
* '''Status Message''' : Many Trackers can be set to send a status message once every 10 position beacons, instead of every beacon. This allows quicker air time, less chance of packet collisions, and an increase in successful packets to APRS-IS.
* '''TX Delay''' : In the old days 300 milliseconds was the standard. Today in the age of PIN diodes 180 milliseconds should be more than enough.
* '''MIC-E''' : Compression can cut air time by more than 50%. Short packet bursts have a much greater success rate, especially in busy Northern California.

=== Recommended timing settings for ''fixed, non-moving'' stations ===

* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path.
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended no more than once every 10 minutes without a path. Keep your local info ''local''.
* '''TX Delay''' : 180 Milliseconds is recommended.

=== Recommended settings for Digipeaters ===
* '''Carrier Detect''' Software detect is superior to using squelch, it's fast, (squelch off set to noise all the time) no squelch delays on decode, or TX delays from noise.
* '''Digi Wait''' : Set digi wait to minimum: Kantronics UIDWait=OFF || TNC-2 UIDIGI PPERSISTANCE=255 and SlotTime=1 || OT2 SLOT not less than 1 || TT4 PPERsist=1 SLOtime=1
* '''Duplicate''' Dup limit 30 seconds is recommended for WIDEn-N digis.
* '''Preempt''' is recommended on WIDEn-N Digis that have aliases like: SSn-N or SAR.
* '''Position Beacon''' : Position beacons with a path of WIDEn-N, or NCAn-N, are recommended once an hour, any additional position beacons with no path. (The latest recommended digi settings from Bob, WB4APR are: [http://www.aprs.org/newN/WIDE1-1settings.txt Fillin] || [http://www.aprs.org/kpc3/kpc3+82WIDEn.txt KPC-3 ver 8.2] || [http://www.aprs.org/kpc3/kpc3+WIDEn.txt KPC-3+] || [http://www.qsl.net/n8deu/uidigi_eprom_settings.htm UIDIGI ver 1.9] || [http://wiki.argentdata.com/index.php/Digipeater_Setup OT2])
* '''Status-Local info''' : Repeaters, EchoLink, and IRLP objects are recommended no more than once every 10 minutes without a path. Keep your local info local. [http://www.aprs.org/info/echo-irlp-win.txt APRS Objects for Echolink/IRLP and WinLink]
* '''Symbols''' : Widen-N Digis are recommended to be updated to support NCAn-N and display a Green star symbol with an "S" overlay. Fillins Have a Green Star with a "1" overlay. The overlay and digi symbol are placed in the position beacon after the Lat & Long. The following position has a S# to indicate a S overlay Digi. (!DDMM.hhN'''S'''DDDMM.hhW'''#'''PHGphgdr/ W2, NCAn-N, We finally updated Intermod Ridge Digi to New Paradigm settings A=003900). Helpful links:[http://wa8lmf.net/aprs/APRS_symbols.htm Symbol Chart] || [http://www.apritch.myby.co.uk/phgrcalc.htm Good PHGR calculator]
* '''TX Delay''' : 180 Milliseconds is recommended.
* '''Trapping''' : Trap abusive paths from near or distant users. Settings will depend on individual geographic factors. Many digis are now trapping down to WIDE3-3, some high level digis even trap WIDE2-2. This gives abusive users one hop. A Northern California digi that constantly receives QRM from a WIDE5-3 beacon from out of State can trap WIDE5-3. using the UIDIGI command: KPC-3 (UIDIGI ON, WIDE2-2, WIDE3-3, WIDE3-2, '''WIDE5-3''') Kantronics TNC's allow four trappable paths. || TNC-2 UIDIGI ver1.9 can have up to eight trappable paths: (UIDigiCall = WIDE5-4, '''WIDE5-3''', WIDE4-4, WIDE4-3, WIDE4-2, WIDE3-3, WIDE3-2, WIDE2-2). || OpenTracker2's can trap hops of any WIDEn using HOPlimit=2, or set up to eight valid aliases with limits. || TinyTrack4's can allow up to three valid aliases:(WIDE1,WIDE2,NCA1) ignoring abusive paths.
* '''Emergency Paths''' TEMP and SSn-N paths are usually not trapped, or restrained. New Paradigm digis in Northern California with a "S" overlay will Digipeat NCAn-N. An emergency message could be propagated throughout Northern California by using a Path of NCA3-3. A path of NCA3-3,SCA3-3 will blanket the whole State, not advisable for routine traffic. TEMP is encouraged to be enabled in [http://www.aprs.org/newN/WIDE1-1settings.txt fillin digis], Home stations, and mobiles. It can be enabled in [http://aprs.org/TEMPn-N.html Kenwood D700 radios]. This gives us another backup network path. Routine use of TEMP is discouraged on 144.390 MHz, except on Field Day or during emergencies.