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

1458RE: [tracker2] Question

Expand Messages
  • Jon
    Mar 5, 2007
    • 0 Attachment
      --- Cap Pennell <ke6afe@...> wrote:

      > Some types of digis will insert their own callsign
      > into the digipeated
      > packet one or the other of those ways you spotted.
      > The way either digi type
      > _operates_ is not different.
      >
      > Depending on the digipeater hardware in use, a
      > user's packet starting out
      > addressed via WIDE1-1,WIDE2-1 may come out of the
      > first digi (DIGIA) showing
      > as
      > DIGIA,WIDE1*,WIDE2-1
      > or as
      Its a tracker2 and its coming out as
      DIGIA*, WIDE1* WIDE2-1

      Which is really what I was querying

      Regards
      John

      > DIGIA*,WIDE2-1
      >
      > In either case, the last "*" (immediately preceding
      > WIDE2-1) indicates that
      > second (WIDE2-1) hop is still available to be
      > operated by the next digi in
      > line. Operation is the same in either of those
      > "DIGIA" cases.
      > 73, Cap KE6AFE
      >
      > P.S. After the second hop of the mobile user's
      > WIDE1-1,WIDE2-1 path, the
      > packet's path may look like either:
      > DIGIA,WIDE1,DIGIB*,WIDE2
      > or
      > DIGIA,DIGIB*,WIDE2
      >
      > > -----Original Message-----
      > > From: tracker2@yahoogroups.com
      > [mailto:tracker2@yahoogroups.com]On
      > > Behalf Of Jon
      > > Sent: Sunday, March 04, 2007 12:35 PM
      > > To: tracker2@yahoogroups.com
      > > Subject: [tracker2] Question
      > >
      > >
      > > Firstly I must preface the question with the
      > caveat,
      > > that I don't know what the firmware version of the
      > > tracker2 is, so I must visit the site this week
      > and
      > > update it.
      > >
      > > I was watching APRS traffic this afternoon as we
      > have
      > > just put another digi/Igate in place when I
      > spotted
      > > this.
      > > 2m: fm EI3JB-9 to U2QTQR via WIDE1-1 WIDE2-1 ctl
      > UIv
      > > pid=F0(Text) len 15 19:08:40
      > > 0000 '}^dl .>/]"3r}.
      > > 2m: fm EI3JB-9 to U2QTQR via EI2WCD-2* WIDE1*
      > WIDE2-1
      > > ctl UIv pid=F0(Text) len 15 19:08:41
      > > 0000 '}^dl .>/]"3r}.
      > > 2m: fm EI3JB-9 to U2QTQR via EI2WWD-3* WIDE2-1 ctl
      > UIv
      > > pid=F0(Text) len 15 19:08:43
      > > 0000 '}^dl .>/]"3r}.
      > >
      > > My question is why the WIDE1* in the second
      > packet? I
      > > know that the WIDE1 has been used up, but I
      > > (incorrectly?) assumed that the digipeater would
      > just
      > > replace the WIDE1-1 with its own callsign and
      > continue
      > > on, like the third line.
      > >
      > > Regards
      > > John
      >
      >
      >
      > ------------------------ Yahoo! Groups Sponsor
      > --------------------~-->
      > Great things are happening at Yahoo! Groups. See
      > the new email design.
      >
      http://us.click.yahoo.com/lOt0.A/hOaOAA/yQLSAA/ELTolB/TM
      >
      --------------------------------------------------------------------~->
      >
      >
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
      >




      ___________________________________________________________
      To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
    • Show all 17 messages in this topic