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

Re: [aprsisce] APRS Packets sent/received but not decoding

Expand Messages
  • Patrick
    You are likely over or under driving your radio. Check the kpc manual for how to adjust the transmit level and adjust it to have around 3kHz of deviation (or
    Message 1 of 18 , Oct 2, 2012
    • 0 Attachment
      You are likely over or under driving your radio.  Check the kpc manual for how to adjust the transmit level and adjust it to have around 3kHz of deviation (or if you don't have a meter take the level adjust it so the audio level of your transmission sounds around the same as other stations you hear on your HT... takes a bit of trial and error. )

      p

      On 10/2/2012 6:15 PM, nt5sm_scott wrote:
       

      I just finished installing a new I-gate using a Yaesu FT-7800 / KPC-3+/ APRSIS32 combination. I built the TNC-Radio cable per recommendations and powered up the KPC-3 in KISS mode. On the receiving end things work perfectly with good IGating. On the transmit side however, even though a beacon is initiated/transmitted/and audio is received with a TH-D72, no packets are being decoded from the Yaesu by the HT. Also, when I connect the HT to another PC and open APRSIS32, no packets are displayed on the port log. The HT works fine handling other received packets.

      Don't know if this is a transmitter deviation level issue or something else in the setup. Here is a sampling of 3 traces:

      IGate Trace:

      WinMain:2012-10-02T21:47:38.421 RFtoIS:[SimplyKiss]IGated KC5DAQ-8>APT311,WR5AAA-1*,WIDE2-1,qAR,NT5SM:!2958.81N/09543.19Wk294/057/A=000160
      WinMain:2012-10-02T21:47:40.078 RFtoIS:[SimplyKiss]IGated KT5TK-12>APOT21,WIDE2-1,qAR,NT5SM:/214739h2947.18N/09548.99W#/A=000193 14.0V HDOP02.7 SATS05 No Label Digi
      WinMain:2012-10-02T21:47:49.515 RFtoIS:[SimplyKiss]IGated N5LUY-7>APT311,WD5CFJ-10*,KT5TK-12*,WIDE2-1,qAR,NT5SM:>Town Car
      WinMain:2012-10-02T21:47:56.921 RFtoIS:[SimplyKiss]IGated KC5TIL-3>APTW01,W5BEC-5*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:_10031544c255s003g007t077r000p000P000h23b10139tRSW

      TRANSMIT TRACE:

      2012-10-02T13:50:08.812 Restore Saved Enable
      2012-10-02T13:50:08.812 Transmit(IS) NT5SM>APWW10,WIDE 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0
      012-10-02T14:19:58.421 Transmit(IS+RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1::NT5SM-9 :ack0
      2012-10-02T14:19:58.421 Transmit(RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1::NT5SM-9 :ack0
      2012-10-02T14:20:13.984 Transmit(IS+RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1::NT5SM-9 :received ok{GN}
      2012-10-02T14:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE 1-1,WIDE2-1:T#216,100,048,002,500,000,10000000
      2012-10-02T14:22:47.984 Transmit(IS+RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
      2012-10-02T14:22:47.984 Transmit(INT) NT5SM>APWW10,WIDE 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
      2012-10-02T21:03:08.812 Transmit(IS) NT5SM>APWW10,WIDE 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=11,DIR_CNT=4,RF_CNT=14
      2012-10-02T21:03:27.968 Transmit(RF) NT5SM>DX,RFONLY:DX de NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi 2103z
      2012-10-02T21:03:27.968 SimplyKiss(Simply(KISS)) NOT Queueing NT5SM>DX,RFONLY:DX de NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi 2103z
      2012-10-02T21:03:27.968 Transmit(IS+RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1:>022103zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
      2012-10-02T21:16:37.296 Transmit(IS+RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
      2012-10-02T21:16:37.296 Transmit(INT) NT5SM>APWW10,WIDE 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
      2012-10-02T21:18:38.812 Transmit(IS+RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1:>022118zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
      2012-10-02T21:22:04.296 Transmit(IS+RF) NT5SM>APWW10,WIDE 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
      2012-10-02T21:22:04.296 Transmit(INT) NT5SM>APWW10,WIDE 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
      2012-10-02T21:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE 1-1,WIDE2-1:T#244,100,048,002,500,000,10000000

      sIMPLY KISS PORT TRACE:

      Port(SimplyKiss):2012-10-02T21:36:01.453 Closing COM1:9600,N,8,1
      Port(SimplyKiss):2012-10-02T21:36:01.453 Command[1]:~
      Port(SimplyKiss):2012-10-02T21:36:01.468 Restarting Reader...
      Port(SimplyKiss):2012-10-02T21:36:01.468 CpReader Running on COM1:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
      Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1:9600,N,8,1
      Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1 with 4 Args
      Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Packet Length 64 Version 2
      Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:ServiceMask 0x1 Reserved1 0x0
      Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:MaxQueue Tx 0 Rx 0 Baud 268435456
      Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider SubType 1 Capabilities 0xFF
      Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Settable Params 127 Baud 0x1006FFFF Data 0xF StopParity 0x1F07
      Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Current Queue Tx 0 Rx 4096
      Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider Specifics 0x0 0x0
      Port(SimplyKiss):2012-10-02T21:36:01.468 CpOpen:Port COM1 9600,N,8,1 !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense RTS_ENABLE
      Port(SimplyKiss):2012-10-02T21:36:01.468 Opened COM1:9600,N,8,1, Flushing 0 in TransmitQueue, Sending 1 OpenCmds
      Port(SimplyKiss):2012-10-02T21:36:01.468 Command[1]:~
      Port(SimplyKiss):2012-10-02T21:37:17.468 KISS:KT5TK-12>APOT21,WIDE2-1:/213717h2947.18N/09548.99W# 13.9V HDOP02.7 SATS06 No Label Digi (105)
      Port(SimplyKiss):2012-10-02T21:37:54.562 KISS:W0FCM-2>R9TW1P,WR5AAA-1*,KT5TK-12*,WIDE6*:`{Ef!^c>/]"45}= (61)
      Port(SimplyKiss):2012-10-02T21:38:54.671 KISS:KD5TAZ-9>APT311,W5BEC-5*,WD5CFJ-10*,KT5TK-12*:>V8 Tracker (114)

      Many thanks,

      Scott, nt5sm and
      nt5sm-9 (HT)


    • ve7did
      Scott: Also remember that the KPC3+ in KISS mode will start to generate delayed packets in a few days/weeks. There is all kinds of documentation available
      Message 2 of 18 , Oct 2, 2012
      • 0 Attachment
        Scott:

        Also remember that the KPC3+ in KISS mode will start to generate delayed
        packets in a few days/weeks. There is all kinds of documentation
        available from a few years ago. Kantronics never fixed the bug as far as
        I know. If you can restart the KISS mode periodically it will fix the
        problem.

        Propagation Knows No Boundaries
        73 de Tom, ve7did



        Patrick wrote:
        >
        >
        > You are likely over or under driving your radio. Check the kpc manual
        > for how to adjust the transmit level and adjust it to have around 3kHz
        > of deviation (or if you don't have a meter take the level adjust it so
        > the audio level of your transmission sounds around the same as other
        > stations you hear on your HT... takes a bit of trial and error. )
        >
        > p
        >
        > On 10/2/2012 6:15 PM, nt5sm_scott wrote:
        >>
        >>
        >> I just finished installing a new I-gate using a Yaesu FT-7800 /
        >> KPC-3+/ APRSIS32 combination. I built the TNC-Radio cable per
        >> recommendations and powered up the KPC-3 in KISS mode. On the
        >> receiving end things work perfectly with good IGating. On the
        >> transmit side however, even though a beacon is
        >> initiated/transmitted/and audio is received with a TH-D72, no packets
        >> are being decoded from the Yaesu by the HT. Also, when I connect the
        >> HT to another PC and open APRSIS32, no packets are displayed on the
        >> port log. The HT works fine handling other received packets.
        >>
        >> Don't know if this is a transmitter deviation level issue or
        >> something else in the setup. Here is a sampling of 3 traces:
        >>
        >> IGate Trace:
        >>
        >> WinMain:2012-10-02T21:47:38.421 RFtoIS:[SimplyKiss]IGated
        >> KC5DAQ-8>APT311,WR5AAA-1*,WIDE2-1,qAR,NT5SM:!2958.81N/09543.19Wk294/057/A=000160
        >> WinMain:2012-10-02T21:47:40.078 RFtoIS:[SimplyKiss]IGated
        >> KT5TK-12>APOT21,WIDE2-1,qAR,NT5SM:/214739h2947.18N/09548.99W#/A=000193
        >> 14.0V HDOP02.7 SATS05 No Label Digi
        >> WinMain:2012-10-02T21:47:49.515 RFtoIS:[SimplyKiss]IGated
        >> N5LUY-7>APT311,WD5CFJ-10*,KT5TK-12*,WIDE2-1,qAR,NT5SM:>Town Car
        >> WinMain:2012-10-02T21:47:56.921 RFtoIS:[SimplyKiss]IGated
        >> KC5TIL-3>APTW01,W5BEC-5*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:_10031544c255s003g007t077r000p000P000h23b10139tRSW
        >>
        >> TRANSMIT TRACE:
        >>
        >> 2012-10-02T13:50:08.812 Restore Saved Enable
        >> 2012-10-02T13:50:08.812 Transmit(IS) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0
        >> 012-10-02T14:19:58.421 Transmit(IS+RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1::NT5SM-9 :ack0
        >> 2012-10-02T14:19:58.421 Transmit(RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1::NT5SM-9 :ack0
        >> 2012-10-02T14:20:13.984 Transmit(IS+RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1::NT5SM-9 :received ok{GN}
        >> 2012-10-02T14:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:T#216,100,048,002,500,000,10000000
        >> 2012-10-02T14:22:47.984 Transmit(IS+RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
        >> 2012-10-02T14:22:47.984 Transmit(INT) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
        >> 2012-10-02T21:03:08.812 Transmit(IS) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=11,DIR_CNT=4,RF_CNT=14
        >> 2012-10-02T21:03:27.968 Transmit(RF) NT5SM>DX,RFONLY:DX de
        >> NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi 2103z
        >> 2012-10-02T21:03:27.968 SimplyKiss(Simply(KISS)) NOT Queueing
        >> NT5SM>DX,RFONLY:DX de NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi
        >> 2103z
        >> 2012-10-02T21:03:27.968 Transmit(IS+RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:>022103zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
        >> 2012-10-02T21:16:37.296 Transmit(IS+RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
        >> 2012-10-02T21:16:37.296 Transmit(INT) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
        >> 2012-10-02T21:18:38.812 Transmit(IS+RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:>022118zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
        >> 2012-10-02T21:22:04.296 Transmit(IS+RF) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
        >> 2012-10-02T21:22:04.296 Transmit(INT) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
        >> 2012-10-02T21:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE
        >> 1-1,WIDE2-1:T#244,100,048,002,500,000,10000000
        >>
        >> sIMPLY KISS PORT TRACE:
        >>
        >> Port(SimplyKiss):2012-10-02T21:36:01.453 Closing COM1:9600,N,8,1
        >> Port(SimplyKiss):2012-10-02T21:36:01.453 Command[1]:~
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 Restarting Reader...
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 CpReader Running on
        >> COM1:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1:9600,N,8,1
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1 with 4 Args
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Packet Length 64 Version 2
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:ServiceMask 0x1
        >> Reserved1 0x0
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:MaxQueue Tx 0 Rx 0 Baud
        >> 268435456
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider SubType 1
        >> Capabilities 0xFF
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Settable Params 127
        >> Baud 0x1006FFFF Data 0xF StopParity 0x1F07
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Current Queue Tx 0 Rx 4096
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider Specifics 0x0 0x0
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 CpOpen:Port COM1 9600,N,8,1
        >> !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense
        >> RTS_ENABLE
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 Opened COM1:9600,N,8,1,
        >> Flushing 0 in TransmitQueue, Sending 1 OpenCmds
        >> Port(SimplyKiss):2012-10-02T21:36:01.468 Command[1]:~
        >> Port(SimplyKiss):2012-10-02T21:37:17.468
        >> KISS:KT5TK-12>APOT21,WIDE2-1:/213717h2947.18N/09548.99W# 13.9V
        >> HDOP02.7 SATS06 No Label Digi (105)
        >> Port(SimplyKiss):2012-10-02T21:37:54.562
        >> KISS:W0FCM-2>R9TW1P,WR5AAA-1*,KT5TK-12*,WIDE6*:`{Ef!^c>/]"45}= (61)
        >> Port(SimplyKiss):2012-10-02T21:38:54.671
        >> KISS:KD5TAZ-9>APT311,W5BEC-5*,WD5CFJ-10*,KT5TK-12*:>V8 Tracker (114)
        >>
        >> Many thanks,
        >>
        >> Scott, nt5sm and
        >> nt5sm-9 (HT)
        >>
        >
        >
        >
        >
      • Lynn W Deffenbaugh (Mr)
        You can read all about this and watch a few demonstration videos at: http://blog.aprs.fi/2011/03/kantronics-kpc3-considered-harmful.html I plan to build in an
        Message 3 of 18 , Oct 3, 2012
        • 0 Attachment
          You can read all about this and watch a few demonstration videos at:

          http://blog.aprs.fi/2011/03/kantronics-kpc3-considered-harmful.html

          I plan to build in an auto-disable/enable timer feature in KISS-mode
          ports to work around this known issue.

          Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

          On 10/2/2012 11:56 PM, ve7did wrote:
          > Scott:
          >
          > Also remember that the KPC3+ in KISS mode will start to generate delayed
          > packets in a few days/weeks. There is all kinds of documentation
          > available from a few years ago. Kantronics never fixed the bug as far as
          > I know. If you can restart the KISS mode periodically it will fix the
          > problem.
          >
          > Propagation Knows No Boundaries
          > 73 de Tom, ve7did
          >
          >
          >
          > Patrick wrote:
          >>
          >> You are likely over or under driving your radio. Check the kpc manual
          >> for how to adjust the transmit level and adjust it to have around 3kHz
          >> of deviation (or if you don't have a meter take the level adjust it so
          >> the audio level of your transmission sounds around the same as other
          >> stations you hear on your HT... takes a bit of trial and error. )
          >>
          >> p
          >>
          >> On 10/2/2012 6:15 PM, nt5sm_scott wrote:
          >>>
          >>>
          >>> I just finished installing a new I-gate using a Yaesu FT-7800 /
          >>> KPC-3+/ APRSIS32 combination. I built the TNC-Radio cable per
          >>> recommendations and powered up the KPC-3 in KISS mode. On the
          >>> receiving end things work perfectly with good IGating. On the
          >>> transmit side however, even though a beacon is
          >>> initiated/transmitted/and audio is received with a TH-D72, no packets
          >>> are being decoded from the Yaesu by the HT. Also, when I connect the
          >>> HT to another PC and open APRSIS32, no packets are displayed on the
          >>> port log. The HT works fine handling other received packets.
          >>>
          >>> Don't know if this is a transmitter deviation level issue or
          >>> something else in the setup. Here is a sampling of 3 traces:
          >>>
          >>> IGate Trace:
          >>>
          >>> WinMain:2012-10-02T21:47:38.421 RFtoIS:[SimplyKiss]IGated
          >>> KC5DAQ-8>APT311,WR5AAA-1*,WIDE2-1,qAR,NT5SM:!2958.81N/09543.19Wk294/057/A=000160
          >>> WinMain:2012-10-02T21:47:40.078 RFtoIS:[SimplyKiss]IGated
          >>> KT5TK-12>APOT21,WIDE2-1,qAR,NT5SM:/214739h2947.18N/09548.99W#/A=000193
          >>> 14.0V HDOP02.7 SATS05 No Label Digi
          >>> WinMain:2012-10-02T21:47:49.515 RFtoIS:[SimplyKiss]IGated
          >>> N5LUY-7>APT311,WD5CFJ-10*,KT5TK-12*,WIDE2-1,qAR,NT5SM:>Town Car
          >>> WinMain:2012-10-02T21:47:56.921 RFtoIS:[SimplyKiss]IGated
          >>> KC5TIL-3>APTW01,W5BEC-5*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:_10031544c255s003g007t077r000p000P000h23b10139tRSW
          >>>
          >>> TRANSMIT TRACE:
          >>>
          >>> 2012-10-02T13:50:08.812 Restore Saved Enable
          >>> 2012-10-02T13:50:08.812 Transmit(IS) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0
          >>> 012-10-02T14:19:58.421 Transmit(IS+RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1::NT5SM-9 :ack0
          >>> 2012-10-02T14:19:58.421 Transmit(RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1::NT5SM-9 :ack0
          >>> 2012-10-02T14:20:13.984 Transmit(IS+RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1::NT5SM-9 :received ok{GN}
          >>> 2012-10-02T14:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:T#216,100,048,002,500,000,10000000
          >>> 2012-10-02T14:22:47.984 Transmit(IS+RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
          >>> 2012-10-02T14:22:47.984 Transmit(INT) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
          >>> 2012-10-02T21:03:08.812 Transmit(IS) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=11,DIR_CNT=4,RF_CNT=14
          >>> 2012-10-02T21:03:27.968 Transmit(RF) NT5SM>DX,RFONLY:DX de
          >>> NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi 2103z
          >>> 2012-10-02T21:03:27.968 SimplyKiss(Simply(KISS)) NOT Queueing
          >>> NT5SM>DX,RFONLY:DX de NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi
          >>> 2103z
          >>> 2012-10-02T21:03:27.968 Transmit(IS+RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:>022103zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
          >>> 2012-10-02T21:16:37.296 Transmit(IS+RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
          >>> 2012-10-02T21:16:37.296 Transmit(INT) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
          >>> 2012-10-02T21:18:38.812 Transmit(IS+RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:>022118zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
          >>> 2012-10-02T21:22:04.296 Transmit(IS+RF) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
          >>> 2012-10-02T21:22:04.296 Transmit(INT) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
          >>> 2012-10-02T21:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE
          >>> 1-1,WIDE2-1:T#244,100,048,002,500,000,10000000
          >>>
          >>> sIMPLY KISS PORT TRACE:
          >>>
          >>> Port(SimplyKiss):2012-10-02T21:36:01.453 Closing COM1:9600,N,8,1
          >>> Port(SimplyKiss):2012-10-02T21:36:01.453 Command[1]:~
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Restarting Reader...
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 CpReader Running on
          >>> COM1:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1:9600,N,8,1
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1 with 4 Args
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Packet Length 64 Version 2
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:ServiceMask 0x1
          >>> Reserved1 0x0
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:MaxQueue Tx 0 Rx 0 Baud
          >>> 268435456
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider SubType 1
          >>> Capabilities 0xFF
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Settable Params 127
          >>> Baud 0x1006FFFF Data 0xF StopParity 0x1F07
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Current Queue Tx 0 Rx 4096
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider Specifics 0x0 0x0
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 CpOpen:Port COM1 9600,N,8,1
          >>> !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense
          >>> RTS_ENABLE
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Opened COM1:9600,N,8,1,
          >>> Flushing 0 in TransmitQueue, Sending 1 OpenCmds
          >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Command[1]:~
          >>> Port(SimplyKiss):2012-10-02T21:37:17.468
          >>> KISS:KT5TK-12>APOT21,WIDE2-1:/213717h2947.18N/09548.99W# 13.9V
          >>> HDOP02.7 SATS06 No Label Digi (105)
          >>> Port(SimplyKiss):2012-10-02T21:37:54.562
          >>> KISS:W0FCM-2>R9TW1P,WR5AAA-1*,KT5TK-12*,WIDE6*:`{Ef!^c>/]"45}= (61)
          >>> Port(SimplyKiss):2012-10-02T21:38:54.671
          >>> KISS:KD5TAZ-9>APT311,W5BEC-5*,WD5CFJ-10*,KT5TK-12*:>V8 Tracker (114)
          >>>
          >>> Many thanks,
          >>>
          >>> Scott, nt5sm and
          >>> nt5sm-9 (HT)
          >>>
          >>
          >>
          >>
          >
          > ------------------------------------
          >
          > Yahoo! Groups Links
          >
          >
          >
          >
        • nt5sm_scott
          Thanks to all who offered suggestions....here s what I ve done so far: 1. Hard reset the kpc-3+ to place it back to Command mode. 2. Reset the XMITLVL from 100
          Message 4 of 18 , Oct 4, 2012
          • 0 Attachment
            Thanks to all who offered suggestions....here's what I've done so far:

            1. Hard reset the kpc-3+ to place it back to Command mode.
            2. Reset the XMITLVL from 100 to 80 (%).
            3. Restarted and tested operation by successfully using "Airmail" to sucessfully send an email over Winlink 2000.
            4. Placed the TNC back to KISS and Reset.

            Again receiving packets successfully on aprsis32, but transmitted beacons still not displaying on TH-D72 HT or being digipeated by other stations. Where to go next to trace this mystery?

            73,
            Scott, nt5sm
            -------------

            --- In aprsisce@yahoogroups.com, "Lynn W Deffenbaugh (Mr)" <kj4erj@...> wrote:
            >
            > You can read all about this and watch a few demonstration videos at:
            >
            > http://blog.aprs.fi/2011/03/kantronics-kpc3-considered-harmful.html
            >
            > I plan to build in an auto-disable/enable timer feature in KISS-mode
            > ports to work around this known issue.
            >
            > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
            >
            > On 10/2/2012 11:56 PM, ve7did wrote:
            > > Scott:
            > >
            > > Also remember that the KPC3+ in KISS mode will start to generate delayed
            > > packets in a few days/weeks. There is all kinds of documentation
            > > available from a few years ago. Kantronics never fixed the bug as far as
            > > I know. If you can restart the KISS mode periodically it will fix the
            > > problem.
            > >
            > > Propagation Knows No Boundaries
            > > 73 de Tom, ve7did
            > >
            > >
            > >
            > > Patrick wrote:
            > >>
            > >> You are likely over or under driving your radio. Check the kpc manual
            > >> for how to adjust the transmit level and adjust it to have around 3kHz
            > >> of deviation (or if you don't have a meter take the level adjust it so
            > >> the audio level of your transmission sounds around the same as other
            > >> stations you hear on your HT... takes a bit of trial and error. )
            > >>
            > >> p
            > >>
            > >> On 10/2/2012 6:15 PM, nt5sm_scott wrote:
            > >>>
            > >>>
            > >>> I just finished installing a new I-gate using a Yaesu FT-7800 /
            > >>> KPC-3+/ APRSIS32 combination. I built the TNC-Radio cable per
            > >>> recommendations and powered up the KPC-3 in KISS mode. On the
            > >>> receiving end things work perfectly with good IGating. On the
            > >>> transmit side however, even though a beacon is
            > >>> initiated/transmitted/and audio is received with a TH-D72, no packets
            > >>> are being decoded from the Yaesu by the HT. Also, when I connect the
            > >>> HT to another PC and open APRSIS32, no packets are displayed on the
            > >>> port log. The HT works fine handling other received packets.
            > >>>
            > >>> Don't know if this is a transmitter deviation level issue or
            > >>> something else in the setup. Here is a sampling of 3 traces:
            > >>>
            > >>> IGate Trace:
            > >>>
            > >>> WinMain:2012-10-02T21:47:38.421 RFtoIS:[SimplyKiss]IGated
            > >>> KC5DAQ-8>APT311,WR5AAA-1*,WIDE2-1,qAR,NT5SM:!2958.81N/09543.19Wk294/057/A=000160
            > >>> WinMain:2012-10-02T21:47:40.078 RFtoIS:[SimplyKiss]IGated
            > >>> KT5TK-12>APOT21,WIDE2-1,qAR,NT5SM:/214739h2947.18N/09548.99W#/A=000193
            > >>> 14.0V HDOP02.7 SATS05 No Label Digi
            > >>> WinMain:2012-10-02T21:47:49.515 RFtoIS:[SimplyKiss]IGated
            > >>> N5LUY-7>APT311,WD5CFJ-10*,KT5TK-12*,WIDE2-1,qAR,NT5SM:>Town Car
            > >>> WinMain:2012-10-02T21:47:56.921 RFtoIS:[SimplyKiss]IGated
            > >>> KC5TIL-3>APTW01,W5BEC-5*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:_10031544c255s003g007t077r000p000P000h23b10139tRSW
            > >>>
            > >>> TRANSMIT TRACE:
            > >>>
            > >>> 2012-10-02T13:50:08.812 Restore Saved Enable
            > >>> 2012-10-02T13:50:08.812 Transmit(IS) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=0,DIR_CNT=0,RF_CNT=0
            > >>> 012-10-02T14:19:58.421 Transmit(IS+RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1::NT5SM-9 :ack0
            > >>> 2012-10-02T14:19:58.421 Transmit(RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1::NT5SM-9 :ack0
            > >>> 2012-10-02T14:20:13.984 Transmit(IS+RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1::NT5SM-9 :received ok{GN}
            > >>> 2012-10-02T14:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:T#216,100,048,002,500,000,10000000
            > >>> 2012-10-02T14:22:47.984 Transmit(IS+RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
            > >>> 2012-10-02T14:22:47.984 Transmit(INT) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:@142247h2936.74N/09543.61WI
            > >>> 2012-10-02T21:03:08.812 Transmit(IS) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=11,DIR_CNT=4,RF_CNT=14
            > >>> 2012-10-02T21:03:27.968 Transmit(RF) NT5SM>DX,RFONLY:DX de
            > >>> NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi 2103z
            > >>> 2012-10-02T21:03:27.968 SimplyKiss(Simply(KISS)) NOT Queueing
            > >>> NT5SM>DX,RFONLY:DX de NT5SM>SimplyKis WR5AAA-1 305 dg frm NT5SM 40mi
            > >>> 2103z
            > >>> 2012-10-02T21:03:27.968 Transmit(IS+RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:>022103zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
            > >>> 2012-10-02T21:16:37.296 Transmit(IS+RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
            > >>> 2012-10-02T21:16:37.296 Transmit(INT) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:@211637h2936.74N/09543.61WI
            > >>> 2012-10-02T21:18:38.812 Transmit(IS+RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:>022118zDX: WR5AAA-1 40.6mi 305° 21:03 2956.95N 09616.90W
            > >>> 2012-10-02T21:22:04.296 Transmit(IS+RF) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
            > >>> 2012-10-02T21:22:04.296 Transmit(INT) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:@212204h2936.74N/09543.61WII-GATE
            > >>> 2012-10-02T21:22:08.812 Transmit(INT) NT5SM>APWW10,WIDE
            > >>> 1-1,WIDE2-1:T#244,100,048,002,500,000,10000000
            > >>>
            > >>> sIMPLY KISS PORT TRACE:
            > >>>
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.453 Closing COM1:9600,N,8,1
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.453 Command[1]:~
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Restarting Reader...
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 CpReader Running on
            > >>> COM1:9600,N,8,1 (1 OpenCmds, 1 CloseCmds)
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1:9600,N,8,1
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Opening COM1 with 4 Args
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Packet Length 64 Version 2
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:ServiceMask 0x1
            > >>> Reserved1 0x0
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:MaxQueue Tx 0 Rx 0 Baud
            > >>> 268435456
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider SubType 1
            > >>> Capabilities 0xFF
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Settable Params 127
            > >>> Baud 0x1006FFFF Data 0xF StopParity 0x1F07
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Current Queue Tx 0 Rx 4096
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 COM1:Provider Specifics 0x0 0x0
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 CpOpen:Port COM1 9600,N,8,1
            > >>> !CTSFlow !DSRFlow !OutXon(2048) !InXoff(512) DTR_ENABLE !DSRSense
            > >>> RTS_ENABLE
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Opened COM1:9600,N,8,1,
            > >>> Flushing 0 in TransmitQueue, Sending 1 OpenCmds
            > >>> Port(SimplyKiss):2012-10-02T21:36:01.468 Command[1]:~
            > >>> Port(SimplyKiss):2012-10-02T21:37:17.468
            > >>> KISS:KT5TK-12>APOT21,WIDE2-1:/213717h2947.18N/09548.99W# 13.9V
            > >>> HDOP02.7 SATS06 No Label Digi (105)
            > >>> Port(SimplyKiss):2012-10-02T21:37:54.562
            > >>> KISS:W0FCM-2>R9TW1P,WR5AAA-1*,KT5TK-12*,WIDE6*:`{Ef!^c>/]"45}= (61)
            > >>> Port(SimplyKiss):2012-10-02T21:38:54.671
            > >>> KISS:KD5TAZ-9>APT311,W5BEC-5*,WD5CFJ-10*,KT5TK-12*:>V8 Tracker (114)
            > >>>
            > >>> Many thanks,
            > >>>
            > >>> Scott, nt5sm and
            > >>> nt5sm-9 (HT)
            > >>>
            > >>
            > >>
            > >>
            > >
            > > ------------------------------------
            > >
            > > Yahoo! Groups Links
            > >
            > >
            > >
            > >
            >
          • James Ewen
            ... Did you change the XMITLVL from 100 to 80, or did you change it from 502 to 401 (80% of the maximum value of 502) ... That would indicate that you are able
            Message 5 of 18 , Oct 4, 2012
            • 0 Attachment
              On Thu, Oct 4, 2012 at 6:15 PM, nt5sm_scott <sbmckee@...> wrote:

              > 1. Hard reset the kpc-3+ to place it back to Command mode.
              > 2. Reset the XMITLVL from 100 to 80 (%).

              Did you change the XMITLVL from 100 to 80, or did you change it from
              502 to 401 (80% of the maximum value of 502)

              > 3. Restarted and tested operation by successfully using "Airmail" to
              > sucessfully send an email over Winlink 2000.

              That would indicate that you are able to be decoded IF your Winlink
              2000 tests were using RF.

              > 4. Placed the TNC back to KISS and Reset.
              >
              > Again receiving packets successfully on aprsis32, but transmitted beacons
              > still not displaying on TH-D72 HT or being digipeated by other stations.

              So, can you explain how you are determining that you are not being
              digipeated? I'm not trying to be a pain, but some people base their
              observations on incomplete data.

              I'm not sure what's up with the TH-D72 not displaying the packets
              unless you have it off frequency, or not in APRS mode. If it is in
              PACKET mode, you will not display anything on screen.

              > Where to go next to trace this mystery?

              Provide more information.

              --
              James
              VE6SRV
            • Scott McKee
              Hi James, ... 502 to 401 (80% of the maximum value of 502) My oversight sorry.. I had revised from the default value of XMITLVL 100 to 80.  I see now this
              Message 6 of 18 , Oct 4, 2012
              • 0 Attachment
                Hi James,

                >Did you change the XMITLVL from 100 to 80, or did you change it from
                502 to 401 (80% of the maximum value of 502)>

                My oversight sorry.. I had revised from the default value of XMITLVL 100 to 80.  I see now this was not a percentage of max.

                <So, can you explain how you are determining that you are not being
                digipeated? I'm not trying to be a pain, but some people base their
                observations on incomplete data.>

                I'm only making this assumption as I have not heard a packet back following my beacon as (nt5sm*2) from an area digi (nearest is 13 mi away).  Is there another way to confirm this? 

                <That would indicate that you are able to be decoded IF your Winlink
                2000 tests were using RF.>  -- Correct via RF --


                <I'm not sure what's up with the TH-D72 not displaying the packets
                unless you have it off frequency, or not in APRS mode. If it is in
                PACKET mode, you will not display anything on screen.>

                 I do receive other packets normally with the HT in APRS mode either independently or in conjunction with APRSIS32 on the laptop. 


                I'm now going to kick up the XMITLVL on the KPC3+ to 150 and see if this will make a difference.  Thanks for plugging away with me.

                73,
                Scott, nt5sm




                From: James Ewen <ve6srv@...>
                To: aprsisce@yahoogroups.com
                Sent: Thursday, October 4, 2012 8:30 PM
                Subject: Re: [aprsisce] Re: APRS Packets sent/received but not decoding

                 
                On Thu, Oct 4, 2012 at 6:15 PM, nt5sm_scott <sbmckee@...> wrote:

                > 1. Hard reset the kpc-3+ to place it back to Command mode.
                > 2. Reset the XMITLVL from 100 to 80 (%).

                Did you change the XMITLVL from 100 to 80, or did you change it from
                502 to 401 (80% of the maximum value of 502)

                > 3. Restarted and tested operation by successfully using "Airmail" to
                > sucessfully send an email over Winlink 2000.

                That would indicate that you are able to be decoded IF your Winlink
                2000 tests were using RF.

                > 4. Placed the TNC back to KISS and Reset.
                >
                > Again receiving packets successfully on aprsis32, but transmitted beacons
                > still not displaying on TH-D72 HT or being digipeated by other stations.

                So, can you explain how you are determining that you are not being
                digipeated? I'm not trying to be a pain, but some people base their
                observations on incomplete data.

                I'm not sure what's up with the TH-D72 not displaying the packets
                unless you have it off frequency, or not in APRS mode. If it is in
                PACKET mode, you will not display anything on screen.

                > Where to go next to trace this mystery?

                Provide more information.

                --
                James
                VE6SRV


              • Lynn W Deffenbaugh (Mr)
                ... Give the following link a read. Especially the part about The No-Test-Equipment Packet Adjustment System .
                Message 7 of 18 , Oct 4, 2012
                • 0 Attachment
                  On 10/4/2012 10:15 PM, Scott McKee wrote:
                  I'm now going to kick up the XMITLVL on the KPC3+ to 150 and see if this will make a difference.  Thanks for plugging away with me.

                  Give the following link a read.  Especially the part about "The No-Test-Equipment Packet Adjustment System".

                  http://www.febo.com/packet/layer-one/transmit.html

                  Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

                • James Ewen
                  ... Listening to 144.390 and observing the packets being decoded is the best way. Some people like to base their observations on the APRS-IS stream, and in
                  Message 8 of 18 , Oct 4, 2012
                  • 0 Attachment
                    On Thu, Oct 4, 2012 at 8:15 PM, Scott McKee <sbmckee@...> wrote:

                    > <So, can you explain how you are determining that you are not being
                    > digipeated? I'm not trying to be a pain, but some people base their
                    > observations on incomplete data.>
                    >
                    > I'm only making this assumption as I have not heard a packet back
                    > following my beacon as (nt5sm*2) from an area digi (nearest is 13 mi away).
                    > Is there another way to confirm this?

                    Listening to 144.390 and observing the packets being decoded is the
                    best way. Some people like to base their observations on the APRS-IS
                    stream, and in your case, being on the internet, you can not see any
                    packets that *may* have been digipeated due to the APRS-IS filtering.

                    > I do receive other packets normally with the HT in APRS mode either
                    > independently or in conjunction with APRSIS32 on the laptop.

                    Okay, that adds more mystery to the equation.

                    > I'm now going to kick up the XMITLVL on the KPC3+ to 150 and see if this
                    > will make a difference. Thanks for plugging away with me.

                    I would have ramped through the levels as a first step. Listen to the
                    audio level on your HT. Starting from zero, the audio level will
                    increase until it starts clipping. At that point the volume will no
                    longer increase. Turn the level down until it starts to get quieter,
                    and then turn it down some more.

                    Too much level is bad, too little is not as bad.

                    --
                    James
                    VE6SRV
                  • Scott McKee
                    Looks like have had some success!!...... now showing nt5sm*2 via 3 hops on the scroll. Will try the HT again tomorrow. May overload front end if too close.  
                    Message 9 of 18 , Oct 4, 2012
                    • 0 Attachment

                      Looks like have had some success!!...... now showing nt5sm*2 via 3 hops on the scroll. Will try the HT again tomorrow. May overload front end if too close.  

                      Thanks and 73,
                      Scott


                      From: James Ewen <ve6srv@...>
                      To: aprsisce@yahoogroups.com
                      Sent: Thursday, October 4, 2012 9:55 PM
                      Subject: Re: [aprsisce] Re: APRS Packets sent/received but not decoding

                       
                      On Thu, Oct 4, 2012 at 8:15 PM, Scott McKee <sbmckee@...> wrote:

                      > <So, can you explain how you are determining that you are not being
                      > digipeated? I'm not trying to be a pain, but some people base their
                      > observations on incomplete data.>
                      >
                      > I'm only making this assumption as I have not heard a packet back
                      > following my beacon as (nt5sm*2) from an area digi (nearest is 13 mi away).
                      > Is there another way to confirm this?

                      Listening to 144.390 and observing the packets being decoded is the
                      best way. Some people like to base their observations on the APRS-IS
                      stream, and in your case, being on the internet, you can not see any
                      packets that *may* have been digipeated due to the APRS-IS filtering.

                      > I do receive other packets normally with the HT in APRS mode either
                      > independently or in conjunction with APRSIS32 on the laptop.

                      Okay, that adds more mystery to the equation.

                      > I'm now going to kick up the XMITLVL on the KPC3+ to 150 and see if this
                      > will make a difference. Thanks for plugging away with me.

                      I would have ramped through the levels as a first step. Listen to the
                      audio level on your HT. Starting from zero, the audio level will
                      increase until it starts clipping. At that point the volume will no
                      longer increase. Turn the level down until it starts to get quieter,
                      and then turn it down some more.

                      Too much level is bad, too little is not as bad.

                      --
                      James
                      VE6SRV


                    • James Ewen
                      ... Can you help by clarifying what you re up to? NT5SM has been acting as an i-gate running APRSISCE/32. NT5SM-1 has also been acting as an i-gate running
                      Message 10 of 18 , Oct 4, 2012
                      • 0 Attachment
                        On Thu, Oct 4, 2012 at 8:15 PM, Scott McKee <sbmckee@...> wrote:

                        > Thanks for plugging away with me.

                        Can you help by clarifying what you're up to?

                        NT5SM has been acting as an i-gate running APRSISCE/32.

                        NT5SM-1 has also been acting as an i-gate running APRSISCE/32.

                        It looks like you might be flopping back and forth with the two.

                        Then there's NT5SM-14 as well...

                        Just want to make sure we're chasing the right right wild goose.

                        --
                        James
                        VE6SRV
                      • Scott McKee
                        Only tried the -1 briefly to see if not having an SSID might have been the issue with the HT. -14 was during initial testing only. Have found -0 nothing to
                        Message 11 of 18 , Oct 4, 2012
                        • 0 Attachment
                          Only tried the -1 briefly to see if not having an SSID might have been the issue with the HT. -14 was during initial testing only. Have found -0 "nothing" to be appropriate for i-gate only.

                          Scott, nt5sm


                          From: James Ewen <ve6srv@...>
                          To: aprsisce@yahoogroups.com
                          Sent: Thursday, October 4, 2012 10:17 PM
                          Subject: Re: [aprsisce] Re: APRS Packets sent/received but not decoding

                           
                          On Thu, Oct 4, 2012 at 8:15 PM, Scott McKee <sbmckee@...> wrote:

                          > Thanks for plugging away with me.

                          Can you help by clarifying what you're up to?

                          NT5SM has been acting as an i-gate running APRSISCE/32.

                          NT5SM-1 has also been acting as an i-gate running APRSISCE/32.

                          It looks like you might be flopping back and forth with the two.

                          Then there's NT5SM-14 as well...

                          Just want to make sure we're chasing the right right wild goose.

                          --
                          James
                          VE6SRV


                        • James Ewen
                          ... Yup, you ve been heard by a few RF stations now. The last packet I saw had KT5TK-15 passing your packet to W5RRR-1 and gated by N5ROG-1. You ve also been
                          Message 12 of 18 , Oct 4, 2012
                          • 0 Attachment
                            On Thu, Oct 4, 2012 at 9:06 PM, Scott McKee <sbmckee@...> wrote:

                            > Looks like have had some success!!...... now showing nt5sm*2 via 3 hops on
                            > the scroll. Will try the HT again tomorrow. May overload front end if too
                            > close.

                            Yup, you've been heard by a few RF stations now. The last packet I saw
                            had KT5TK-15 passing your packet to W5RRR-1 and gated by N5ROG-1.

                            You've also been heard by WR5AAA-1 and KT5TK-12 as well.

                            NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx I-GATE
                            NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx
                            I-GATE

                            --
                            James
                            VE6SRV
                          • Lynn W Deffenbaugh (Mr)
                            Here s the raw RF packets I ve captured sourced by NT5SM. Looks like it was working on the 1st and 2nd. Nothing heard on the 3rd, and just a couple of packets
                            Message 13 of 18 , Oct 4, 2012
                            • 0 Attachment
                              Here's the raw RF packets I've captured sourced by NT5SM. Looks like it
                              was working on the 1st and 2nd. Nothing heard on the 3rd, and just a
                              couple of packets just a bit ago. All times are Eastern time (UTC -0400).

                              Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

                              2012-10-01 21:19:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@011931h2936.75N/09543.59WI
                              2012-10-01 21:58:49 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                              2012-10-01 21:58:49 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                              2012-10-01 21:58:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                              2012-10-01 21:58:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                              2012-10-01 22:19:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@021931h2936.75N/09543.59WI
                              2012-10-01 22:49:35 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@024931h2936.75N/09543.59WIAPRS I-GATE
                              2012-10-01 22:53:32 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                              2012-10-01 22:53:32 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                              2012-10-01 22:53:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                              2012-10-01 22:53:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                              2012-10-01 22:59:34 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@025931h2936.75N/09543.59WI
                              2012-10-01 23:19:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@031931h2936.75N/09543.59WI
                              2012-10-01 23:19:33 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@031931h2936.75N/09543.59WI
                              2012-10-01 23:24:17 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                              2012-10-01 23:24:17 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                              2012-10-01 23:24:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                              2012-10-01 23:24:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                              2012-10-01 23:49:33 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@034931h2936.75N/09543.59WIAPRS I-GATE
                              2012-10-01 23:49:34 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@034931h2936.75N/09543.59WIAPRS I-GATE
                              2012-10-01 23:59:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@035931h2936.75N/09543.59WI
                              2012-10-02 22:50:52 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@025047h2936.66N/09543.63WIPHG3130 I-GATE
                              2012-10-02 22:58:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                              2012-10-02 22:58:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                              2012-10-02 22:58:57 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                              2012-10-02 22:58:57 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                              2012-10-02 23:02:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                              2012-10-02 23:02:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                              2012-10-02 23:15:21 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@031516h2936.66N/09543.63WxPHG3130 I-GATE
                              2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                              2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                              2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                              2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                              2012-10-02 23:31:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                              2012-10-02 23:31:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                              2012-10-04 22:54:43 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@025459h2936.69N/09543.61Wx
                              2012-10-04 22:59:56 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                              2012-10-04 22:59:56 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                              2012-10-04 23:03:42 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@030359h2936.69N/09543.61Wx
                              2012-10-04 23:03:42 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@030359h2936.69N/09543.61Wx



                              On 10/4/2012 11:35 PM, James Ewen wrote:
                              > On Thu, Oct 4, 2012 at 9:06 PM, Scott McKee <sbmckee@...> wrote:
                              >
                              >> Looks like have had some success!!...... now showing nt5sm*2 via 3 hops on
                              >> the scroll. Will try the HT again tomorrow. May overload front end if too
                              >> close.
                              > Yup, you've been heard by a few RF stations now. The last packet I saw
                              > had KT5TK-15 passing your packet to W5RRR-1 and gated by N5ROG-1.
                              >
                              > You've also been heard by WR5AAA-1 and KT5TK-12 as well.
                              >
                              > NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx I-GATE
                              > NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx
                              > I-GATE
                              >
                              > --
                              > James
                              > VE6SRV
                              >
                              >
                              > ------------------------------------
                              >
                              > Yahoo! Groups Links
                              >
                              >
                              >
                              >
                            • Scott McKee
                              That looks good here....KT5TK-12 is the nearest digi but he has no I-gate.  The SW of Houston lacks in coverage so trying to fill a hole.  Only rooftop Ringo
                              Message 14 of 18 , Oct 4, 2012
                              • 0 Attachment
                                That looks good here....KT5TK-12 is the nearest digi but he has no I-gate.  The SW of Houston lacks in coverage so trying to fill a hole.  Only rooftop Ringo antenna but it will help in our flat terrain here.  Thanks to all for your guidance.. 73, Scott


                                From: Lynn W Deffenbaugh (Mr) <kj4erj@...>
                                To: aprsisce@yahoogroups.com
                                Sent: Thursday, October 4, 2012 10:51 PM
                                Subject: Re: [aprsisce] APRS Packets sent/received but not decoding - some success !

                                 
                                Here's the raw RF packets I've captured sourced by NT5SM. Looks like it
                                was working on the 1st and 2nd. Nothing heard on the 3rd, and just a
                                couple of packets just a bit ago. All times are Eastern time (UTC -0400).

                                Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

                                2012-10-01 21:19:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@011931h2936.75N/09543.59WI
                                2012-10-01 21:58:49 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                                2012-10-01 21:58:49 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                                2012-10-01 21:58:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                                2012-10-01 21:58:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 01:53 2956.95N 09616.90W
                                2012-10-01 22:19:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@021931h2936.75N/09543.59WI
                                2012-10-01 22:49:35 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@024931h2936.75N/09543.59WIAPRS I-GATE
                                2012-10-01 22:53:32 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                                2012-10-01 22:53:32 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                                2012-10-01 22:53:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                                2012-10-01 22:53:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/IDX: WR5AAA-1 40.6mi 305° 02:53 2956.95N 09616.90W
                                2012-10-01 22:59:34 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@025931h2936.75N/09543.59WI
                                2012-10-01 23:19:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@031931h2936.75N/09543.59WI
                                2012-10-01 23:19:33 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@031931h2936.75N/09543.59WI
                                2012-10-01 23:24:17 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                                2012-10-01 23:24:17 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                                2012-10-01 23:24:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                                2012-10-01 23:24:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>020324zDX: WR5AAA-1 40.6mi 305° 03:23 2956.95N 09616.90W
                                2012-10-01 23:49:33 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@034931h2936.75N/09543.59WIAPRS I-GATE
                                2012-10-01 23:49:34 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@034931h2936.75N/09543.59WIAPRS I-GATE
                                2012-10-01 23:59:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@035931h2936.75N/09543.59WI
                                2012-10-02 22:50:52 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@025047h2936.66N/09543.63WIPHG3130 I-GATE
                                2012-10-02 22:58:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                                2012-10-02 22:58:33 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                                2012-10-02 22:58:57 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                                2012-10-02 22:58:57 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                                2012-10-02 23:02:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                                2012-10-02 23:02:18 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1::NT5SM-9 :test again{HC}
                                2012-10-02 23:15:21 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@031516h2936.66N/09543.63WxPHG3130 I-GATE
                                2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                2012-10-02 23:16:53 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                2012-10-02 23:31:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                2012-10-02 23:31:50 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                2012-10-04 22:54:43 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@025459h2936.69N/09543.61Wx
                                2012-10-04 22:59:56 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                2012-10-04 22:59:56 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                2012-10-04 23:03:42 NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@030359h2936.69N/09543.61Wx
                                2012-10-04 23:03:42 NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@030359h2936.69N/09543.61Wx

                                On 10/4/2012 11:35 PM, James Ewen wrote:
                                > On Thu, Oct 4, 2012 at 9:06 PM, Scott McKee <sbmckee@...> wrote:
                                >
                                >> Looks like have had some success!!...... now showing nt5sm*2 via 3 hops on
                                >> the scroll. Will try the HT again tomorrow. May overload front end if too
                                >> close.
                                > Yup, you've been heard by a few RF stations now. The last packet I saw
                                > had KT5TK-15 passing your packet to W5RRR-1 and gated by N5ROG-1.
                                >
                                > You've also been heard by WR5AAA-1 and KT5TK-12 as well.
                                >
                                > NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx I-GATE
                                > NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx
                                > I-GATE
                                >
                                > --
                                > James
                                > VE6SRV
                                >
                                >
                                > ------------------------------------
                                >
                                > Yahoo! Groups Links
                                >
                                >
                                >
                                >



                              • James Ewen
                                Scott, You re getting heard by the local RF network for sure... NT5SM APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx I-GATE
                                Message 15 of 18 , Oct 5, 2012
                                • 0 Attachment
                                  Scott,

                                  You're getting heard by the local RF network for sure...


                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033726h2936.69N/09543.61Wx
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033726h2936.69N/09543.61Wx
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@033726h2936.69N/09543.61Wx
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050343z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050353z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@040126h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA5GIL-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,WD5IYT:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,K5KRK*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,NT5SM:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WB5LJZ-5*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WB5LJZ-5*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,NT5SM:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@120224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:@120224h2936.69N/09543.61Wx  I-GATE
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA5GIL-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA5GIL-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,NT5SM:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051503z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*051503z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                  NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051533z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org


                                  You might want to look at modifying the repeater object that you are sending out. First off, drop the multiple hop outgoing path... The object should go out to an area equal to what you should be able to hear it over. It is best practice to have a local digipeater send the object as it has a better chance of not causing collisions than a home station does. Sending from a home station and then through a digipeater uses twice the amount of airtime than from a digipeater. 

                                  You also might want to format the voice repeater object to match the voice repeater specification so that the full information is available and tunable on the QSY capable radios. It is still fully humanly readable, and able to be understood by the radios as well.

                                  We've moved from trying to get the thing to work into the realm of making it work optimally now...

                                  James
                                  VE6SRV
                                • Scott Mckee
                                  Looks good ... Tried the HT out on a walk and still no beacon from home being displayed. http://aprs.fi/#!call=a%2FNT5SM-9&timerange=3600 I will try to
                                  Message 16 of 18 , Oct 5, 2012
                                  • 0 Attachment
                                    Looks good ... Tried the HT out on a walk and still no beacon  from home being displayed.    http://aprs.fi/#!call=a%2FNT5SM-9&timerange=3600  I will try to send a message from home and see if I get it direct or via KT5TK. BTW, what site are you going to see my RF packets?8
                                    73,
                                    Scott nt5sm.





                                    On Oct 5, 2012, at 10:47, James Ewen <ve6srv@...> wrote:

                                     

                                    Scott,

                                    You're getting heard by the local RF network for sure...


                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033726h2936.69N/09543.61Wx
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033726h2936.69N/09543.61Wx
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@033726h2936.69N/09543.61Wx
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050343z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050353z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@040126h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA5GIL-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,WD5IYT:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,K5KRK*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,NT5SM:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WB5LJZ-5*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WB5LJZ-5*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,NT5SM:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@120224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:@120224h2936.69N/09543.61Wx  I-GATE
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA5GIL-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA5GIL-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,NT5SM:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051503z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*051503z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                    NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051533z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org


                                    You might want to look at modifying the repeater object that you are sending out. First off, drop the multiple hop outgoing path... The object should go out to an area equal to what you should be able to hear it over. It is best practice to have a local digipeater send the object as it has a better chance of not causing collisions than a home station does. Sending from a home station and then through a digipeater uses twice the amount of airtime than from a digipeater. 

                                    You also might want to format the voice repeater object to match the voice repeater specification so that the full information is available and tunable on the QSY capable radios. It is still fully humanly readable, and able to be understood by the radios as well.

                                    We've moved from trying to get the thing to work into the realm of making it work optimally now...

                                    James
                                    VE6SRV

                                  • Lynn W Deffenbaugh (Mr)
                                    RF-enabled instances of APRSISCE/32 send a non-dupe-suppressed packet back to my server so that I can provide displays like: http://tinyurl.com/IGATE-NT5SM
                                    Message 17 of 18 , Oct 5, 2012
                                    • 0 Attachment
                                      RF-enabled instances of APRSISCE/32 send a non-dupe-suppressed packet back to my server so that I can provide displays like:

                                      http://tinyurl.com/IGATE-NT5SM

                                      http://tinyurl.com/8pu9qx3

                                      At least until I get these features implemented directly in the local client.

                                      The packet logs below were extracted from my central logging.  I'm hoping to come up with a way to allow IGates to send this information directly to "interested" parties on an approved basis, but I haven't yet overcome the complexities of getting the packets through Internet routers and gateways and really don't want to open up that support can-of-worms.  ("Why can't I see XYZ's RF packets?  Did you open a port on your router to let the packets come in?  What's a router...).

                                      Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

                                      On 10/5/2012 2:36 PM, Scott Mckee wrote:
                                      Looks good ... Tried the HT out on a walk and still no beacon  from home being displayed.    http://aprs.fi/#!call=a%2FNT5SM-9&timerange=3600  I will try to send a message from home and see if I get it direct or via KT5TK. BTW, what site are you going to see my RF packets?8
                                      73,
                                      Scott nt5sm.





                                      On Oct 5, 2012, at 10:47, James Ewen <ve6srv@...> wrote:

                                       
                                      Scott,

                                      You're getting heard by the local RF network for sure...


                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033141h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@033726h2936.69N/09543.61Wx
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@033726h2936.69N/09543.61Wx
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@033726h2936.69N/09543.61Wx
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050343z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050353z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@040126h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050643z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA5GIL-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,WD5IYT:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,K5KRK*,WIDE2*,qAR,N5ROG-1:@073224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,NT5SM:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,NT5SM:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*050803z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WB5LJZ-5*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050903z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WB5LJZ-5*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*050933z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,NT5SM:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:@120224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,WD5CFJ-10*,KT5TK-12*,qAR,NT5SM:@120224h2936.69N/09543.61Wx  I-GATE
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA5GIL-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA5GIL-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,NT5SM:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,NU5P-11*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*051303z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,WIDE2-1,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:>EL29do/x
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,WD5IYT:;6.94-RPTR*051503z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,AI5TX-7*,WIDE2*,qAR,KA1MZY-1:;6.94-RPTR*051503z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org
                                      NT5SM>APWW10,KT5TK-15*,W5RRR-1*,WIDE2*,qAR,N5ROG-1:;6.94-RPTR*051533z2933.93N/09531.09Wr146.940MHz T:167 -060  info: www.bvarc.org


                                      You might want to look at modifying the repeater object that you are sending out. First off, drop the multiple hop outgoing path... The object should go out to an area equal to what you should be able to hear it over. It is best practice to have a local digipeater send the object as it has a better chance of not causing collisions than a home station does. Sending from a home station and then through a digipeater uses twice the amount of airtime than from a digipeater. 

                                      You also might want to format the voice repeater object to match the voice repeater specification so that the full information is available and tunable on the QSY capable radios. It is still fully humanly readable, and able to be understood by the radios as well.

                                      We've moved from trying to get the thing to work into the realm of making it work optimally now...

                                      James
                                      VE6SRV

                                    Your message has been successfully submitted and would be delivered to recipients shortly.