APRSWiki - User contributions [en]

User:Hardaker

2012-02-02T04:02:15Z

Hardaker:

Just another HAM with not enough time to do everything he wants with the hobby. I've written some [http://www.hamtools.org/ software] and even wrote the APRS decoder in the [[marble]] mapping system. I also maintain the server for the [http://www.amateur-radio-wiki.net http://www.amateur-radio-wiki.net] site.

User:Hardaker

2012-02-02T04:02:01Z

Hardaker:

User talk:KM5VY

2012-02-02T03:59:39Z

Hardaker: /* Your Messages */

Feel free to leave messages for me here. Please sign them using the little signature button or two dashes followed by four tildes. --[[User:KM5VY|KM5VY]] 12:36, 14 August 2007 (Pacific Daylight Time)

===Your Messages===

FYI, I switched the amateur-radio-wiki.net wiki to a local set of questions for creating accounts that should be easy to answer for amateurs but much more difficult to spammers. My spam has dropped to near nothing now. You might consider a similar change and using ConfirmEdit's self-written-question ability. [[User:Hardaker|Hardaker]] 07:27, 31 January 2012 (PST)

Ok, I'd be happy to send him some questions. Got a contact email for me? [[User:Hardaker|Hardaker]] 16:36, 1 February 2012 (PST)

Gotcha; thanks. I wasn't sure of his user name. [[User:Hardaker|Hardaker]] 19:59, 1 February 2012 (PST)

User talk:KM5VY

2012-02-02T00:36:30Z

Hardaker:

User talk:KM5VY

2012-01-31T15:27:46Z

Hardaker:

Software

2011-02-09T17:59:08Z

Hardaker: /* DOS */

