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

T2-135 Decode Problem

Expand Messages
  • jkm_dotnet
    Hello to all, I just purchased a T2-135 and received it in the mail today. I ve gotten it installed and configured and it seems to beacon just fine. However,
    Message 1 of 3 , Dec 1, 2008
    • 0 Attachment
      Hello to all,

      I just purchased a T2-135 and received it in the mail today. I've
      gotten it installed and configured and it seems to beacon just fine.
      However, when I've tried to receive with it, I notice that it's
      missing a lot of our local traffic.

      After looking at which traffic was not being decoded, it appears that
      it is any traffic coming from Kantronics KPC-3+ TNCs, version 3.83 and
      higher. I think in these versions of the TNCs, there's something
      about the audio tones they use that sound different than the other
      TNCs I've heard (like TNC2-type clones and TinyTrak/T2 devices).
      There are two digipeaters locally using KPC-3+ TNCs, version 9.1, that
      I'm unable to decode at all, one of which is the strongest signal I
      receive on APRS here at the house. The digis running KPC-3 version
      8.2 all decode fine, although it still seems like it's missing a few
      of those packets occasionally as well, but that could just be from
      packet collisions.

      I've been through some earlier threads that seem to point to a solder
      issue with these boards, but they looked like they were from 6 months
      ago, so I'm not sure if that's what's happening here. If it is, I
      know that I'd melt the board if I tried any touch-up myself; I'm
      definitely not handy with a soldering iron :-( Is it possible that
      something else is going on? Is anyone else seeing this happening and
      know of a resolution?

      Any help would be greatly appreciated!

      Thanks in advance!

      Justin Munger/W1IX
    • Scott Miller
      ... Interesting.. I wonder if they re using v.23 tones or something. Without switching the TNCs around it s hard to say for sure that it s not a radio problem,
      Message 2 of 3 , Dec 2, 2008
      • 0 Attachment
        > After looking at which traffic was not being decoded, it appears that
        > it is any traffic coming from Kantronics KPC-3+ TNCs, version 3.83 and
        > higher. I think in these versions of the TNCs, there's something
        > about the audio tones they use that sound different than the other

        Interesting.. I wonder if they're using v.23 tones or something.
        Without switching the TNCs around it's hard to say for sure that it's
        not a radio problem, though.

        > I've been through some earlier threads that seem to point to a solder
        > issue with these boards, but they looked like they were from 6 months
        > ago, so I'm not sure if that's what's happening here. If it is, I

        That shouldn't be it. They're all tested more thoroughly now before
        shipping. Have you tried setting the radio to narrow mode? F + MHZ
        should select narrow/wide.

        If you could get a good recording of the traffic off the air, I can take
        a look at it.

        Scott
      • jkm_dotnet
        HI Scott and all, I ve taken a 60 second audio sample from off the air which has a good sampling of our local digi. I ran it through AGW Packet Engine and
        Message 3 of 3 , Dec 3, 2008
        • 0 Attachment
          HI Scott and all,

          I've taken a 60 second audio sample from off the air which has a good
          sampling of our local digi. I ran it through AGW Packet Engine and
          obtained the following traffic that it decoded:

          13:14:37R NE1LL>EABP7S,K8GPS-4*,WIDE2-1 Port=1 <UI R Len=15>:
          `nSQl )>/>"7"}
          13:14:38R NE1LL>EABP7S,K8GPS-4*,N8WCT-4*,WIDE2* Port=1 <UI R Len=15>:
          `nSQl )>/>"7"}
          13:14:42R K8KDR-1>APU25N,WIDE2-2 Port=1 <UI C Len=56>:
          >031603zMatt - k8kdr@... Running: UI-View32 V2.03
          13:14:43R K8KDR-1>APU25N,K8GPS-4*,WIDE2-1 Port=1 <UI C Len=56>:
          >031603zMatt - k8kdr@... Running: UI-View32 V2.03
          13:14:44R K8KDR-1>APU25N,N8WCT-4*,WIDE2-1 Port=1 <UI C Len=56>:
          >031603zMatt - k8kdr@... Running: UI-View32 V2.03
          13:14:52R KX8O-5>APOT02,W8GUC*,WIDE1*,K8GPS-4*,WIDE2 Port=1 <UI Len=43>:
          /031803z3938.35N/08414.20W>004/018/A=000999
          13:14:57R KB1GQT-1>S9UV3X,KC8JDS-4*,WIDE1*,K8GPS-4*,WIDE3-2 Port=1 <UI
          R Len=15>:
          'n00!fy>/]"7(}
          13:15:03R KC8KQE>APU25N,W8GUC*,K8GPS-4*,WIDE2 Port=1 <UI C Len=61>:
          ;146.7300 *131725z3955.47N/08351.37WmW8OG Repeater-1 PL 77.0
          13:15:11R KX8O-5>APOT02,W8GUC*,WIDE1*,K8GPS-4*,WIDE2 Port=1 <UI Len=43>:
          /031804z3938.40N/08414.37W>328/012/A=000992
          13:15:17R KC8KQE>APU25N,W8GUC*,K8GPS-4*,WIDE2 Port=1 <UI C Len=33>:
          >262106zMonitor 146.730, PL77Htz
          13:15:24R N8MFS>BEACON,WIDE*,WIDE Port=1 <UI Len=54>:
          =4042.80N/08233.50W#PHG6580/A=1419/N8MFS MANSFIELD OH
          13:15:30R KB8VUL>APRS,WIDE2-1 Port=1 <UI C Len=50>:
          !4011.01N/08237.33W- PHG6390/WIDE Johnstown, Ohio
          13:15:31R KB8VUL>APRS,K8GPS-4*,WIDE2 Port=1 <UI C Len=50>:
          !4011.01N/08237.33W- PHG6390/WIDE Johnstown, Ohio
          13:15:32R KB8VUL>APRS,KB8UVN-11*,WIDE2* Port=1 <UI C Len=50>:
          !4011.01N/08237.33W- PHG6390/WIDE Johnstown, Ohio
          13:15:33R KB8VUL>APRS,N8WCT-4*,WIDE2* Port=1 <UI C Len=50>:
          !4011.01N/08237.33W- PHG6390/WIDE Johnstown, Ohio

          N8WCT-4 is the KPC3+ v9.1 TNC that I'm unable to decode with the
          T2-135. Also there was a packet from KC8JDS-4, the other KPC3+ v9.1
          TNC in the area, but AGWPE didn't decode that either. However, it
          isn't very strong here, so the packet probably got squashed by
          something else. K8GPS-4 is a KPC3+ 8.2 TNC which I'm able to decode
          flawlessly here. Also, the N8MFS packet with the WIDE* was digipeated
          through K8GPS-10, also a KPC3+ v8.2 which is only one signal bar
          maximum here so the T2-135 is decoding weak signals nicely! I also
          did try the narrow FM mode but found the decoding situation to be the
          same.

          I will post the recording in the files area as W1IXPacketAudio.wav. I
          really appreciate your help with this, the more I play with the
          T2-135, the more I'm lovin' it, and think it would make a fantastic
          portable digipeater, so I'm looking forward to what we all find out!

          73 and thanks again!

          Justin/W1IX

          --- In tracker2@yahoogroups.com, Scott Miller <scott@...> wrote:
          >
          > > After looking at which traffic was not being decoded, it appears that
          > > it is any traffic coming from Kantronics KPC-3+ TNCs, version 3.83 and
          > > higher. I think in these versions of the TNCs, there's something
          > > about the audio tones they use that sound different than the other
          >
          > Interesting.. I wonder if they're using v.23 tones or something.
          > Without switching the TNCs around it's hard to say for sure that it's
          > not a radio problem, though.
          >
          > > I've been through some earlier threads that seem to point to a solder
          > > issue with these boards, but they looked like they were from 6 months
          > > ago, so I'm not sure if that's what's happening here. If it is, I
          >
          > That shouldn't be it. They're all tested more thoroughly now before
          > shipping. Have you tried setting the radio to narrow mode? F + MHZ
          > should select narrow/wide.
          >
          > If you could get a good recording of the traffic off the air, I can
          take
          > a look at it.
          >
          > Scott
          >
        Your message has been successfully submitted and would be delivered to recipients shortly.