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

New OT3m

Expand Messages
  • kc2yu
    Having some difficulty with my brand new OT3m. I ve got it hooked up to an FT-8800 and to the computer via UBS. Got otwincfg running and was able to configure
    Message 1 of 9 , Aug 31, 2012
    • 0 Attachment
      Having some difficulty with my brand new OT3m.

      I've got it hooked up to an FT-8800 and to the computer via UBS.

      Got otwincfg running and was able to configure the ot3m (and write settings).

      I can make use otwincfg to transmit (test the PTT button in the program).

      Downloaded aprsis32 and did a very brief config (mycall, location, etc.).

      But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32 map or packet log.

      It appears aprsis32 isn't communicating with the ot3m.

      I found a web page that says I need to put the following command in aprsis32.xml -- http://www.kj4iwx.com/?p=52

      but that isn't working.

      Any ideas?

      Thank you,

      Joseph, kc2yu
    • kc2yu
      Update: I believe aprsis32 and the ot3m are now talking. Here s a snippet from the trace-port log: Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading
      Message 2 of 9 , Aug 31, 2012
      • 0 Attachment
        Update:

        I believe aprsis32 and the ot3m are now talking.

        Here's a snippet from the trace-port log:

        Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D 0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
        Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D 0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
        Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D 0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
        Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D 0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W

        So, packets are getting from the radio to aprsis32, but I'm not seeing them on my map or list of names. Sounds like this is an aprsis32 question, so sorry for msg traffic here. I'll move it over.



        --- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@...> wrote:
        >
        >
        > Having some difficulty with my brand new OT3m.
        >
        > I've got it hooked up to an FT-8800 and to the computer via UBS.
        >
        > Got otwincfg running and was able to configure the ot3m (and write settings).
        >
        > I can make use otwincfg to transmit (test the PTT button in the program).
        >
        > Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
        >
        > But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32 map or packet log.
        >
        > It appears aprsis32 isn't communicating with the ot3m.
        >
        > I found a web page that says I need to put the following command in aprsis32.xml -- http://www.kj4iwx.com/?p=52
        >
        > but that isn't working.
        >
        > Any ideas?
        >
        > Thank you,
        >
        > Joseph, kc2yu
        >
      • Lynn W. Deffenbaugh (Mr)
        Based on the Missing Leading C0 , your tracker port isn t in KISS mode. You ll want to use the appropriate AMODE/BMODE/USBKISS to put it there and make sure
        Message 3 of 9 , Aug 31, 2012
        • 0 Attachment
          Based on the "Missing Leading C0", your tracker port isn't in KISS
          mode. You'll want to use the appropriate AMODE/BMODE/USBKISS to put it
          there and make sure your port in APRSISCE/32 is a Simply(KISS) or edit
          the XML file and set the <Open/CloseCmd>s to no-ops as described at
          http://aprsisce.wikidot.com/tt4-via-kiss (yes, I know that's for the
          TT4, but it describes how to set up the No-Operation <Open/CloseCmd>s).

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

          On 8/31/2012 11:03 AM, kc2yu wrote:
          > Update:
          >
          > I believe aprsis32 and the ot3m are now talking.
          >
          > Here's a snippet from the trace-port log:
          >
          > Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D 0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
          > Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D 0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
          > Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D 0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
          > Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D 0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
          >
          > So, packets are getting from the radio to aprsis32, but I'm not seeing them on my map or list of names. Sounds like this is an aprsis32 question, so sorry for msg traffic here. I'll move it over.
          >
          >
          >
          > --- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@...> wrote:
          >>
          >> Having some difficulty with my brand new OT3m.
          >>
          >> I've got it hooked up to an FT-8800 and to the computer via UBS.
          >>
          >> Got otwincfg running and was able to configure the ot3m (and write settings).
          >>
          >> I can make use otwincfg to transmit (test the PTT button in the program).
          >>
          >> Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
          >>
          >> But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32 map or packet log.
          >>
          >> It appears aprsis32 isn't communicating with the ot3m.
          >>
          >> I found a web page that says I need to put the following command in aprsis32.xml -- http://www.kj4iwx.com/?p=52
          >>
          >> but that isn't working.
          >>
          >> Any ideas?
          >>
          >> Thank you,
          >>
          >> Joseph, kc2yu
          >>
          >
          >
          >
          > ------------------------------------
          >
          > Yahoo! Groups Links
          >
          >
          >
          >
        • Fred Hillhouse
          They are talking but not correctly. Put the OT3 in KISS using OT config software and create a port using SimplyKISS in APRSIS32. That should work. Best
          Message 4 of 9 , Aug 31, 2012
          • 0 Attachment
            They are talking but not correctly.
             
            Put the OT3 in KISS using OT config software and create a port using SimplyKISS in APRSIS32. That should work.
             
            Best regards,
            fred, N7FMH
             
             


            From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of kc2yu
            Sent: Friday, August 31, 2012 11:03
            To: tracker2@yahoogroups.com
            Subject: [tracker2] Re: New OT3m

             


            Update:

            I believe aprsis32 and the ot3m are now talking.

            Here's a snippet from the trace-port log:

            Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D 0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
            Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D 0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
            Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D 0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
            Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D 0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W

            So, packets are getting from the radio to aprsis32, but I'm not seeing them on my map or list of names. Sounds like this is an aprsis32 question, so sorry for msg traffic here. I'll move it over.

            --- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@...> wrote:
            >
            >
            > Having some difficulty with my brand new OT3m.
            >
            > I've got it hooked up to an FT-8800 and to the computer via UBS.
            >
            > Got otwincfg running and was able to configure the ot3m (and write settings).
            >
            > I can make use otwincfg to transmit (test the PTT button in the program).
            >
            > Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
            >
            > But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32 map or packet log.
            >
            > It appears aprsis32 isn't communicating with the ot3m.
            >
            > I found a web page that says I need to put the following command in aprsis32.xml -- http://www.kj4iwx.com/?p=52
            >
            > but that isn't working.
            >
            > Any ideas?
            >
            > Thank you,
            >
            > Joseph, kc2yu
            >

          • kc2yu
            That did it, thought I m not sure what exactly it did. The ot was in AUTO mode for the serial ports. I switched them to KISS. Then restarted aprsis32 and it
            Message 5 of 9 , Aug 31, 2012
            • 0 Attachment
              That did it, thought I'm not sure what exactly it did.

              The ot was in AUTO mode for the serial ports. I switched them to KISS.

              Then restarted aprsis32 and it worked.

              Shut down aprsis32 and restarted it and it didn't.

              Checked otwincfg and the serial ports were back to AUTO -- despite having written the config the first time.

              Edited aprsis32.xml and replace the opencmd & closecmd lines with:

              <OpenCmd>~!!0</OpenCmd>
              <CloseCmd>~!!0</CloseCmd>

              Seems like that did it (not 100% certain).

              Thanks very much!

              And, it sure looks like the OT continues to digi on its own while still in KISS mode connected to aprsis32 -- very cool.

              What I'd like to do now is find a way to see who is hearing my signals direct. I very well may need to turn down the power, or adjust in some other way.





              --- In tracker2@yahoogroups.com, "Lynn W. Deffenbaugh (Mr)" <ldeffenb@...> wrote:
              >
              > Based on the "Missing Leading C0", your tracker port isn't in KISS
              > mode. You'll want to use the appropriate AMODE/BMODE/USBKISS to put it
              > there and make sure your port in APRSISCE/32 is a Simply(KISS) or edit
              > the XML file and set the <Open/CloseCmd>s to no-ops as described at
              > http://aprsisce.wikidot.com/tt4-via-kiss (yes, I know that's for the
              > TT4, but it describes how to set up the No-Operation <Open/CloseCmd>s).
              >
              > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
              >
              > On 8/31/2012 11:03 AM, kc2yu wrote:
              > > Update:
              > >
              > > I believe aprsis32 and the ot3m are now talking.
              > >
              > > Here's a snippet from the trace-port log:
              > >
              > > Port(test):2012-08-31T15:00:27.705 KISS:Missing Leading C0[165]:<0D 0A>WB2ZEX>APW285,N2MH-15*,WA2MJM-15*:_08311456c290s006g002t094r493p493P000h00b10138wHKT<0D 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
              > > Port(test):2012-08-31T15:00:33.529 KISS:Missing Leading C0[152]:<0D 0A>W2LV>APN391,WIDE2-1:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
              > > Port(test):2012-08-31T15:00:36.529 KISS:Missing Leading C0[155]:<0D 0A>W2LV>APN391,WA2MJM-15*:!!0013002002DB0623266602FF024C----00F3026100000000<0D 0A 0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
              > > Port(test):2012-08-31T15:00:38.146 KISS:Missing Leading C0[154]:<0D 0A>N1LMA-9>APNX01,SALECT*,KB1AEV-15*,WIDE2:!4120.95NS07157.74W#PHG5130/CRSnet<0D 0A>cmd:b`@145645hIS for Wb`@145745hIS for Wb`@145751hIS for Wb`@145833hIS for W
              > >
              > > So, packets are getting from the radio to aprsis32, but I'm not seeing them on my map or list of names. Sounds like this is an aprsis32 question, so sorry for msg traffic here. I'll move it over.
              > >
              > >
              > >
              > > --- In tracker2@yahoogroups.com, "kc2yu" <jrskoler@> wrote:
              > >>
              > >> Having some difficulty with my brand new OT3m.
              > >>
              > >> I've got it hooked up to an FT-8800 and to the computer via UBS.
              > >>
              > >> Got otwincfg running and was able to configure the ot3m (and write settings).
              > >>
              > >> I can make use otwincfg to transmit (test the PTT button in the program).
              > >>
              > >> Downloaded aprsis32 and did a very brief config (mycall, location, etc.).
              > >>
              > >> But, while I hear lots of traffic on 144.39, nothing shows up on the aprsis32 map or packet log.
              > >>
              > >> It appears aprsis32 isn't communicating with the ot3m.
              > >>
              > >> I found a web page that says I need to put the following command in aprsis32.xml -- http://www.kj4iwx.com/?p=52
              > >>
              > >> but that isn't working.
              > >>
              > >> Any ideas?
              > >>
              > >> Thank you,
              > >>
              > >> Joseph, kc2yu
              > >>
              > >
              > >
              > >
              > > ------------------------------------
              > >
              > > Yahoo! Groups Links
              > >
              > >
              > >
              > >
              >
            • Bob Burns W9RXR
              ... Yes, that is a feature of the Tracker2 and Tracker3 lines that comes up in conversation here from time to time. It s a useful feature, but you have to be
              Message 6 of 9 , Aug 31, 2012
              • 0 Attachment
                At 12:33 PM 8/31/2012, kc2yu wrote:

                >And, it sure looks like the OT continues to digi on its own while
                >still in KISS mode connected to aprsis32 -- very cool.

                Yes, that is a feature of the Tracker2 and Tracker3 lines that comes
                up in conversation here from time to time. It's a useful feature, but
                you have to be careful with it as you don't want both the TNC and the
                client program doing the same thing whether it be beaconing or
                digipeating. For instance, if your client program is handling the
                beaconing, make sure the TNC isn't beaconing, too.

                If you take a look at the Tracker2 set up instructions for UI-View
                (http://wiki.argentdata.com/index.php?title=UI-View_Setup), you will
                see that UI-View's "Into KISS" strings are commanding the Tracker2 to
                _not_ beacon before it actually tells the Tracker2 to go into KISS mode.

                Bob...
              • kc2yu
                It seems like a very nice feature. With features come power and complications. I don t believe the APRSISCE/32 instance is digipeating, but I should check the
                Message 7 of 9 , Aug 31, 2012
                • 0 Attachment
                  It seems like a very nice feature.

                  With features come power and complications.

                  I don't believe the APRSISCE/32 instance is digipeating, but I should check the beaconing. I have the ot3m digi as kc2yu-2, while the ASRSISCE/32 as kc2yu-3 -- just assuming it'd be easier to distinguish what is generating what and there cause a problem doing so.

                  Thanks for the explanation!

                  --- In tracker2@yahoogroups.com, Bob Burns W9RXR <w9rxr_@...> wrote:
                  >
                  > At 12:33 PM 8/31/2012, kc2yu wrote:
                  >
                  > >And, it sure looks like the OT continues to digi on its own while
                  > >still in KISS mode connected to aprsis32 -- very cool.
                  >
                  > Yes, that is a feature of the Tracker2 and Tracker3 lines that comes
                  > up in conversation here from time to time. It's a useful feature, but
                  > you have to be careful with it as you don't want both the TNC and the
                  > client program doing the same thing whether it be beaconing or
                  > digipeating. For instance, if your client program is handling the
                  > beaconing, make sure the TNC isn't beaconing, too.
                  >
                  > If you take a look at the Tracker2 set up instructions for UI-View
                  > (http://wiki.argentdata.com/index.php?title=UI-View_Setup), you will
                  > see that UI-View's "Into KISS" strings are commanding the Tracker2 to
                  > _not_ beacon before it actually tells the Tracker2 to go into KISS mode.
                  >
                  > Bob...
                  >
                • James Ewen
                  ... Look at your map, and use Screen|Paths to enable showing the paths between stations. You ll be able to see who you can hear direct. You can contact the
                  Message 8 of 9 , Aug 31, 2012
                  • 0 Attachment
                    On Fri, Aug 31, 2012 at 10:33 AM, kc2yu <jrskoler@...> wrote:

                    > What I'd like to do now is find a way to see who is hearing my signals direct.

                    Look at your map, and use Screen|Paths to enable showing the paths
                    between stations. You'll be able to see who you can hear direct. You
                    can contact the operators of those stations and ask them if they can
                    see you. Digipeaters will digipeat your packets so you can see if they
                    hear you when they send your packets back at you. i-gates pushing your
                    data to the internet can be observed via the internet, but you might
                    not see all of the i-gates that can hear you due to the duplicate
                    filtering issues.

                    --
                    James
                    VE6SRV
                  • kc2yu
                    Got it -- thanks. Been playing with APRSISCE/32 and it s incredibly powerful. Still learning....
                    Message 9 of 9 , Sep 1, 2012
                    • 0 Attachment
                      Got it -- thanks.

                      Been playing with APRSISCE/32 and it's incredibly powerful.

                      Still learning....

                      --- In tracker2@yahoogroups.com, James Ewen <ve6srv@...> wrote:
                      >
                      > On Fri, Aug 31, 2012 at 10:33 AM, kc2yu <jrskoler@...> wrote:
                      >
                      > > What I'd like to do now is find a way to see who is hearing my signals direct.
                      >
                      > Look at your map, and use Screen|Paths to enable showing the paths
                      > between stations. You'll be able to see who you can hear direct. You
                      > can contact the operators of those stations and ask them if they can
                      > see you. Digipeaters will digipeat your packets so you can see if they
                      > hear you when they send your packets back at you. i-gates pushing your
                      > data to the internet can be observed via the internet, but you might
                      > not see all of the i-gates that can hear you due to the duplicate
                      > filtering issues.
                      >
                      > --
                      > James
                      > VE6SRV
                      >
                    Your message has been successfully submitted and would be delivered to recipients shortly.