APRSWiki - User contributions [en]

Dire Wolf

2012-11-20T03:13:05Z

Wb2osz:

'''Dire Wolf'''

Dire Wolf is a software modem and APRS encoder/decoder for both Microsoft Windows and Linux. It can be used stand-alone to receive APRS messages or as a digipeater. It can also be used as a virtual TNC for other applications such as APRSIS32, UI-View32, Xastir, and many others. Both KISS and AGWPE protocols are supported for use by applications.

== Links ==
* [http://home.comcast.net/~wb2osz/site/ Details and download]

[[Category:Software]]

Dire Wolf

2012-11-20T03:07:35Z

Wb2osz:

Dire Wolf is a software modem and APRS encoder/decoder for both Microsoft Windows and Linux. It can be used stand-alone to receive APRS messages or as a digipeater. It can also be used as a virtual TNC for other applications such as APRSIS32, UI-View32, Xastir, and many others. Both KISS and AGWPE protocols are supported for use by applications.

== Links ==
* [http://home.comcast.net/~wb2osz/site/] - Details and download.

[[Category:Software]]

Dire Wolf

2012-11-20T03:06:14Z

Wb2osz: /* Links */

Dire Wolf is a software modem and APRS encoder/decoder. It can be used stand-alone to receive APRS messages or as a digipeater. It can also be used as a virtual TNC for other applications such as APRSIS32, UI-View32, Xastir, and many others. Both KISS and AGWPE protocols are supported for use by applications.

== Links ==
* [http://home.comcast.net/~wb2osz/site/] - Details and download.

[[Category:Software]]

Dire Wolf

2012-11-20T03:04:52Z

Wb2osz: Created page with "== Links == * [http://home.comcast.net/~wb2osz/site/] - Details and download. Category:Software"

== Links ==
* [http://home.comcast.net/~wb2osz/site/] - Details and download.

[[Category:Software]]

SoundCardInterfaces

2012-11-20T02:59:09Z

Wb2osz:

There is a lot of information out on the web about soundcard/radio interface hardware.
If you decide to use any kind of software that employs your computer's soundcard as a TNC,
you will need to buy or build such an interface. (If you use a serial or USB connected
external TNC then you don't need a soundcard interface.)

This device is '''not''' mode or band specific. You can use the same
device that you employ for other digital modes (PSK, slowscan, RTTY, etc.), as long
as it will connect to the radio and the computer combination that you are going to use for APRS.
For example: if you use your Icom 706 mkIIG (an all-mode HF through 70cm rig) for PSK-31
on HF, you probably can use the same soundcard/radio interface device for APRS. Just
set up the radio for the mode, band and frequency used in your area for APRS operation, and
run your APRS software instead of your PSK software.

----
The task is to connect the audio inputs and outputs between the radio and
soundcard. Solutions range from direct connection to electrically isolated
systems using audio transformers or optical coupling. Some provision for
keying the radio is also useful. Usually this involves a connection to the
computer via serial port (USB or rs232) or parallel port.

This is a good opportunity for doing a little junkbox homebrewing.
The guts of old computer modems usually contain audio isolation transformers,
rs-232 ports and other hardware bits.

For an off-the-shelf solution,
[http://www.westmountainradio.com/ West Mountain Radio's] RigBlaster units
are popular.

----
As to software for doing APRS over a soundcard, investigate [[LinuxSoundmodem]] for Linux or Solaris, and [[AGWPE]] for Windows. [[Dire Wolf]] works on both Windows and Linux. All of these will do the tone encoding/decoding, then you need a compatible APRS program to connect to them.

[[Category:Hardware]]

Talk:Digipeater

2012-11-20T02:48:58Z

Wb2osz:

Digipeater example

I'm 99% sure I'm wrong about the astrix usage. I'm hoping someone with
authoritative knowledge can fix that up.

ChrisW0EP

----

The usual convention is for only the last used digipeater field to marked with an asterisk.

John WB2OSZ

Digipeater

2012-11-20T02:46:31Z

Wb2osz: Improved technique for digipeater tracing.

==Digipeater==

===Definition===

A Digipeater is a station that does digital repeating. Unlike full-duplex
VHF/UHF voice repeaters a digipeater will
receive a packet, process it, and retransmit on the same frequency. A digipeater
which operates on multiple frequencies is called a [[gateway]].

In classic packet radio each such hop had to be explicitly included in the packet by the sender at origination. In APRS all digipeaters use generic aliases. The sender does not have to know the callsign of the digipeater but just indicate the number of hops he wants to go.

Digipeating is defined in AX.25 specification document.
An initiating station can include in each packet a list of intermediate stations which are supposed to digipeat the packet, passing it on toward the desired destination. The list of intermediate stations is called the [[Paths|path]]. Stations receiving packets examine the path of received packets. Using it's configuration information a receiving station can decide if a packet is a candidate for digipeating. When this is true the packet addressing information is modified slightly and the modified packet is transmitted.

The idea is to get packets to propagate outward from the initiating station... but not so far as to be an unnecessary burden on the system and surrounding users. The practical range of a VHF 1200 baud APRS channel is estimated to include the nearest 60 stations (approximately), called the [[AlohaCircle|Aloha Circle]].

===The Digipeating Path and Development of WIDEn-N===

If there are multiple aliases in the PATH they are examined in the order left-to-right. An asterisk '''*''' is used to show that a element in the path is no longer active. In the path '''ABCD*,EFGH,IJKL''' only the '''EFGH''' path element is active because the previous path element '''ABCD*''' is "used up". And the '''IJKL''' is not yet active because it is not the left-most active field.

When APRS was first invented the generic calls of RELAY, WIDE and TRACE were used for all digipeaters, but there was no duplicaton suppression mechanism. Paths beyond 2 hops could fold back ending up with dozens of unwanted duplicate packets. By 1994 a WIDEn-N and TRACEn-N scheme was proposed by WB4APR. It was finally implemented in 1998 by Kantronics, providing perfect dupe suppression and becoming the standard and most efficient way of operating. When a digipeater sees an "n-N" packet, it digipeats it and decrements the "N" by 1. This continues until the "N" is zero.

Up until 2004 APRS in the USA was using a mixture of the old generic paths and the new n-N type paths and the presence of the old paths was causing terrible QRM. TO combat these inefficiencies, WB4APR launched the New-N Paradigm to phase out all the old legacy paths and greatly simplify paths to simply WIDEn-N and to make these paths 100% traceable. For current recommended paths, see the [[Paths]] page.

===Local and Wide Digipeaters===

As with voice VHF repeaters, digipeaters are installed in places of prominence to allow for extended range. If a small station can "hit" the digipeater, his packet will go much farther then his own station can reach. Local digipeaters (called '''FILL-IN''' digipeaters) are usually located in blind spots where mobiles are unable to be heard by the main digipeaters. THese '''FILL-IN''' digis only respond to the '''WIDE1-1''' path. This keeps them from needlessly repeating all other traffic from the high digis.

===Digipeating example===

Station ''ABCD'' sends a packet with path '''WIDE1-1, WIDE2-2'''.

A nearby station ''EFGH'' is configured to respond to '''WIDE1-1''', so he does so. He decrements the second number (the SSID) making '''-1''' into '''-0''' and retransmits the packet with path '''EFGH,WIDE1*, WIDE2-2'''. The convention is that -'''0''' is not displayed.
A WIDEn-N digipeater will also insert its own callsign into the path before the WIDEn-N path element that it acted on so that the path is traceable through all the digipeaters that relayed it. In this example the packet now includes '''EFGH''' showing it passed through station ''EFGH''.

Another station ''IJKL'' (configured to respond to '''WIDEn-N''') picks it up and sends it out with '''EFGH,WIDE1,IJKL*,WIDE2-1'''. The destination '''WIDE2-1''' still has one hop so it is not yet marked with a '''*''' and this packet is available for further digipeating.

Then station ''MNOP'' (configured to respond to '''WIDEn-N''') hears it. Because '''WIDE2-1''' is still active, he repeats it back out as '''EFGH,WIDE1,IJKL,MNOP,WIDE2*'''. Since there are no more active path elements any digipeating station receiving that packet will not repeat it.

Again, the list of destinations are consumed in left-to-right order. Path tracing allows digipeaters to insert their callsigns prior to the active path as a way of tracking the path the packet actually took through the system. The numbers after the dash in the WIDEn-N format are decremented until they reach '''-0''' and disappear altogether. The last destination that is used-up is marked with a '''*'''.

This technique has the unfortunate property that the resulting path does not indicate what actually happened along the way. '''EFGH,WIDE1,IJKL,MNOP,WIDE2*''' looks like the packet was retransmitted 5 times: first by EFGH, then by some unknown station not configured for tracing, then by IJKL, then by MNOP, and finally by some other unknown station that is not configured for tracing. This makes it difficult to figure out what stations can hear each other when a couple apparent unknown stations end up in the list.

===A Better Digipeating technique===

What we would really like to see is a final path of '''EFGH,IJKL,MNOP*''' which clearly reflects the path taken. This is easy to achieve by making a small change to the tracing algorithm. When the active path hop count (ssid) is 2 or more, we decrement it, and insert the digipeater name, just like before. However, when the hop count is 1, it is '''replaced''' by the digipeater name.

As in the previous example, Station ''ABCD'' sends a packet with path '''WIDE1-1, WIDE2-2'''.

A nearby station ''EFGH'' is configured to respond to '''WIDE1-1''' and replaces that part with its own call resulting in '''EFGH*,WIDE2-2'''.

Another station ''IJKL'' (configured to respond to '''WIDEn-N''') picks it up and sends it out with '''EFGH,IJKL*,WIDE2-1'''.

Then station ''MNOP'' (configured to respond to '''WIDEn-N''') hears it repeats it back out as '''EFGH,IJKL,MNOP*'''. The result accurately reveals the path taken and it is easy to create maps of what stations can hear each other.

{| class="wikitable"
|-
! !! Unconditional insert !! More intelligent insert or replace
|-
| Original path || WIDE1-1,WIDE2-2 || WIDE1-1,WIDE2-2
|-
| After 1 hop || EFGH,WIDE1*,WIDE2-2 || EFGH*,WIDE2-2
|-
| After 2 hops || EFGH,WIDE1,IJKL*,WIDE2-1 || EFGH,IJKL*,WIDE2-1
|-
| After 3 hops || EFGH,WIDE1,IJKL,MNOP,WIDE2* || EFGH,IJKL,MNOP*
|-
| Implemented by || KPC-3, TM-D710A || Dire Wolf soundcard TNC
|}

===Dupe Checking===

You might be thinking, "Hey, what's to keep ''EFGH'' from hearing that packet that ''IJKL'' sent out? ''EFGH'' would send it out again, ''IJKL'' would pick it up and send it out again. This thing could just loop around and not really get anywhere." To solve this, all modern digipeaters have ''dupe-checking'' algorithms.

'''WIDEn-N''' Digipeaters have some '''memory''' of what has been transmitted them recently and drops duplicates. This is known as [[DuplicateChecking|dupe checking]]. Otherwise they would spend a lot of their time just booming packets back and forth amongst each other and the little pip-squeak tracker stations would never be heard at all. The dupe checking algorithm in the digipeater will act to suppress re-transmission of packets that have recently been transmitted. The main parameter of this '''memory''' a time specification i.e. the number of seconds that transmitted packets are kept around for comparing to candidates for digipeating.

Duplicates are detected by comparing the source, destination, and information fields. The digipeater path is not part of the comparison. A digipeater should not re-transmit something it originated or already digipeated. This will also limit the rate of identical packets that are being generated at a rapid rated. Suppose some station was sending 10 identical packets per second. A digipeater configured to remember packets for 30 seconds will cut this rate down to 2 per minute.

Other details of the ''New-N Paradigm'' include settings to TRAP abusive user paths with large values of '''N'''. Usually only '''WIDE2-2''' is recommended in most high density areas and surrounding territory.

=== Suggested Setup for a Mobile/Fixed APRS Station ===

Please read suggested setups for [[Paths]].

=== Other discussion ===
Steve WA8LMF has a parallel discussion of digipeaters and [http://www.wa8lmf.net/DigiPaths/ digipaths].
Of particular interest is the [http://www.wa8lmf.net/DigiPaths/NNNN-Digi-Demo.htm animation] of the New-N Paradigm.

== Links ==
* [http://www.youtube.com/watch?v=zTNjUllHbKg Video: Digipeater on TM-D710] - Digipeater on [[TM-D710]]

This video has several errors.
3:57 - Voice Alert - 614
This has nothing to do with the voice module. [http://info.aprs.net/index.php/VoiceAlert VoiceAlert]

4:03 - Digipeat (MyCal) - 616
This is digipeating stations with paths like MYCALL,WIDEn-N
In this example MYCALL is N0AOL, turning on menu 616 enables stations to use N0AOL,WIDE2-1 so that this station is digipeating it.
Could be used as a "private" digipeater i.e if you have a TH-D7 and you need to use your home station to reach a digipeater.

4:44 - UICHECK - 617
This is a duplicate check so that it's not retransmitting packets sent i.e every 10sec

6:59 - UIFLOOD - 619
He is saying that his station is not going outside Colorado. He is activating a SS digipeater so that people using CO instead of WIDEn-N is been digipeted from this station. This setting doesn't limit the propagation of his beacon.

7:15 - UITRACE - 620
This has nothing to do with messaging. This enables a tracable digipeater. This can be default ON if the alias is TEMP. Now people using TEMP in their path is going trough this digipeater.
Can also be used to make a tracable WIDEn-N digi if you replace TEMP with WIDE.

A nice explanation of the digi functions can be found on: [http://www.kenwood.com/i/products/info/amateur/pdf/TM-D710AE_IDM_R1.pdf In-depth Manual]

So no offence to the author of this video :o)

Digipeater

2012-11-20T02:28:59Z

Wb2osz: /* Digipeating example */

==Digipeater==

===Definition===

A Digipeater is a station that does digital repeating. Unlike full-duplex
VHF/UHF voice repeaters a digipeater will
receive a packet, process it, and retransmit on the same frequency. A digipeater
which operates on multiple frequencies is called a [[gateway]].

In classic packet radio each such hop had to be explicitly included in the packet by the sender at origination. In APRS all digipeaters use generic aliases. The sender does not have to know the callsign of the digipeater but just indicate the number of hops he wants to go.

Digipeating is defined in AX.25 specification document.
An initiating station can include in each packet a list of intermediate stations which are supposed to digipeat the packet, passing it on toward the desired destination. The list of intermediate stations is called the [[Paths|path]]. Stations receiving packets examine the path of received packets. Using it's configuration information a receiving station can decide if a packet is a candidate for digipeating. When this is true the packet addressing information is modified slightly and the modified packet is transmitted.

The idea is to get packets to propagate outward from the initiating station... but not so far as to be an unnecessary burden on the system and surrounding users. The practical range of a VHF 1200 baud APRS channel is estimated to include the nearest 60 stations (approximately), called the [[AlohaCircle|Aloha Circle]].

===The Digipeating Path and Development of WIDEn-N===

If there are multiple aliases in the PATH they are examined in the order left-to-right. An asterisk '''*''' is used to show that a element in the path is no longer active. In the path '''ABCD*,EFGH,IJKL''' only the '''EFGH''' path element is active because the previous path element '''ABCD*''' is "used up". And the '''IJKL''' is not yet active because it is not the left-most active field.

When APRS was first invented the generic calls of RELAY, WIDE and TRACE were used for all digipeaters, but there was no duplicaton suppression mechanism. Paths beyond 2 hops could fold back ending up with dozens of unwanted duplicate packets. By 1994 a WIDEn-N and TRACEn-N scheme was proposed by WB4APR. It was finally implemented in 1998 by Kantronics, providing perfect dupe suppression and becoming the standard and most efficient way of operating. When a digipeater sees an "n-N" packet, it digipeats it and decrements the "N" by 1. This continues until the "N" is zero.

Up until 2004 APRS in the USA was using a mixture of the old generic paths and the new n-N type paths and the presence of the old paths was causing terrible QRM. TO combat these inefficiencies, WB4APR launched the New-N Paradigm to phase out all the old legacy paths and greatly simplify paths to simply WIDEn-N and to make these paths 100% traceable. For current recommended paths, see the [[Paths]] page.

===Local and Wide Digipeaters===

As with voice VHF repeaters, digipeaters are installed in places of prominence to allow for extended range. If a small station can "hit" the digipeater, his packet will go much farther then his own station can reach. Local digipeaters (called '''FILL-IN''' digipeaters) are usually located in blind spots where mobiles are unable to be heard by the main digipeaters. THese '''FILL-IN''' digis only respond to the '''WIDE1-1''' path. This keeps them from needlessly repeating all other traffic from the high digis.

===Digipeating example===

Station ''ABCD'' sends a packet with path '''WIDE1-1, WIDE2-2'''.

A nearby station ''EFGH'' is configured to respond to '''WIDE1-1''', so he does so. He decrements the second number (the SSID) making '''-1''' into '''-0''' and retransmits the packet with path '''EFGH,WIDE1*, WIDE2-2'''. The convention is that -'''0''' is not displayed.
A WIDEn-N digipeater will also insert its own callsign into the path before the WIDEn-N path element that it acted on so that the path is traceable through all the digipeaters that relayed it. In this example the packet now includes '''EFGH''' showing it passed through station ''EFGH''.

Another station ''IJKL'' (configured to respond to '''WIDEn-N''') picks it up and sends it out with '''EFGH,WIDE1,IJKL*,WIDE2-1'''. The destination '''WIDE2-1''' still has one hop so it is not yet marked with a '''*''' and this packet is available for further digipeating.

Then station ''MNOP'' (configured to respond to '''WIDEn-N''') hears it. Because '''WIDE2-1''' is still active, he repeats it back out as '''EFGH,WIDE1,IJKL,MNOP,WIDE2*'''. Since there are no more active path elements any digipeating station receiving that packet will not repeat it.

Again, the list of destinations are consumed in left-to-right order. Path tracing allows digipeaters to insert their callsigns prior to the active path as a way of tracking the path the packet actually took through the system. The numbers after the dash in the WIDEn-N format are decremented until they reach '''-0''' and disappear altogether. The last destination that is used-up is marked with a '''*'''.

This technique has the unfortunate property that the resulting path does not indicate what actually happened along the way. '''EFGH,WIDE1,IJKL,MNOP,WIDE2*''' looks like the packet was retransmitted 5 times: first by EFGH, then by some unknown station not configured for tracing, then by IJKL, then by MNOP, and finally by some other unknown station that is not configured for tracing. This makes it difficult to figure out what stations can hear each other when a couple apparent unknown stations end up in the list.

===A Better Digipeating technique===

What we would really like to see is a final path of '''EFGH,IJKL,MNOP*''' which clearly reflects the path taken. This is easy to achieve by making a small change to the tracing algorithm. When the active path hop count (ssid) is 2 or more, we decrement it, and insert the digipeater name, just like before. However, when the hop count is 1, it is *replaced* by the digipeater name.

As in the previous example, Station ''ABCD'' sends a packet with path '''WIDE1-1, WIDE2-2'''.

A nearby station ''EFGH'' is configured to respond to '''WIDE1-1''' and replaces that part with its own call resulting in '''EFGH*,WIDE2-2'''.

Another station ''IJKL'' (configured to respond to '''WIDEn-N''') picks it up and sends it out with '''EFGH,IJKL*,WIDE2-1'''.

Then station ''MNOP'' (configured to respond to '''WIDEn-N''') hears it repeats it back out as '''EFGH,IJKL,MNOP*'''. The result accurately reveals the path taken and it is easy to create maps of what stations can hear each other.

===Dupe Checking===

You might be thinking, "Hey, what's to keep ''EFGH'' from hearing that packet that ''IJKL'' sent out? ''EFGH'' would send it out again, ''IJKL'' would pick it up and send it out again. This thing could just loop around and not really get anywhere." To solve this, all modern digipeaters have ''dupe-checking'' algorithms.

'''WIDEn-N''' Digipeaters have some '''memory''' of what has been transmitted them recently and drops duplicates. This is known as [[DuplicateChecking|dupe checking]]. Otherwise they would spend a lot of their time just booming packets back and forth amongst each other and the little pip-squeak tracker stations would never be heard at all. The dupe checking algorithm in the digipeater will act to suppress re-transmission of packets that have recently been transmitted. The main parameter of this '''memory''' a time specification i.e. the number of seconds that transmitted packets are kept around for comparing to candidates for digipeating.

Duplicates are detected by comparing the source, destination, and information fields. The digipeater path is not part of the comparison. A digipeater should not re-transmit something it originated or already digipeated. This will also limit the rate of identical packets that are being generated at a rapid rated. Suppose some station was sending 10 identical packets per second. A digipeater configured to remember packets for 30 seconds will cut this rate down to 2 per minute.

Other details of the ''New-N Paradigm'' include settings to TRAP abusive user paths with large values of '''N'''. Usually only '''WIDE2-2''' is recommended in most high density areas and surrounding territory.

=== Suggested Setup for a Mobile/Fixed APRS Station ===

Please read suggested setups for [[Paths]].

=== Other discussion ===
Steve WA8LMF has a parallel discussion of digipeaters and [http://www.wa8lmf.net/DigiPaths/ digipaths].
Of particular interest is the [http://www.wa8lmf.net/DigiPaths/NNNN-Digi-Demo.htm animation] of the New-N Paradigm.

== Links ==
* [http://www.youtube.com/watch?v=zTNjUllHbKg Video: Digipeater on TM-D710] - Digipeater on [[TM-D710]]

This video has several errors.
3:57 - Voice Alert - 614
This has nothing to do with the voice module. [http://info.aprs.net/index.php/VoiceAlert VoiceAlert]

4:03 - Digipeat (MyCal) - 616
This is digipeating stations with paths like MYCALL,WIDEn-N
In this example MYCALL is N0AOL, turning on menu 616 enables stations to use N0AOL,WIDE2-1 so that this station is digipeating it.
Could be used as a "private" digipeater i.e if you have a TH-D7 and you need to use your home station to reach a digipeater.

4:44 - UICHECK - 617
This is a duplicate check so that it's not retransmitting packets sent i.e every 10sec

6:59 - UIFLOOD - 619
He is saying that his station is not going outside Colorado. He is activating a SS digipeater so that people using CO instead of WIDEn-N is been digipeted from this station. This setting doesn't limit the propagation of his beacon.

7:15 - UITRACE - 620
This has nothing to do with messaging. This enables a tracable digipeater. This can be default ON if the alias is TEMP. Now people using TEMP in their path is going trough this digipeater.
Can also be used to make a tracable WIDEn-N digi if you replace TEMP with WIDE.

A nice explanation of the digi functions can be found on: [http://www.kenwood.com/i/products/info/amateur/pdf/TM-D710AE_IDM_R1.pdf In-depth Manual]

So no offence to the author of this video :o)

Digipeater

2012-11-20T02:16:26Z

Wb2osz: /* Digipeating example */

==Digipeater==

===Definition===

A Digipeater is a station that does digital repeating. Unlike full-duplex
VHF/UHF voice repeaters a digipeater will
receive a packet, process it, and retransmit on the same frequency. A digipeater
which operates on multiple frequencies is called a [[gateway]].

In classic packet radio each such hop had to be explicitly included in the packet by the sender at origination. In APRS all digipeaters use generic aliases. The sender does not have to know the callsign of the digipeater but just indicate the number of hops he wants to go.

Digipeating is defined in AX.25 specification document.
An initiating station can include in each packet a list of intermediate stations which are supposed to digipeat the packet, passing it on toward the desired destination. The list of intermediate stations is called the [[Paths|path]]. Stations receiving packets examine the path of received packets. Using it's configuration information a receiving station can decide if a packet is a candidate for digipeating. When this is true the packet addressing information is modified slightly and the modified packet is transmitted.

The idea is to get packets to propagate outward from the initiating station... but not so far as to be an unnecessary burden on the system and surrounding users. The practical range of a VHF 1200 baud APRS channel is estimated to include the nearest 60 stations (approximately), called the [[AlohaCircle|Aloha Circle]].

===The Digipeating Path and Development of WIDEn-N===

If there are multiple aliases in the PATH they are examined in the order left-to-right. An asterisk '''*''' is used to show that a element in the path is no longer active. In the path '''ABCD*,EFGH,IJKL''' only the '''EFGH''' path element is active because the previous path element '''ABCD*''' is "used up". And the '''IJKL''' is not yet active because it is not the left-most active field.

When APRS was first invented the generic calls of RELAY, WIDE and TRACE were used for all digipeaters, but there was no duplicaton suppression mechanism. Paths beyond 2 hops could fold back ending up with dozens of unwanted duplicate packets. By 1994 a WIDEn-N and TRACEn-N scheme was proposed by WB4APR. It was finally implemented in 1998 by Kantronics, providing perfect dupe suppression and becoming the standard and most efficient way of operating. When a digipeater sees an "n-N" packet, it digipeats it and decrements the "N" by 1. This continues until the "N" is zero.

Up until 2004 APRS in the USA was using a mixture of the old generic paths and the new n-N type paths and the presence of the old paths was causing terrible QRM. TO combat these inefficiencies, WB4APR launched the New-N Paradigm to phase out all the old legacy paths and greatly simplify paths to simply WIDEn-N and to make these paths 100% traceable. For current recommended paths, see the [[Paths]] page.

===Local and Wide Digipeaters===

As with voice VHF repeaters, digipeaters are installed in places of prominence to allow for extended range. If a small station can "hit" the digipeater, his packet will go much farther then his own station can reach. Local digipeaters (called '''FILL-IN''' digipeaters) are usually located in blind spots where mobiles are unable to be heard by the main digipeaters. THese '''FILL-IN''' digis only respond to the '''WIDE1-1''' path. This keeps them from needlessly repeating all other traffic from the high digis.

===Digipeating example===

Station ''ABCD'' sends a packet with path '''WIDE1-1, WIDE2-2'''.

A nearby station ''EFGH'' is configured to respond to '''WIDE1-1''', so he does so. He decrements the second number (the SSID) making '''-1''' into '''-0''' and retransmits the packet with path '''EFGH,WIDE1*, WIDE2-2'''. The convention is that -'''0''' is not displayed.
A WIDEn-N digipeater will also insert its own callsign into the path before the WIDEn-N path element that it acted on so that the path is traceable through all the digipeaters that relayed it. In this example the packet now includes '''EFGH''' showing it passed through station ''EFGH''.

Another station ''IJKL'' (configured to respond to '''WIDEn-N''') picks it up and sends it out with '''EFGH,WIDE1,IJKL*,WIDE2-1'''. The destination '''WIDE2-1''' still has one hop so it is not yet marked with a '''*''' and this packet is available for further digipeating.

Then station ''MNOP'' (configured to respond to '''WIDEn-N''') hears it. Because '''WIDE2-1''' is still active, he repeats it back out as '''EFGH,WIDE1,IJKL,MNOP,WIDE2*'''. Since there are no more active path elements any digipeating station receiving that packet will not repeat it.

Again, the list of destinations are consumed in left-to-right order. Path tracing allows digipeaters to insert their callsigns prior to the active path as a way of tracking the path the packet actually took through the system. The numbers after the dash in the WIDEn-N format are decremented until they reach '''-0''' and disappear altogether. The last destination that is used-up is marked with a '''*'''.

This technique has the unfortunate property that the resulting path does not indicate what actually happened along the way. '''EFGH,WIDE1,IJKL,MNOP,WIDE2*''' looks like the packet was retransmitted 5 times: first by EFGH, then by some unknown station not configured for tracing, then by IJKL, then by MNOP, and finally by some other unknown station that is not configured for tracing. This makes it difficult to figure out what stations can hear each other when a couple apparent unknown stations end up in the list.

===Dupe Checking===

You might be thinking, "Hey, what's to keep ''EFGH'' from hearing that packet that ''IJKL'' sent out? ''EFGH'' would send it out again, ''IJKL'' would pick it up and send it out again. This thing could just loop around and not really get anywhere." To solve this, all modern digipeaters have ''dupe-checking'' algorithms.

'''WIDEn-N''' Digipeaters have some '''memory''' of what has been transmitted them recently and drops duplicates. This is known as [[DuplicateChecking|dupe checking]]. Otherwise they would spend a lot of their time just booming packets back and forth amongst each other and the little pip-squeak tracker stations would never be heard at all. The dupe checking algorithm in the digipeater will act to suppress re-transmission of packets that have recently been transmitted. The main parameter of this '''memory''' a time specification i.e. the number of seconds that transmitted packets are kept around for comparing to candidates for digipeating.

Duplicates are detected by comparing the source, destination, and information fields. The digipeater path is not part of the comparison. A digipeater should not re-transmit something it originated or already digipeated. This will also limit the rate of identical packets that are being generated at a rapid rated. Suppose some station was sending 10 identical packets per second. A digipeater configured to remember packets for 30 seconds will cut this rate down to 2 per minute.

Other details of the ''New-N Paradigm'' include settings to TRAP abusive user paths with large values of '''N'''. Usually only '''WIDE2-2''' is recommended in most high density areas and surrounding territory.

=== Suggested Setup for a Mobile/Fixed APRS Station ===

Please read suggested setups for [[Paths]].

=== Other discussion ===
Steve WA8LMF has a parallel discussion of digipeaters and [http://www.wa8lmf.net/DigiPaths/ digipaths].
Of particular interest is the [http://www.wa8lmf.net/DigiPaths/NNNN-Digi-Demo.htm animation] of the New-N Paradigm.

== Links ==
* [http://www.youtube.com/watch?v=zTNjUllHbKg Video: Digipeater on TM-D710] - Digipeater on [[TM-D710]]

This video has several errors.
3:57 - Voice Alert - 614
This has nothing to do with the voice module. [http://info.aprs.net/index.php/VoiceAlert VoiceAlert]

4:03 - Digipeat (MyCal) - 616
This is digipeating stations with paths like MYCALL,WIDEn-N
In this example MYCALL is N0AOL, turning on menu 616 enables stations to use N0AOL,WIDE2-1 so that this station is digipeating it.
Could be used as a "private" digipeater i.e if you have a TH-D7 and you need to use your home station to reach a digipeater.

4:44 - UICHECK - 617
This is a duplicate check so that it's not retransmitting packets sent i.e every 10sec

6:59 - UIFLOOD - 619
He is saying that his station is not going outside Colorado. He is activating a SS digipeater so that people using CO instead of WIDEn-N is been digipeted from this station. This setting doesn't limit the propagation of his beacon.

7:15 - UITRACE - 620
This has nothing to do with messaging. This enables a tracable digipeater. This can be default ON if the alias is TEMP. Now people using TEMP in their path is going trough this digipeater.
Can also be used to make a tracable WIDEn-N digi if you replace TEMP with WIDE.

A nice explanation of the digi functions can be found on: [http://www.kenwood.com/i/products/info/amateur/pdf/TM-D710AE_IDM_R1.pdf In-depth Manual]

So no offence to the author of this video :o)

Digipeater

2012-11-20T02:10:36Z

Wb2osz: /* Dupe Checking */

==Digipeater==

===Definition===

A Digipeater is a station that does digital repeating. Unlike full-duplex
VHF/UHF voice repeaters a digipeater will
receive a packet, process it, and retransmit on the same frequency. A digipeater
which operates on multiple frequencies is called a [[gateway]].

In classic packet radio each such hop had to be explicitly included in the packet by the sender at origination. In APRS all digipeaters use generic aliases. The sender does not have to know the callsign of the digipeater but just indicate the number of hops he wants to go.

Digipeating is defined in AX.25 specification document.
An initiating station can include in each packet a list of intermediate stations which are supposed to digipeat the packet, passing it on toward the desired destination. The list of intermediate stations is called the [[Paths|path]]. Stations receiving packets examine the path of received packets. Using it's configuration information a receiving station can decide if a packet is a candidate for digipeating. When this is true the packet addressing information is modified slightly and the modified packet is transmitted.

The idea is to get packets to propagate outward from the initiating station... but not so far as to be an unnecessary burden on the system and surrounding users. The practical range of a VHF 1200 baud APRS channel is estimated to include the nearest 60 stations (approximately), called the [[AlohaCircle|Aloha Circle]].

===The Digipeating Path and Development of WIDEn-N===

If there are multiple aliases in the PATH they are examined in the order left-to-right. An asterisk '''*''' is used to show that a element in the path is no longer active. In the path '''ABCD*,EFGH,IJKL''' only the '''EFGH''' path element is active because the previous path element '''ABCD*''' is "used up". And the '''IJKL''' is not yet active because it is not the left-most active field.

When APRS was first invented the generic calls of RELAY, WIDE and TRACE were used for all digipeaters, but there was no duplicaton suppression mechanism. Paths beyond 2 hops could fold back ending up with dozens of unwanted duplicate packets. By 1994 a WIDEn-N and TRACEn-N scheme was proposed by WB4APR. It was finally implemented in 1998 by Kantronics, providing perfect dupe suppression and becoming the standard and most efficient way of operating. When a digipeater sees an "n-N" packet, it digipeats it and decrements the "N" by 1. This continues until the "N" is zero.

Up until 2004 APRS in the USA was using a mixture of the old generic paths and the new n-N type paths and the presence of the old paths was causing terrible QRM. TO combat these inefficiencies, WB4APR launched the New-N Paradigm to phase out all the old legacy paths and greatly simplify paths to simply WIDEn-N and to make these paths 100% traceable. For current recommended paths, see the [[Paths]] page.

===Local and Wide Digipeaters===

As with voice VHF repeaters, digipeaters are installed in places of prominence to allow for extended range. If a small station can "hit" the digipeater, his packet will go much farther then his own station can reach. Local digipeaters (called '''FILL-IN''' digipeaters) are usually located in blind spots where mobiles are unable to be heard by the main digipeaters. THese '''FILL-IN''' digis only respond to the '''WIDE1-1''' path. This keeps them from needlessly repeating all other traffic from the high digis.

===Digipeating example===

Station ''ABCD'' sends a packet with path '''WIDE1-1, WIDE2-2'''.

A nearby station ''EFGH'' is configured to respond to '''WIDE1-1''', so he does so. He decrements the second number (the SSID) making '''-1''' into '''-0''' and retransmits the packet with path '''EFGH,WIDE1*, WIDE2-2'''. The convention is that -'''0''' is not displayed.
A WIDEn-N digipeater will also insert its own callsign into the path before the WIDEn-N path element that it acted on so that the path is traceable through all the digipeaters that relayed it. In this example the packet now includes '''EFGH''' showing it passed through station ''EFGH''.

Another station ''IJKL'' (configured to respond to '''WIDEn-N''') picks it up and sends it out with '''EFGH,WIDE1,IJKL*,WIDE2-1'''. The destination '''WIDE2-1''' still has one hop so it is not yet marked with a '''*''' and this packet is available for further digipeating.

Then station ''MNOP'' (configured to respond to '''WIDEn-N''') hears it. Because '''WIDE2-1''' is still active, he repeats it back out as '''EFGH,WIDE1,IJKL,MNOP,WIDE2*'''. Since there are no more active path elements any digipeating station receiving that packet will not repeat it.

Again, the list of destinations are consumed in left-to-right order. Path tracing allows digipeaters to insert their callsigns prior to the active path as a way of tracking the path the packet actually took through the system. The numbers after the dash in the WIDEn-N format are decremented until they reach '''-0''' and disappear altogether. The last destination that is used-up is marked with a '''*'''.

===Dupe Checking===

You might be thinking, "Hey, what's to keep ''EFGH'' from hearing that packet that ''IJKL'' sent out? ''EFGH'' would send it out again, ''IJKL'' would pick it up and send it out again. This thing could just loop around and not really get anywhere." To solve this, all modern digipeaters have ''dupe-checking'' algorithms.

'''WIDEn-N''' Digipeaters have some '''memory''' of what has been transmitted them recently and drops duplicates. This is known as [[DuplicateChecking|dupe checking]]. Otherwise they would spend a lot of their time just booming packets back and forth amongst each other and the little pip-squeak tracker stations would never be heard at all. The dupe checking algorithm in the digipeater will act to suppress re-transmission of packets that have recently been transmitted. The main parameter of this '''memory''' a time specification i.e. the number of seconds that transmitted packets are kept around for comparing to candidates for digipeating.

Duplicates are detected by comparing the source, destination, and information fields. The digipeater path is not part of the comparison. A digipeater should not re-transmit something it originated or already digipeated. This will also limit the rate of identical packets that are being generated at a rapid rated. Suppose some station was sending 10 identical packets per second. A digipeater configured to remember packets for 30 seconds will cut this rate down to 2 per minute.

Other details of the ''New-N Paradigm'' include settings to TRAP abusive user paths with large values of '''N'''. Usually only '''WIDE2-2''' is recommended in most high density areas and surrounding territory.

=== Suggested Setup for a Mobile/Fixed APRS Station ===

Please read suggested setups for [[Paths]].

=== Other discussion ===
Steve WA8LMF has a parallel discussion of digipeaters and [http://www.wa8lmf.net/DigiPaths/ digipaths].
Of particular interest is the [http://www.wa8lmf.net/DigiPaths/NNNN-Digi-Demo.htm animation] of the New-N Paradigm.

== Links ==
* [http://www.youtube.com/watch?v=zTNjUllHbKg Video: Digipeater on TM-D710] - Digipeater on [[TM-D710]]

This video has several errors.
3:57 - Voice Alert - 614
This has nothing to do with the voice module. [http://info.aprs.net/index.php/VoiceAlert VoiceAlert]

4:03 - Digipeat (MyCal) - 616
This is digipeating stations with paths like MYCALL,WIDEn-N
In this example MYCALL is N0AOL, turning on menu 616 enables stations to use N0AOL,WIDE2-1 so that this station is digipeating it.
Could be used as a "private" digipeater i.e if you have a TH-D7 and you need to use your home station to reach a digipeater.

4:44 - UICHECK - 617
This is a duplicate check so that it's not retransmitting packets sent i.e every 10sec

6:59 - UIFLOOD - 619
He is saying that his station is not going outside Colorado. He is activating a SS digipeater so that people using CO instead of WIDEn-N is been digipeted from this station. This setting doesn't limit the propagation of his beacon.

7:15 - UITRACE - 620
This has nothing to do with messaging. This enables a tracable digipeater. This can be default ON if the alias is TEMP. Now people using TEMP in their path is going trough this digipeater.
Can also be used to make a tracable WIDEn-N digi if you replace TEMP with WIDE.

A nice explanation of the digi functions can be found on: [http://www.kenwood.com/i/products/info/amateur/pdf/TM-D710AE_IDM_R1.pdf In-depth Manual]

So no offence to the author of this video :o)

Digipeater

2012-11-20T00:58:41Z

Wb2osz: Remove excess * in the examples. In the usual display format, only the last used digipeater is marked with *.

==Digipeater==

===Definition===

A Digipeater is a station that does digital repeating. Unlike full-duplex
VHF/UHF voice repeaters a digipeater will
receive a packet, process it, and retransmit on the same frequency. A digipeater
which operates on multiple frequencies is called a [[gateway]].

In classic packet radio each such hop had to be explicitly included in the packet by the sender at origination. In APRS all digipeaters use generic aliases. The sender does not have to know the callsign of the digipeater but just indicate the number of hops he wants to go.

Digipeating is defined in AX.25 specification document.
An initiating station can include in each packet a list of intermediate stations which are supposed to digipeat the packet, passing it on toward the desired destination. The list of intermediate stations is called the [[Paths|path]]. Stations receiving packets examine the path of received packets. Using it's configuration information a receiving station can decide if a packet is a candidate for digipeating. When this is true the packet addressing information is modified slightly and the modified packet is transmitted.

The idea is to get packets to propagate outward from the initiating station... but not so far as to be an unnecessary burden on the system and surrounding users. The practical range of a VHF 1200 baud APRS channel is estimated to include the nearest 60 stations (approximately), called the [[AlohaCircle|Aloha Circle]].

===The Digipeating Path and Development of WIDEn-N===

If there are multiple aliases in the PATH they are examined in the order left-to-right. An asterisk '''*''' is used to show that a element in the path is no longer active. In the path '''ABCD*,EFGH,IJKL''' only the '''EFGH''' path element is active because the previous path element '''ABCD*''' is "used up". And the '''IJKL''' is not yet active because it is not the left-most active field.

When APRS was first invented the generic calls of RELAY, WIDE and TRACE were used for all digipeaters, but there was no duplicaton suppression mechanism. Paths beyond 2 hops could fold back ending up with dozens of unwanted duplicate packets. By 1994 a WIDEn-N and TRACEn-N scheme was proposed by WB4APR. It was finally implemented in 1998 by Kantronics, providing perfect dupe suppression and becoming the standard and most efficient way of operating. When a digipeater sees an "n-N" packet, it digipeats it and decrements the "N" by 1. This continues until the "N" is zero.

Up until 2004 APRS in the USA was using a mixture of the old generic paths and the new n-N type paths and the presence of the old paths was causing terrible QRM. TO combat these inefficiencies, WB4APR launched the New-N Paradigm to phase out all the old legacy paths and greatly simplify paths to simply WIDEn-N and to make these paths 100% traceable. For current recommended paths, see the [[Paths]] page.

===Local and Wide Digipeaters===

As with voice VHF repeaters, digipeaters are installed in places of prominence to allow for extended range. If a small station can "hit" the digipeater, his packet will go much farther then his own station can reach. Local digipeaters (called '''FILL-IN''' digipeaters) are usually located in blind spots where mobiles are unable to be heard by the main digipeaters. THese '''FILL-IN''' digis only respond to the '''WIDE1-1''' path. This keeps them from needlessly repeating all other traffic from the high digis.

===Digipeating example===

Station ''ABCD'' sends a packet with path '''WIDE1-1, WIDE2-2'''.

A nearby station ''EFGH'' is configured to respond to '''WIDE1-1''', so he does so. He decrements the second number (the SSID) making '''-1''' into '''-0''' and retransmits the packet with path '''EFGH,WIDE1*, WIDE2-2'''. The convention is that -'''0''' is not displayed.
A WIDEn-N digipeater will also insert its own callsign into the path before the WIDEn-N path element that it acted on so that the path is traceable through all the digipeaters that relayed it. In this example the packet now includes '''EFGH''' showing it passed through station ''EFGH''.

Another station ''IJKL'' (configured to respond to '''WIDEn-N''') picks it up and sends it out with '''EFGH,WIDE1,IJKL*,WIDE2-1'''. The destination '''WIDE2-1''' still has one hop so it is not yet marked with a '''*''' and this packet is available for further digipeating.

Then station ''MNOP'' (configured to respond to '''WIDEn-N''') hears it. Because '''WIDE2-1''' is still active, he repeats it back out as '''EFGH,WIDE1,IJKL,MNOP,WIDE2*'''. Since there are no more active path elements any digipeating station receiving that packet will not repeat it.

Again, the list of destinations are consumed in left-to-right order. Path tracing allows digipeaters to insert their callsigns prior to the active path as a way of tracking the path the packet actually took through the system. The numbers after the dash in the WIDEn-N format are decremented until they reach '''-0''' and disappear altogether. The last destination that is used-up is marked with a '''*'''.

===Dupe Checking===

You might be thinking, "Hey, what's to keep ''EFGH'' from hearing that packet that ''IJKL'' sent out? ''EFGH'' would send it out again, ''IJKL'' would pick it up and send it out again. This thing could just loop around and not really get anywhere." To solve this, all modern digipeaters have ''dupe-checking'' algorithms.

'''WIDEn-N''' Digipeaters have some '''memory''' of what has gone through them recently. This is known as [[DuplicateChecking|dupe checking]]. Otherwise they would spend a lot of their time just booming packets back and forth amongst each other and the little pip-squeak tracker stations would never be heard at all. The dupe checking algorithm in the digipeater will act to suppress re-transmission of packets that have recently been transmitted. The main parameter of this '''memory''' a time specification i.e. the number of seconds that received packets are kept around for comparing to incoming packets.

Other details of the ''New-N Paradigm'' include settings to TRAP abusive user paths with large values of '''N'''. Usually only '''WIDE2-2''' is recommended in most high density areas and surrounding territory.

=== Suggested Setup for a Mobile/Fixed APRS Station ===

Please read suggested setups for [[Paths]].

=== Other discussion ===
Steve WA8LMF has a parallel discussion of digipeaters and [http://www.wa8lmf.net/DigiPaths/ digipaths].
Of particular interest is the [http://www.wa8lmf.net/DigiPaths/NNNN-Digi-Demo.htm animation] of the New-N Paradigm.

== Links ==
* [http://www.youtube.com/watch?v=zTNjUllHbKg Video: Digipeater on TM-D710] - Digipeater on [[TM-D710]]

This video has several errors.
3:57 - Voice Alert - 614
This has nothing to do with the voice module. [http://info.aprs.net/index.php/VoiceAlert VoiceAlert]

4:03 - Digipeat (MyCal) - 616
This is digipeating stations with paths like MYCALL,WIDEn-N
In this example MYCALL is N0AOL, turning on menu 616 enables stations to use N0AOL,WIDE2-1 so that this station is digipeating it.
Could be used as a "private" digipeater i.e if you have a TH-D7 and you need to use your home station to reach a digipeater.

4:44 - UICHECK - 617
This is a duplicate check so that it's not retransmitting packets sent i.e every 10sec

6:59 - UIFLOOD - 619
He is saying that his station is not going outside Colorado. He is activating a SS digipeater so that people using CO instead of WIDEn-N is been digipeted from this station. This setting doesn't limit the propagation of his beacon.

7:15 - UITRACE - 620
This has nothing to do with messaging. This enables a tracable digipeater. This can be default ON if the alias is TEMP. Now people using TEMP in their path is going trough this digipeater.
Can also be used to make a tracable WIDEn-N digi if you replace TEMP with WIDE.

A nice explanation of the digi functions can be found on: [http://www.kenwood.com/i/products/info/amateur/pdf/TM-D710AE_IDM_R1.pdf In-depth Manual]

So no offence to the author of this video :o)

Software

2012-02-05T16:21:55Z

Wb2osz: /* APRS related X.25 Software */

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

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

==== Linux and Unix ====
* [http://edu.kde.org/marble/ Marble] the KDE Desktop Globe
* [[XASTIR]]
* [http://www.winaprs.com X-APRS] - Discontinued

==== 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.pinpointaprs.com/ PinPoint APRS]
* [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]]

=== Mobile System ===
==== Apple iOS ====
* [http://itunes.apple.com/us/app/aprs/id341511796?mt=8 APRS by Gary Huntress]
* [http://itunes.apple.com/ru/app/aprsnow/id366006368?mt=8 APRSNow by Gregg Wonderly]
* [http://itunes.apple.com/ru/app/ham-dashboard/id397752661?mt=8 Ham Dashboard]
* [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 OpenAPRS]
* [http://itunes.apple.com/ru/app/openaprs-xl/id363666470?mt=8 OpenAPRS-xL]
* [[PocketPacket]]
* [http://itunes.apple.com/us/app/ship-finder/id319726819?mt=8 Ship Finder]
* [http://itunes.apple.com/us/app/ship-finder-free/id324177409?mt=8 Ship Finder Free]
* [http://itunes.apple.com/ru/app/ship-finder-hd/id363360636?mt=8 Ship Finder HD]
* [http://itunes.apple.com/ru/app/ship-finder-hd-free/id364616485?mt=8 Ship Finder HD Free]

==== Android ====
* [http://aprsdroid.org/ 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]

==== 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 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]
*[http://home.comcast.net/~wb2osz/site/ Dire Wolf sound card TNC - AGWPE replacement for Windows and 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|*]]