<DIV>Boy, just when you think you have it... another explanation comes along and messes up things...</DIV>
<DIV>Bob sure gives easy to understand explanations, but somehow the half life of this knowledge seems to be somewhere around 24 hours. I think my brain is FULL. I have long-been digging around the internet and also have the APRS spec [80% over my head so far), but this path stuff is still foggy and I know it is really quite easy. Archive hunting is fraught with lots of un helpful stuff to sift through. All explanations on the net seem to assume way-more knowledge about packet than I have (Zero)</DIV>
<DIV> </DIV>
<DIV>I'm trying to undrstand the *basics* of the path designators. I've had a D700 for about 2 years and some of this is starting to stick, but... </DIV>
<DIV> </DIV>
<DIV>I get the WIDEn-n concept, but it is the series of XXXX,YYYY path designators (aliases) and precisely how they are handled that I have fog. If there is a clear explanation of just how packet paths are handled, on the net, point me there and forget the rest of this as this may all be handled by one paper or answer... Here goes.</DIV>
<DIV> </DIV>
<DIV>In excerpt 2 (below), the *Bob* recommends a D700 digipeater path of:</DIV>
<DIV> Set APRS-UIDIGI to TEMP,WIDE1-1</DIV>
<DIV>Now, it seems that the tracker should have a path of only TEMP,</DIV>
<DIV>Except Bob says:</DIV>
<DIV> Set pocket tracker to use path VIA WIDE1-1,WIDE2-1</DIV>
<DIV> </DIV>
<DIV>SO.. FIRST basic UIDIGI stuff:</DIV>
<DIV>Will a digi set for TEMP,WIDE1-1 digipeat a packet with _either_ a path of TEMP *OR* WIDE1-1 in the first slot?</DIV>
<DIV> I think I am asking ; Is it the case that a Digi will 'peat a packet with *any* of the alias's (in the currently tested spot of the packet) in its own UI list?</DIV>
<DIV> </DIV>
<DIV>Then, for a station originating packets:</DIV>
<DIV>Are the aliases handled only sequentially by digis, left to right? like this...</DIV>
<DIV>With a path of : XXXX,YYYY</DIV>
<DIV>Is it true that this packet will ONLY be 'peated by a Digi with XXXX in its list? In other words if no XXXX Digi hears it, it dies, forever lost in the ether, even if a YYYY Digi hears it?</DIV>
<DIV> </DIV>
<DIV>Then the XXXX Digi transmits it (marking XXXX with *) and only a YYYY digi will then 'peat it?</DIV>
<DIV> </DIV>
<DIV>So, Digis look for the first alias without * and if it gets a match with *any* in its list it repeats it?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV>=== Part two GATE question ===</DIV>
<DIV>In the HF case (1st <SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">excerpt </SPAN>below). The recommended path </DIV>
<DIV> GATE,WIDE2-1</DIV>
<DIV>means that ONLY a GATE will take this packet off the RF network, right?______</DIV>
<DIV>Then, after the GATE gets it, it will only then be digipeated by the true WIDE (assuming it has the WIDEn-n software)?___</DIV>
<DIV> </DIV>
<DIV> Except, is this from the HF side *to* 2M or from 2M to HF -- or does it matter -- ?_____</DIV>
<DIV> </DIV>
<DIV>
<DIV> </DIV>
<DIV>Moving to (the final) PART 3 a related topic "Call Substitution"</DIV>
<DIV>Without this, I believe each Digi that 'peats a packet puts an asterisk (*) in the field of the path designator it "used" ?? Hmmmm Peter piper 'peats a peck of 'peated packets...</DIV>
<DIV> </DIV>
<DIV>
<DIV>*With* Call Substitution, we will see (within the 'peated packet) a list of calls of the digis that handled this packet, right? I think the last one will have the * I look @ the findu raw packets and next hope to follow the q construct information there...'cept I don't really know wht a "client" is...</DIV>
<DIV> </DIV></DIV></DIV></DIV>
<DIV>Ah, what the heck, as long as I'm here...</DIV>
<DIV> </DIV>
<DIV>What is the stuff immediately after my call (<FONT face="Courier New">T2PS9Y) </FONT>in the APRS-IS packets on findu:</DIV>
<DIV><FONT face="Courier New">K9DCI-9>T2PS9Y,WB9WLS*,WIDE2-2,qAR,KH6KI-1:'tZdl,M>/]Steve Wonder Lake IL 145.410 ???</FONT></DIV>
<DIV><FONT face="Courier New">Hmmm I thought I changed back to .WIDE1-1,WIDE2-1</FONT></DIV>
<DIV><BR></DIV>
<DIV>
<DIV>73, Steve, K;9.D'C,I</DIV></DIV>
<DIV>========== EXCERPT #1 =================</DIV>
<DIV> </DIV>
<DIV>Date: Fri, 03 Jun 2005 19:26:27 -0400<BR>From: "Robert Bruninga" <BRUNINGA@USNA.EDU><BR>Subject: Re: [aprssig] HF and the new n-N paradigm, mobile digis<BR><BR>Good questions!<BR><BR>>What would be the recommended path for APRS <BR>>mobile/portable stations on HF? ... the old way <BR>>was to use GATE, WIDE ... Would the new way<BR>> be GATE, WIDE1-1?<BR><BR>No, because the special path of WIDE1-1 is for<BR>use by home and fill-in digis only. So better to<BR>use the path of GATE,WIDE2-1. It is still only<BR>a 1 hop path but does not key up home stations.<BR><BR>>Also, is there any convention in place for a standard <BR>>alias to be used for a mobile digi? For example, ...<BR>>I've got a pockettracker.... to make it back to my car<BR>>DIGI...<BR><BR>Yes, set your D700 to digipeat by using a PC to enable<BR>its UITRACE parameter with the permanent alias of<BR>TEMPn-N. This way, any mobile any time can be used<BR>as a temporary digi, but all the other time,
the digi does<BR>not digipeat any normal on-air packets and so does not<BR>add any problems. But is always available.<BR><BR>de WB4APR, Bob<BR><BR>
<DIV> </DIV>
<DIV>========== EXCERPT # 2 ================<BR>Message: 9<BR>Date: Sat, 04 Jun 2005 09:50:53 -0400<BR>From: "Robert Bruninga" <BRUNINGA@USNA.EDU><BR>Subject: [aprssig] Mobile Digis (New -N Paradigm)<BR>To: <VO1ONE@GMAIL.COM>, <APRSSIG@LISTS.TAPR.ORG>, "Robert Bruninga"<BR><BRUNINGA@USNA.EDU><BR>Message-ID: <S2A179A0.055@FSGWHUB.USNA.EDU><BR>Content-Type: text/plain; charset=US-ASCII<BR><BR>We should add this recommendation formally to the <BR>New-N Paradigm. This will go a long way towards<BR>common and consistent use of pocket trackers and<BR>other temporary applications:<BR><BR>D700 user's should be aware of these settings:<BR><BR>NORMAL OPERATIONS:<BR>Set APRS-DIGI OFF!<BR><BR>DIGIPEATING A POCKET TRACKER:<BR>Set Tracket to 144.99<BR>Set D700 band B to RX 144.99<BR>Set D700 band A to TX 144.39<BR>Set D700 TNC to RX B & TX A<BR>Set RADIO-TNC-DCD to both A&B<BR>Set APRS-UIDIGI to TEMP,WIDE1-1<BR>Save in a PM just for this application<BR>Set pocket tracker
to use path VIA WIDE1-1,WIDE2-1<BR><BR>This will make the pocket tracker use the the full<BR>power of the D700 and with courteous channel <BR>sharing AND with no interference or congestion<BR>between the tracker and your mobile. Notice that<BR>setting DCD to both is generally not a good idea<BR>for normal operation because it will keep your <BR>normal posits from going out if you are using band<BR>B. So that is why this should be in a PM all its <BR>own only used for digipeating the tracker.<BR><BR>ADDITIONAL SETTINGS using a PC:<BR>Set UITRACE TEMP,30<BR><BR>This will cause your D700 to ALWAYS be ready at<BR>any time to act as a temproary digipeater in support<BR>of TEMPn-N routing. SUch as FieldDay.<BR><BR>The question is whether this is saved in APRS mode<BR>or only in packet mode. And if you set it while in a<BR>PM, can it be saved there too? I suspect this only<BR>works in PACKET mode but that is fine for Field Day<BR>or any other temporary net you want to set up.<BR><BR>RESULT
OF TEMP mode:<BR>You can use TEMP or WIDE1-1 to digipeat thorugh any<BR>mobile that is in APRS mode and has APRS-MENU-DIGI ON.<BR>And you can use TEMP7-7 as a path for Field Day<BR>via any D700 that is in packet mode or any other time.<BR><BR>Once we all agree to this or some other arrangement,<BR>lets get EVERYONE on board. We can easily <BR>send a MESSAGE to ALL D700 users by simply using<BR>the GROUP MESSAGE function. All of the Kenwoods<BR>come with the default MESSAGE group of KWD.<BR><BR>Until we get the word out, a good message might be<BR><BR>To: KWD: See new-N settings for D700. Google XXXXXXX<BR><BR>and after we get everyone to a consistent set, then for<BR>special events where you need an instant net on <BR>a different freq for emergency or special comms then:<BR><BR>To: KWD: SPECIAL, pse support alt-net on 145.01 TNX<BR><BR>or any other uses.. But we need owners to be fully<BR>awayre of the potential of their radios, how to set<BR>them up, and how to use them. THus, I
want us all to<BR>debate the final settings for digipeating and agree and<BR>then include it in the New-N pparadigm so that APRS<BR>works consistently everywhere and is flexible and can<BR>respond quickly to emergent needs.<BR><BR>de Wb4APR, Bob<BR><BR></DIV></DIV><p>__________________________________________________<br>Do You Yahoo!?<br>Tired of spam? Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com