Digipeater - Revision history

Wb2osz: Improved technique for digipeater tracing.

2012-11-20T02:46:31Z

Improved technique for digipeater tracing.

Wb2osz: /* Digipeating example */

2012-11-20T02:28:59Z

‎Digipeating example

Wb2osz: /* Digipeating example */

2012-11-20T02:16:26Z

‎Digipeating example

Wb2osz: /* Dupe Checking */

2012-11-20T02:10:36Z

‎Dupe Checking

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

2012-11-20T00:58:41Z

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

KM5VY: Reverted edits by Reverse22 (talk) to last revision by LA3QMA

2011-12-31T01:44:38Z

Reverted edits by Reverse22 (talk) to last revision by LA3QMA

Anonymous at 23:01, 30 December 2011

2011-12-30T23:01:15Z

LA3QMA: /* Links */

2010-06-11T15:46:48Z

‎Links

UR3IRS: /* Links */

2010-01-05T03:37:12Z

‎Links

UR3IRS: /* Links */

2010-01-04T17:37:20Z

‎Links

@@ Line 45: / Line 45: @@
 ===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.
+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'''.
@@ Line 54: / Line 54: @@
 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===

← Older revision		Revision as of 02:28, 20 November 2012
Line 42:		Line 42:

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

← Older revision		Revision as of 02:16, 20 November 2012
Line 40:		Line 40:

	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 '''*'''.		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===		===Dupe Checking===

@@ Line 45: / Line 45: @@
 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.
+'''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.
 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.

@@ Line 32: / Line 32: @@
 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 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.
+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.
+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.  Destinations that are all used-up are marked with a '''*'''.
+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===

← Older revision		Revision as of 01:44, 31 December 2011
Line 82:		Line 82:

	So no offence to the author of this video :o)		So no offence to the author of this video :o)
−
−
−	~~[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse phone lookup]~~
−
−	~~[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]~~

← Older revision		Revision as of 23:01, 30 December 2011
Line 82:		Line 82:

	So no offence to the author of this video :o)		So no offence to the author of this video :o)
		+
		+
		+	[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse phone lookup]
		+
		+	[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

← Older revision		Revision as of 15:46, 11 June 2010
Line 59:		Line 59:
	== Links ==		== Links ==
	* [http://www.youtube.com/watch?v=zTNjUllHbKg Video: Digipeater on TM-D710] - Digipeater on [[TM-D710]]		* [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)

← Older revision		Revision as of 03:37, 5 January 2010
Line 58:		Line 58:

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

← Older revision		Revision as of 17:37, 4 January 2010
Line 58:		Line 58:

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