Loading ...
Sorry, an error occurred while loading the content.

RE: [tracker2] Firmware build 53875

Expand Messages
  • scott@opentrac.org
    Personally, I like to know what the path started out as. I can have it drop used-up WIDEn-N s, but if I do it ll apply to everything - I m not going to start
    Message 1 of 12 , May 31, 2006
    • 0 Attachment
      Personally, I like to know what the path started out as.  I can have it drop used-up WIDEn-N's, but if I do it'll apply to everything - I'm not going to start adding special exceptions for certain aliases.


      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Cap Pennell
      Sent: Tuesday, May 30, 2006 2:30 PM
      To: tracker2@yahoogroups.com
      Subject: RE: [tracker2] Firmware build 53875

      Either way works the same (allowing the next digi to operate the next "address" in the mobile user's digipath) but leaving the WIDE1* in the "path history" can help show other users that the digipath started as WIDE1-1 (so they too can have success using that path).  In other words, it preserves more of the "path history".
       
      Most of Central California's high level WIDEn-N digis are still using the older KPC-3 v8.2 TNCs that now must include WIDE1-1 in their UIdigi command (and I suspect that's true in many other areas too, as those were the only WIDEn-N capable TNCs about 9 and 10 years ago when WIDEn-N began and the high digis were installed) , and so they now turn a mobile user's
      WIDE1-1,WIDE2-1
      into
      MYcall*,WIDE2-1
       
      But the newer KPC-3 and KPC-3Plus v8.3 and v9.x TNCs (which don't need UIdigi WIDE1-1) now turn a mobile user's
      WIDE1-1,WIDE2-1
      into
      MYcall,WIDE1*,WIDE2-1
       
      Both techniques allow that next (WIDE2-1) hop to be operated by a second digipeater, and that's the most important thing.
      73, Cap KE6AFE
       
       -----Original Message-----
      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com]On Behalf Of Wes Johnston
      Sent: Tuesday, May 30, 2006 10:59 AM
      To: tracker2@yahoogroups.com
      Subject: Re: [tracker2] Firmware build 53875

      Seems to me to be a waste to leave the WIDE1-0* in there when it's used up.  Just taking up space, not really conveying any _information_.
       
      Older kpc's leave it in there.... but I'd really like to see:
      ai4px-15>aprs v WIDE1-1,WIDE2-2
      become
      ai4px-15>aprs v digicall*,WIDE2-2
       
      NOT
      ai4px-15>aprs v digicall*,WIDE1*,WIDE2-2
       
      Wes
      ai4px
      ----- Original Message -----
      From: scott@...
      Sent: Tuesday, May 30, 2006 12:36 PM
      Subject: RE: [tracker2] Firmware build 53875

      It'll do the first one... should the replacement that you show happen any time a WIDEn-N is used up?
       
      Scott


      From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Cap Pennell
      Sent: Saturday, May 27, 2006 9:09 PM
      To: tracker2@yahoogroups.com
      Subject: RE: [tracker2] Firmware build 53875

      Does
      ALIAS WIDE, HOPLIMIT 1, DIGIID ON: APRS via WIDE1-1,WIDE2-1 become APRS via MYCALL, WIDE1*,WIDE2-1
      (with the "*" after WIDE1)  ?
      Or become APRS via MYCALL*,WIDE2-1 (or something like that, to allow the second hop from that next digi down the road) ?  Hope so.
      73, Cap KE6AFE
       
    Your message has been successfully submitted and would be delivered to recipients shortly.