== APRS Client Applications ==
=== Apple Mac OS X ===
* [http://www.winaprs.com/ MacAPRS] Two versions, one for <=OS9, one for OS X
* [http://homepage.mac.com/kd6cji/ Packetograph]
* [[XASTIR]]

=== Apple iOS ===
* [http://itunes.apple.com/us/app/aprs/id341511796?mt=8 APRS by Gary Huntress]
* [http://itunes.apple.com/gb/app/ham-tracker/id406552499?mt=8 Ham Tracker]
* [http://itunes.apple.com/us/app/iaprs/id314705586?mt=8 iAPRS]
* [http://itunes.apple.com/us/app/ibcnu/id314134969?mt=8 iBCNU]
* [http://itunes.apple.com/us/app/ilocator/id351058111?mt=8 iLocator]
* [http://itunes.apple.com/us/app/openaprs/id360574554?mt=8 Open APRS]
* [http://itunes.apple.com/us/app/pocketpacket/id336500866?mt=8 Pocket Packet] & [http://koomasi.com/pocketpacket/ Site koomasi.com]
* [http://itunes.apple.com/us/app/ship-finder/id319726819?mt=8 Snip Finder]
* [http://itunes.apple.com/us/app/ship-finder-free/id324177409?mt=8 Snip Finder Free]

* [http://itunes.apple.com/ru/app/aprsnow/id366006368?mt=8 APRSNow]
* [http://itunes.apple.com/ru/app/openaprs-xl/id363666470?mt=8 OpenAPRS-xL]
* [http://itunes.apple.com/ru/app/ship-finder-hd-free/id364616485?mt=8 Ship Finder HD Free]
* [http://itunes.apple.com/ru/app/ship-finder-hd/id363360636?mt=8 Ship Finder HD]

=== Android ===
* [http://wiki.github.com/ge0rg/aprsdroid/ APRSdroid] - APRS-IS Tracker on Android
* [http://aobajoke.no-ip.org/~ja7ude/japanese/u2aprs10/indexe.html U2APRS] - APRS Client

=== BlackBerry OS ===
* [http://aprsbb.bluearray.net/ APRSBB]

=== DOS ===
* [[APRSdos]]

=== Linux and Unix ===

* [http://edu.kde.org/marble/ Marble] the KDE Desktop Globe

=== Maemo ===
* [http://maemo-mapper-aprs.blogspot.com/2009/03/maemo-mapper-26-is-now-available-with.html Maemo Mapper 2.6 APRS]

=== Palm OS ===
* [[SmartPalm]]

=== Windows ===
* [[AGWTracker]]
* [[APRSAndGoogleEarth]]
* [[APRSISCE]] - APRS IS CE Client for Windows Mobile and Win32
* [[APRSParser]]
* [[APRS+SA]] - Discontinued?
* [http://www.aprspoint.com/ APRSPoint]
* [[APRSSCS]]
* [http://www.eoss.org/wbaltrak/ BalloonTrack]
* [http://www.gpsflight.com/Main/Software.htm GPSTeam Pro] New for 2008
* [http://www.aprs-is.net/javAPRS/ JavAPRS]
* [http://f6cte.free.fr/index_anglais.htm MultiPSK] Runs HF and VHF APRS "stand-alone" (does not require AGW Packet Engine)
* [http://www.radio-active.net.au/web/tracking/netaprs.html NetAPRS]
* [[OziAPRS]]
* [http://www.cplus.org/rmw/english1.html RadioMobile]
* [http://www.kr1st.com/cybiko.htm UIMessenger]
* [[UI-View32|UI-View]] - Registration status changed to Donationware
* [[USAPhotoMaps]]
* [[WinAPRS]]
* [http://www.winaprs.org X-APRS] - Discontinued

=== Windows CE/Mobile ===
* [[APRS-Go]] - [http://aprsgo.com/ aprsgo.com]
* [[APRSce|APRS/CE]]
* [[APRSISCE]] - APRS IS CE Client for Windows Mobile and Win32
* [http://www.cplus.org/rmw/english1.html PocketAPRS] - Discontinued
* [http://www.mgmaps.com/ Mobile GMaps] - mgMaps for mobile devices. http://wap.mgmaps.com/12/index-all.html

== APRS Server Applications (digipeating, igate, etc) ==
* [http://sourceforge.net/projects/aprsd/ Aprsd] Internet Server
* [http://pakettiradio.net/aprsg/ Aprsg] - software for Unix-like operating systems and Microsoft Windows
* [http://aprsdigi.sourceforge.net/ aprsdigi] Digipeater
* [http://www.qsl.net/digi_ned/ DigiNED] Digipeater for DOS and Linux
* [http://wiki.ham.fi/Aprx.en aprx] A lightweight igate and digipeater for Linux and Unix
* [http://russnelson.com/gpsd/ Gpsd] A daemon for serving up [[GPS]] data, allows multiple apps to use one [[GPS]]
* [[javAPRSSrvr]] Internet Server written in Java
* [http://meteo.othello.ch Meteo] Weather station Daemon
* [http://melhuish.info/simon/projects/oww/ One Wire Weather] Weather Station Daemon
* [http://www.lavrsen.dk/twiki/bin/view/Open2300 Open2300] Weather Station Daemon
* [http://wetnet.net SLUG] Firmware for Linksys NSLU2 Hardware
* [http://wx200d.sourceforge.net wx200d] Weather Station Daemon
* [http://aprskml.dev.java.net APRS KML server] for use with Google Earth for Mapping
* [http://www.aprs4r.org/cgi-bin/trac.cgi/wiki/WikiStart APRS-4R server] for use with openWRT on embedded devices. Includes [[Digipeater]], [[i-Gate]] and mapping (with google Earth) functionality.

== APRS related X.25 Software ==
*[[AGWPE|AGWPE AGW Packet Engine]] (MS-Windows soundcard [[TNC]])
*[http://www.on7lds.net/ldsped/index.html ldsped: AGWPE replacement for Linux]
*[[APRS2ATM]]
*[http://www.roadfacts.com/software/dmapper/dmapper.htm DMapper]
*[[LinuxAX25|Linux AX.25 Kernel Support]]
*[[LinuxSoundmodem|Linux Soundmodem]] (sound card [[TNC]])
*[http://wiki.ampr2.net/nwaprs/SearchAndRescue SAR-Related methods to do APRS + Topo maps]
*[http://www.ve1fis.net/frankenrouter-2 Soundmodem running on ASUS WL-520gU router and OpenWRT]

== Other ==
* [[TH-D7-APRS]] - for Mac OS X & [[Kenwood TH-D7]]

== Summary of APRS Clients ==
*[http://www.eskimo.com/~archer/aprs_capabilities.html APRS Client Capabilities Chart]

[[Category:Software|*]]

NorCal APRS Regional Info

2010-04-16T17:41:29Z

Hardaker: /* Challenges */ fix link

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