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

Firmware build 54030

Expand Messages
  • scott@opentrac.org
    Ok, new firmware is up. Peet Bros Ultimeter 2000 series weather stations (2000, 2100, 800, 100, etc) are now supported. There s nothing to configure on the
    Message 1 of 21 , Oct 22, 2006
    • 0 Attachment
      Ok, new firmware is up. Peet Bros Ultimeter 2000 series weather stations
      (2000, 2100, 800, 100, etc) are now supported. There's nothing to configure
      on the tracker side if you've got AUTOBAUD on - just set your weather
      station to complete record mode, and plug it in to either port on the
      tracker.

      Right now it'll send both a position packet AND a weather packet (which
      includes position) when it's ready to transmit. I've got to figure out how
      I want to restrict which packets get sent when.

      Scott
    • k0yg
      Hi Scott, I loaded up the new build and connected my Peet Ultimeter 2000. I have the Ultimter connected to port 2 and the computer to port 1. I set the baud
      Message 2 of 21 , Oct 23, 2006
      • 0 Attachment
        Hi Scott,

        I loaded up the new build and connected my Peet Ultimeter 2000. I
        have the Ultimter connected to port 2 and the computer to port 1. I
        set the baud rate manually on port 2 to 2400. Here are my initial
        observations:

        1. The new "WXINFO" command seems to report bad data along with good
        data every once in a while. Here is a sample of what I get when I
        type WXINFO as fast as I can type:

        TEMP:-1226 WIND 139 AT 1794 GUST 1281 BARO -20478
        TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
        TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
        TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
        TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
        TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
        TEMP:1644 WIND 11 AT 0 GUST 1 BARO 638
        TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
        TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
        TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
        TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
        TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
        TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
        TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
        TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
        TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
        TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
        TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
        TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
        TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
        TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192

        Seems like this command should also report humidity. (I don't have a
        himidity sensor attached so maybe this is why)

        2. The T2 reports the humidity as "h00" but findu reports this as
        100%.

        3. When I set the transmit rate to every 2 minutes, the data being
        transmitted was correct once in a while and incorrect most of the
        time. For instance it reported humidity between 12% and 51% and
        sometimes zero. Here is a sample of the bad packets (part up to WX
        data has been truncated)

        _180/006g010t048P000h12b10211OU2k (humidity wrong)
        _180/000g000t053P000b10202OU2k (no humidity)
        _180/000g000t053P000b10202OU2k (no humidity)
        _000/063g014t085P141h12b00731OU2k (everything is wrong)
        _180/000g003t055P000h51b10201OU2k (humidity wrong)
        _180/000g003t055P000h51b10201OU2k (humidity wrong)

        When I changed the transmit rate to every 4 minutes this problem
        seemed to happen less often with only the humidity being wrong
        sometimes.

        4. Which combination of commands trigger the WX string to be
        transmitted? It seems like status needs to be something other than
        zero along with interval? Which one controls how often the strin is
        sent?

        I'll do more longer term testing along with the autobaud and let you
        know how that goes.

        Mark


        --- In tracker2@yahoogroups.com, <scott@...> wrote:
        >
        > Ok, new firmware is up. Peet Bros Ultimeter 2000 series weather
        stations
        > (2000, 2100, 800, 100, etc) are now supported. There's nothing to
        configure
        > on the tracker side if you've got AUTOBAUD on - just set your
        weather
        > station to complete record mode, and plug it in to either port on
        the
        > tracker.
        >
        > Right now it'll send both a position packet AND a weather packet
        (which
        > includes position) when it's ready to transmit. I've got to figure
        out how
        > I want to restrict which packets get sent when.
        >
        > Scott
        >
      • scott@opentrac.org
        I didn t mention the WXINFO command because it s still flawed - it reports whatever is in memory at the moment, which might be invalid if it s in the middle of
        Message 3 of 21 , Oct 23, 2006
        • 0 Attachment
          I didn't mention the WXINFO command because it's still flawed - it reports whatever is in memory at the moment, which might be invalid if it's in the middle of parsing a string.
           
          Were you using a GPS receiver or fixed position mode?
           
          Right now, timing is dependent on the INTERVAL setting.  It'll transmit a weather packet whenever it transmits a position packet, assuming the weather data is valid.
           
          Scott


          From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of k0yg
          Sent: Monday, October 23, 2006 1:00 PM
          To: tracker2@yahoogroups.com
          Subject: [tracker2] Re: Firmware build 54030

          Hi Scott,

          I loaded up the new build and connected my Peet Ultimeter 2000. I
          have the Ultimter connected to port 2 and the computer to port 1. I
          set the baud rate manually on port 2 to 2400. Here are my initial
          observations:

          1. The new "WXINFO" command seems to report bad data along with good
          data every once in a while. Here is a sample of what I get when I
          type WXINFO as fast as I can type:

          TEMP:-1226 WIND 139 AT 1794 GUST 1281 BARO -20478
          TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
          TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
          TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
          TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
          TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
          TEMP:1644 WIND 11 AT 0 GUST 1 BARO 638
          TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
          TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
          TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
          TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
          TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
          TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
          TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
          TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
          TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
          TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
          TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
          TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
          TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
          TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192

          Seems like this command should also report humidity. (I don't have a
          himidity sensor attached so maybe this is why)

          2. The T2 reports the humidity as "h00" but findu reports this as
          100%.

          3. When I set the transmit rate to every 2 minutes, the data being
          transmitted was correct once in a while and incorrect most of the
          time. For instance it reported humidity between 12% and 51% and
          sometimes zero. Here is a sample of the bad packets (part up to WX
          data has been truncated)

          _180/006g010t048P00 0h12b10211OU2k (humidity wrong)
          _180/000g000t053P00 0b10202OU2k (no humidity)
          _180/000g000t053P00 0b10202OU2k (no humidity)
          _000/063g014t085P14 1h12b00731OU2k (everything is wrong)
          _180/000g003t055P00 0h51b10201OU2k (humidity wrong)
          _180/000g003t055P00 0h51b10201OU2k (humidity wrong)

          When I changed the transmit rate to every 4 minutes this problem
          seemed to happen less often with only the humidity being wrong
          sometimes.

          4. Which combination of commands trigger the WX string to be
          transmitted? It seems like status needs to be something other than
          zero along with interval? Which one controls how often the strin is
          sent?

          I'll do more longer term testing along with the autobaud and let you
          know how that goes.

          Mark

          --- In tracker2@yahoogroup s.com, <scott@...> wrote:
          >
          > Ok, new firmware is up. Peet Bros Ultimeter 2000 series weather
          stations
          > (2000, 2100, 800, 100, etc) are now supported. There's nothing to
          configure
          > on the tracker side if you've got AUTOBAUD on - just set your
          weather
          > station to complete record mode, and plug it in to either port on
          the
          > tracker.
          >
          > Right now it'll send both a position packet AND a weather packet
          (which
          > includes position) when it's ready to transmit. I've got to figure
          out how
          > I want to restrict which packets get sent when.
          >
          > Scott
          >

        • Mark Miller
          Scott, It looks like you have taken care of the RX lockup when using KISS. With this build and Xastir, I have not had any problems. 73, Mark N5RFX
          Message 4 of 21 , Oct 23, 2006
          • 0 Attachment
            Scott,

            It looks like you have taken care of the RX lockup when using
            KISS. With this build and Xastir, I have not had any problems.

            73,

            Mark N5RFX
          • Mark Miller
            Will the Dallas 1-wire weather station work with this build? 73, Mark N5RFX
            Message 5 of 21 , Oct 23, 2006
            • 0 Attachment
              Will the Dallas 1-wire weather station work with this build?

              73,

              Mark N5RFX
            • scott@opentrac.org
              Nope. That s next. Scott _____ From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Mark Miller Sent: Monday, October 23, 2006 2:29
              Message 6 of 21 , Oct 23, 2006
              • 0 Attachment
                Nope.  That's next.
                 
                Scott


                From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Mark Miller
                Sent: Monday, October 23, 2006 2:29 PM
                To: tracker2@yahoogroups.com
                Subject: RE: [tracker2] Re: Firmware build 54030

                Will the Dallas 1-wire weather station work with this build?

                73,

                Mark N5RFX

              • k0yg
                I m in fixed position mode. Mark ... reports ... in the ... transmit a ... the weather ... Behalf ... good ... a ... you ... s.com, ... figure
                Message 7 of 21 , Oct 23, 2006
                • 0 Attachment
                  I'm in fixed position mode.

                  Mark


                  --- In tracker2@yahoogroups.com, <scott@...> wrote:
                  >
                  > I didn't mention the WXINFO command because it's still flawed - it
                  reports
                  > whatever is in memory at the moment, which might be invalid if it's
                  in the
                  > middle of parsing a string.
                  >
                  > Were you using a GPS receiver or fixed position mode?
                  >
                  > Right now, timing is dependent on the INTERVAL setting. It'll
                  transmit a
                  > weather packet whenever it transmits a position packet, assuming
                  the weather
                  > data is valid.
                  >
                  > Scott
                  >
                  >
                  > _____
                  >
                  > From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On
                  Behalf
                  > Of k0yg
                  > Sent: Monday, October 23, 2006 1:00 PM
                  > To: tracker2@yahoogroups.com
                  > Subject: [tracker2] Re: Firmware build 54030
                  >
                  >
                  >
                  > Hi Scott,
                  >
                  > I loaded up the new build and connected my Peet Ultimeter 2000. I
                  > have the Ultimter connected to port 2 and the computer to port 1. I
                  > set the baud rate manually on port 2 to 2400. Here are my initial
                  > observations:
                  >
                  > 1. The new "WXINFO" command seems to report bad data along with
                  good
                  > data every once in a while. Here is a sample of what I get when I
                  > type WXINFO as fast as I can type:
                  >
                  > TEMP:-1226 WIND 139 AT 1794 GUST 1281 BARO -20478
                  > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                  > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                  > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                  > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                  > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                  > TEMP:1644 WIND 11 AT 0 GUST 1 BARO 638
                  > TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
                  > TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
                  > TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
                  > TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
                  > TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
                  > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                  > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                  > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                  > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                  > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                  > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                  > TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
                  > TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
                  > TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
                  >
                  > Seems like this command should also report humidity. (I don't have
                  a
                  > himidity sensor attached so maybe this is why)
                  >
                  > 2. The T2 reports the humidity as "h00" but findu reports this as
                  > 100%.
                  >
                  > 3. When I set the transmit rate to every 2 minutes, the data being
                  > transmitted was correct once in a while and incorrect most of the
                  > time. For instance it reported humidity between 12% and 51% and
                  > sometimes zero. Here is a sample of the bad packets (part up to WX
                  > data has been truncated)
                  >
                  > _180/006g010t048P000h12b10211OU2k (humidity wrong)
                  > _180/000g000t053P000b10202OU2k (no humidity)
                  > _180/000g000t053P000b10202OU2k (no humidity)
                  > _000/063g014t085P141h12b00731OU2k (everything is wrong)
                  > _180/000g003t055P000h51b10201OU2k (humidity wrong)
                  > _180/000g003t055P000h51b10201OU2k (humidity wrong)
                  >
                  > When I changed the transmit rate to every 4 minutes this problem
                  > seemed to happen less often with only the humidity being wrong
                  > sometimes.
                  >
                  > 4. Which combination of commands trigger the WX string to be
                  > transmitted? It seems like status needs to be something other than
                  > zero along with interval? Which one controls how often the strin is
                  > sent?
                  >
                  > I'll do more longer term testing along with the autobaud and let
                  you
                  > know how that goes.
                  >
                  > Mark
                  >
                  > --- In tracker2@yahoogroup <mailto:tracker2%40yahoogroups.com>
                  s.com,
                  > <scott@> wrote:
                  > >
                  > > Ok, new firmware is up. Peet Bros Ultimeter 2000 series weather
                  > stations
                  > > (2000, 2100, 800, 100, etc) are now supported. There's nothing to
                  > configure
                  > > on the tracker side if you've got AUTOBAUD on - just set your
                  > weather
                  > > station to complete record mode, and plug it in to either port on
                  > the
                  > > tracker.
                  > >
                  > > Right now it'll send both a position packet AND a weather packet
                  > (which
                  > > includes position) when it's ready to transmit. I've got to
                  figure
                  > out how
                  > > I want to restrict which packets get sent when.
                  > >
                  > > Scott
                  > >
                  >
                • k0yg
                  I m in fixed position mode. Mark ... reports ... in the ... transmit a ... the weather ... Behalf ... good ... a ... you ... s.com, ... figure
                  Message 8 of 21 , Oct 23, 2006
                  • 0 Attachment
                    I'm in fixed position mode.

                    Mark


                    --- In tracker2@yahoogroups.com, <scott@...> wrote:
                    >
                    > I didn't mention the WXINFO command because it's still flawed - it
                    reports
                    > whatever is in memory at the moment, which might be invalid if it's
                    in the
                    > middle of parsing a string.
                    >
                    > Were you using a GPS receiver or fixed position mode?
                    >
                    > Right now, timing is dependent on the INTERVAL setting. It'll
                    transmit a
                    > weather packet whenever it transmits a position packet, assuming
                    the weather
                    > data is valid.
                    >
                    > Scott
                    >
                    >
                    > _____
                    >
                    > From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On
                    Behalf
                    > Of k0yg
                    > Sent: Monday, October 23, 2006 1:00 PM
                    > To: tracker2@yahoogroups.com
                    > Subject: [tracker2] Re: Firmware build 54030
                    >
                    >
                    >
                    > Hi Scott,
                    >
                    > I loaded up the new build and connected my Peet Ultimeter 2000. I
                    > have the Ultimter connected to port 2 and the computer to port 1. I
                    > set the baud rate manually on port 2 to 2400. Here are my initial
                    > observations:
                    >
                    > 1. The new "WXINFO" command seems to report bad data along with
                    good
                    > data every once in a while. Here is a sample of what I get when I
                    > type WXINFO as fast as I can type:
                    >
                    > TEMP:-1226 WIND 139 AT 1794 GUST 1281 BARO -20478
                    > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                    > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                    > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                    > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                    > TEMP:819 WIND 412 AT -512 GUST 514 BARO 8192
                    > TEMP:1644 WIND 11 AT 0 GUST 1 BARO 638
                    > TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
                    > TEMP:91 WIND 486 AT 854 GUST 1730 BARO 304
                    > TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
                    > TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
                    > TEMP:952 WIND 361 AT 381 GUST 141 BARO 0
                    > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                    > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                    > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                    > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                    > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                    > TEMP:0 WIND 0 AT 1096 GUST 0 BARO 0
                    > TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
                    > TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
                    > TEMP:0 WIND 52 AT 0 GUST 258 BARO 8192
                    >
                    > Seems like this command should also report humidity. (I don't have
                    a
                    > himidity sensor attached so maybe this is why)
                    >
                    > 2. The T2 reports the humidity as "h00" but findu reports this as
                    > 100%.
                    >
                    > 3. When I set the transmit rate to every 2 minutes, the data being
                    > transmitted was correct once in a while and incorrect most of the
                    > time. For instance it reported humidity between 12% and 51% and
                    > sometimes zero. Here is a sample of the bad packets (part up to WX
                    > data has been truncated)
                    >
                    > _180/006g010t048P000h12b10211OU2k (humidity wrong)
                    > _180/000g000t053P000b10202OU2k (no humidity)
                    > _180/000g000t053P000b10202OU2k (no humidity)
                    > _000/063g014t085P141h12b00731OU2k (everything is wrong)
                    > _180/000g003t055P000h51b10201OU2k (humidity wrong)
                    > _180/000g003t055P000h51b10201OU2k (humidity wrong)
                    >
                    > When I changed the transmit rate to every 4 minutes this problem
                    > seemed to happen less often with only the humidity being wrong
                    > sometimes.
                    >
                    > 4. Which combination of commands trigger the WX string to be
                    > transmitted? It seems like status needs to be something other than
                    > zero along with interval? Which one controls how often the strin is
                    > sent?
                    >
                    > I'll do more longer term testing along with the autobaud and let
                    you
                    > know how that goes.
                    >
                    > Mark
                    >
                    > --- In tracker2@yahoogroup <mailto:tracker2%40yahoogroups.com>
                    s.com,
                    > <scott@> wrote:
                    > >
                    > > Ok, new firmware is up. Peet Bros Ultimeter 2000 series weather
                    > stations
                    > > (2000, 2100, 800, 100, etc) are now supported. There's nothing to
                    > configure
                    > > on the tracker side if you've got AUTOBAUD on - just set your
                    > weather
                    > > station to complete record mode, and plug it in to either port on
                    > the
                    > > tracker.
                    > >
                    > > Right now it'll send both a position packet AND a weather packet
                    > (which
                    > > includes position) when it's ready to transmit. I've got to
                    figure
                    > out how
                    > > I want to restrict which packets get sent when.
                    > >
                    > > Scott
                    > >
                    >
                  • Clay Jackson
                    I may have asked this before; but has anyone looked at replacing the TASCO modem in the Kenwood TS2000 with an OT2? I ve got a friend who has 3 (I only have 1)
                    Message 9 of 21 , Oct 24, 2006
                    • 0 Attachment
                      I may have asked this before; but has anyone looked at replacing the
                      TASCO modem in the Kenwood TS2000 with an OT2?

                      I've got a friend who has 3 (I only have 1) and the service manual;
                      and he's looking at the configuration (where/how it's mounted, I/O,
                      etc). We would REALLY like to replace the TASCO 'pile' with a 'real'
                      TNC (definition of 'real' - a TNC that has enough memory/speed to
                      keep up with WinLink, AND will DIGI). I'm not a WinLink fan myself;
                      but there's a WHOLE bunch of EmComm folks who are, and a TS2000 with
                      an embedded OT2 would be a HUGE win; as would the Kenwood 2M Rig
                      (I've forgotten the model number on that one).

                      Thanks!

                      Clay
                      N7QNM
                    • scott@opentrac.org
                      Let me know what you find out - send pictures, too. Sounds like a good candidate for my next project, if not the T2. Scott _____ From:
                      Message 10 of 21 , Oct 25, 2006
                      • 0 Attachment
                        Let me know what you find out - send pictures, too.  Sounds like a good candidate for my next project, if not the T2.
                         
                        Scott


                        From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Clay Jackson
                        Sent: Tuesday, October 24, 2006 11:01 PM
                        To: tracker2@yahoogroups.com
                        Subject: [tracker2] TS2000 vs OT2

                        I may have asked this before; but has anyone looked at replacing the
                        TASCO modem in the Kenwood TS2000 with an OT2?

                        I've got a friend who has 3 (I only have 1) and the service manual;
                        and he's looking at the configuration (where/how it's mounted, I/O,
                        etc). We would REALLY like to replace the TASCO 'pile' with a 'real'
                        TNC (definition of 'real' - a TNC that has enough memory/speed to
                        keep up with WinLink, AND will DIGI). I'm not a WinLink fan myself;
                        but there's a WHOLE bunch of EmComm folks who are, and a TS2000 with
                        an embedded OT2 would be a HUGE win; as would the Kenwood 2M Rig
                        (I've forgotten the model number on that one).

                        Thanks!

                        Clay
                        N7QNM

                      • Clay Jackson
                        OK - well, the word is that the DM700 does have a separate board, so I would almost guess that the Alinco board would fit, perhaps with a different connector.
                        Message 11 of 21 , Oct 25, 2006
                        • 0 Attachment
                          OK - well, the word is that the DM700 does have a separate board, so I would almost guess that the Alinco board would fit, perhaps with a different connector.  Speaking of connectors, a friend sent me this link - they might be able to get you connectors for the Alinco.

                          www.samtec.com


                          I'll keep you posted!

                          Clay

                          On Oct 25, 2006, at 1:01 PM, <scott@...> <scott@...> wrote:

                          Let me know what you find out - send pictures, too.  Sounds like a good candidate for my next project, if not the T2.
                           
                          Scott


                          From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of Clay Jackson
                          Sent: Tuesday, October 24, 2006 11:01 PM
                          To: tracker2@yahoogroups.com
                          Subject: [tracker2] TS2000 vs OT2

                          I may have asked this before; but has anyone looked at replacing the
                          TASCO modem in the Kenwood TS2000 with an OT2?

                          I've got a friend who has 3 (I only have 1) and the service manual;
                          and he's looking at the configuration (where/how it's mounted, I/O,
                          etc). We would REALLY like to replace the TASCO 'pile' with a 'real'
                          TNC (definition of 'real' - a TNC that has enough memory/speed to
                          keep up with WinLink, AND will DIGI). I'm not a WinLink fan myself;
                          but there's a WHOLE bunch of EmComm folks who are, and a TS2000 with
                          an embedded OT2 would be a HUGE win; as would the Kenwood 2M Rig
                          (I've forgotten the model number on that one).

                          Thanks!

                          Clay
                          N7QNM


                        • James Ewen
                          You are looking to open a new can of worms... The Alinco radio simply has a slot where the TASCO modem board connects to the radio interface. The Kenwood radio
                          Message 12 of 21 , Oct 25, 2006
                          • 0 Attachment
                            You are looking to open a new can of worms...
                             
                            The Alinco radio simply has a slot where the TASCO modem board connects to the radio interface.
                             
                            The Kenwood radio does the same, but it also has firmware that talks to the TASCO board from the user interface side. The OT device would need to talk the same language that the TASCO modem does, and then at that, what improvements can you get?
                             
                            If you could swap out the modem board, and gain access to the user interface firmware in the Kewood allowing us to change the user interface, and make use of features available in the OT product.
                             
                            James
                            VE6SRV
                          • Clay Jackson
                            The firmware will definitely need addressing; but, I m guessing that it s pretty simple, because the Kenwood commands look real similar to the Tasco
                            Message 13 of 21 , Nov 1, 2006
                            • 0 Attachment
                              The firmware will definitely need addressing; but, I'm guessing that it's pretty simple, because the 'Kenwood' commands look real similar to the 'Tasco' commands documented in the Alinco manual.  My guess is that all they REALLY do is pass the inputs from the serial port on to the TASCO, and perhaps generate a few commands from the radio firmware to handle the front panel functions like setting baud rate and so on.

                              My friend with the TS2000 Service Manual has been tied up recently (as have I) with family stuff; but, as soon as we can get together, I'll have more information to share.  if the physical interface on the Kenwood side has a data in/data out that connects to the serial port, then I think we're in business.

                              Clay
                              =====

                              On Oct 25, 2006, at 10:40 PM, James Ewen wrote:

                              You are looking to open a new can of worms...
                               
                              The Alinco radio simply has a slot where the TASCO modem board connects to the radio interface.
                               
                              The Kenwood radio does the same, but it also has firmware that talks to the TASCO board from the user interface side. The OT device would need to talk the same language that the TASCO modem does, and then at that, what improvements can you get?
                               
                              If you could swap out the modem board, and gain access to the user interface firmware in the Kewood allowing us to change the user interface, and make use of features available in the OT product.
                               
                              James
                              VE6SRV

                            • James Ewen
                              ... The commands look similar because they are the same units. My guess is that all they REALLY do is pass the inputs from the serial port ... That is where
                              Message 14 of 21 , Nov 1, 2006
                              • 0 Attachment
                                On 11/2/06, Clay Jackson <clayj@...> wrote:
                                The firmware will definitely need addressing; but, I'm guessing that it's pretty simple, because the 'Kenwood' commands look real similar to the 'Tasco' commands documented in the Alinco manual. 

                                The commands look similar because they are the same units.

                                My guess is that all they REALLY do is pass the inputs from the serial port on to the TASCO, and perhaps generate a few commands from the radio firmware to handle the front panel functions like setting baud rate and so on.

                                That is where the problem lies. If you are going to replace the TNC in the Kenwood, it has to respond to the commands that are sent from the Kenwood user interface firmware. Unless , of course, you are going to ignore most of the radio, and only use the TNC and one transmitter and receiver.

                                I would suggest that if you are looking to do the latter, it would be cheaper to buy an Alinco, especially if you are looking to do so with a TS-2000.

                                James
                                VE6SRV
                              • Clay Jackson
                                Good points - turns out were kinda screwed on this anyway. I got a look at a Service Manual (online) last nite; and, from what I could tell (I wasn t able to
                                Message 15 of 21 , Nov 4, 2006
                                • 0 Attachment
                                  Good points - turns out were kinda screwed on this anyway.  I got a look at a Service Manual (online) last nite; and, from what I could tell (I wasn't able to bring up the board pictorials, but did look at the schematic and the component lists) the TNC is actually a two chip set installed on the main logic board.   So, it would take a fair amount of hardware hacking to replace 'em anyway; and then, as you point out, the firmware would probably still be an issue.

                                  Oh, well - it was a thought...

                                  Clay
                                  N7QNM

                                  On Nov 1, 2006, at 9:56 PM, James Ewen wrote:

                                  On 11/2/06, Clay Jackson <clayj@...> wrote:
                                  The firmware will definitely need addressing; but, I'm guessing that it's pretty simple, because the 'Kenwood' commands look real similar to the 'Tasco' commands documented in the Alinco manual. 

                                  The commands look similar because they are the same units.

                                  My guess is that all they REALLY do is pass the inputs from the serial port on to the TASCO, and perhaps generate a few commands from the radio firmware to handle the front panel functions like setting baud rate and so on.

                                  That is where the problem lies. If you are going to replace the TNC in the Kenwood, it has to respond to the commands that are sent from the Kenwood user interface firmware. Unless , of course, you are going to ignore most of the radio, and only use the TNC and one transmitter and receiver.

                                  I would suggest that if you are looking to do the latter, it would be cheaper to buy an Alinco, especially if you are looking to do so with a TS-2000.

                                  James
                                  VE6SRV

                                • Wes Johnston, AI4PX
                                  Also, I ve watched my d700 talk to the TNC... just to collect GPRMC and GPGGA, it has to constantly set the buffer to either/or. Once the data is collected
                                  Message 16 of 21 , Nov 4, 2006
                                  • 0 Attachment
                                    Also, I've watched my d700 talk to the TNC... just to collect GPRMC and GPGGA, it has to constantly set the buffer to either/or.  Once the data is collected and it has constructed a packet to send, it does it in two steps.  It first sets the UI path to the longitude and path, then as soon as the TNC accepts that command it puts it into converse mode and sends the data portion of the mic-e packet.  Then it's back to command mode and toggling between GPRMC and GPGGA.  Pretty clunky.  I suppose if the OT tnc would just gobble up any old command and not send an error message, the kenwood would believe that the command was accepted.  The OT TNC would simply ignore the things that kenwood sends it (except for messages and message ACKs), and pretty much decide on it's own what and when to send.  It's like you would have a MYCALL command on the kenwood menu, but the OT would ignore it.  Any packet received would simply be passed along to the kenwood to display.
                                     
                                    I tried once to make smartbeaconing work on the d700 by making a supervisory processor watch for the conditions to trigger a beacon and send the BCN 0<cr>BCN 1<cr> commands.  Problem was that if it wanted to beacon and you were entering a message on the mic keypad, it would bail out of your message when the BCN commands hit on the serial port.  'Twas just to aggrivating.
                                    Wes

                                     
                                    On 11/4/06, Clay Jackson <clayj@...> wrote:

                                    Good points - turns out were kinda screwed on this anyway.  I got a look at a Service Manual (online) last nite; and, from what I could tell (I wasn't able to bring up the board pictorials, but did look at the schematic and the component lists) the TNC is actually a two chip set installed on the main logic board.   So, it would take a fair amount of hardware hacking to replace 'em anyway; and then, as you point out, the firmware would probably still be an issue.


                                     
                                    Oh, well - it was a thought...

                                     
                                    Clay
                                    N7QNM

                                    On Nov 1, 2006, at 9:56 PM, James Ewen wrote:

                                    On 11/2/06, Clay Jackson <clayj@...> wrote:
                                    The firmware will definitely need addressing; but, I'm guessing that it's pretty simple, because the 'Kenwood' commands look real similar to the 'Tasco' commands documented in the Alinco manual. 

                                    The commands look similar because they are the same units.
                                     

                                    My guess is that all they REALLY do is pass the inputs from the serial port on to the TASCO, and perhaps generate a few commands from the radio firmware to handle the front panel functions like setting baud rate and so on.

                                    That is where the problem lies. If you are going to replace the TNC in the Kenwood, it has to respond to the commands that are sent from the Kenwood user interface firmware. Unless , of course, you are going to ignore most of the radio, and only use the TNC and one transmitter and receiver.
                                     

                                    I would suggest that if you are looking to do the latter, it would be cheaper to buy an Alinco, especially if you are looking to do so with a TS-2000.

                                    James
                                    VE6SRV

                                     




                                    --
                                    Where there's silence, there is no Hope.
                                  • KB4YTM
                                    Hey Scott, When this is available, will it do both kiss mode AND 1-wire wx at the same time? Thanks Richard KB4YTM ... Behalf
                                    Message 17 of 21 , Nov 4, 2006
                                    • 0 Attachment
                                      Hey Scott,

                                      When this is available, will it do both kiss mode AND 1-wire wx at the
                                      same time?

                                      Thanks
                                      Richard
                                      KB4YTM


                                      --- In tracker2@yahoogroups.com, <scott@...> wrote:
                                      >
                                      > Nope. That's next.
                                      >
                                      > Scott
                                      >
                                      >
                                      > _____
                                      >
                                      > From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On
                                      Behalf
                                      > Of Mark Miller
                                      > Sent: Monday, October 23, 2006 2:29 PM
                                      > To: tracker2@yahoogroups.com
                                      > Subject: RE: [tracker2] Re: Firmware build 54030
                                      >
                                      >
                                      >
                                      > Will the Dallas 1-wire weather station work with this build?
                                      >
                                      > 73,
                                      >
                                      > Mark N5RFX
                                      >
                                    • scott@opentrac.org
                                      Yeah. Does Peet Bros and KISS at the same time now. Once I get the 1-wire stuff ported, you should be able to do 1-wire weather, KISS, digipeating, and
                                      Message 18 of 21 , Nov 4, 2006
                                      • 0 Attachment
                                        Yeah.  Does Peet Bros and KISS at the same time now.  Once I get the 1-wire stuff ported, you should be able to do 1-wire weather, KISS, digipeating, and tracking with waypoint output (or console mode) at the same time.  Not that many people use mobile weather stations, but there are a few.
                                         
                                        Scott


                                        From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of KB4YTM
                                        Sent: Saturday, November 04, 2006 7:43 PM
                                        To: tracker2@yahoogroups.com
                                        Subject: [tracker2] Re: Firmware build 54030

                                        Hey Scott,

                                        When this is available, will it do both kiss mode AND 1-wire wx at the
                                        same time?

                                        Thanks
                                        Richard
                                        KB4YTM

                                        --- In tracker2@yahoogroup s.com, <scott@...> wrote:
                                        >
                                        > Nope. That's next.
                                        >
                                        > Scott
                                        >
                                        >
                                        > _____
                                        >
                                        > From: tracker2@yahoogroup s.com [mailto:tracker2@yahoogroup s.com] On
                                        Behalf
                                        > Of Mark Miller
                                        > Sent: Monday, October 23, 2006 2:29 PM
                                        > To: tracker2@yahoogroup s.com
                                        > Subject: RE: [tracker2] Re: Firmware build 54030
                                        >
                                        >
                                        >
                                        > Will the Dallas 1-wire weather station work with this build?
                                        >
                                        > 73,
                                        >
                                        > Mark N5RFX
                                        >

                                      • EM Sharp
                                        Should I be looking for a hardware problem? My OT2 while running on build 54030 gives a Temp of B9C when the Temp Offset is set to 16. With other settings the
                                        Message 19 of 21 , Nov 25, 2006
                                        • 0 Attachment
                                          Should I be looking for a hardware problem?
                                          My OT2 while running on build 54030 gives a Temp of B9C when the Temp
                                          Offset is set to 16. With other settings the display is also not what
                                          I would expect.

                                          Should I be looking for a hardware problem or is there a problem with
                                          the firmware and/or configuration program?

                                          Is there a way (Command or otherwise) of setting the offset from
                                          Command Mode without going back to the Configuration program?

                                          I am still running with the release B values in the filter for the
                                          2211 decoder and the unit is not doing too well and is VERY sensitive
                                          to audio level. Are the values given in the 9/10/2006 Tracker2
                                          Revision the best current ones to be used? In other words, should I
                                          update the card with these components to improve decode?

                                          Elmer
                                        • scott@opentrac.org
                                          Yeah, that s weird. Did you check the voltage on the temperature sensor? It should read 10 mV per kelvin, so at room temperature it should be around 2.9
                                          Message 20 of 21 , Nov 27, 2006
                                          • 0 Attachment
                                            Yeah, that's weird.  Did you check the voltage on the temperature sensor?  It should read 10 mV per kelvin, so at room temperature it should be around 2.9 volts.
                                             
                                            I could have sworn I added a temperature offset command - I'm going to have to go check on that.
                                             
                                            Do you have a 5.1k or 51k resistor installed on the 2211?  Is your board a B or C?  Have you tried tuning it using an external audio source, like the APRS TNC test CD?  You can use the alternating tones to set the demodulator to 50% duty cycle.
                                             
                                            Scott


                                            From: tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com] On Behalf Of EM Sharp
                                            Sent: Saturday, November 25, 2006 5:36 PM
                                            To: tracker2@yahoogroups.com
                                            Subject: [tracker2] Firmware build 54030

                                            Should I be looking for a hardware problem?
                                            My OT2 while running on build 54030 gives a Temp of B9C when the Temp
                                            Offset is set to 16. With other settings the display is also not what
                                            I would expect.

                                            Should I be looking for a hardware problem or is there a problem with
                                            the firmware and/or configuration program?

                                            Is there a way (Command or otherwise) of setting the offset from
                                            Command Mode without going back to the Configuration program?

                                            I am still running with the release B values in the filter for the
                                            2211 decoder and the unit is not doing too well and is VERY sensitive
                                            to audio level. Are the values given in the 9/10/2006 Tracker2
                                            Revision the best current ones to be used? In other words, should I
                                            update the card with these components to improve decode?

                                            Elmer

                                          • wa2ysm
                                            Scott: 1) My problem on the temp sensor. I installed it backwards, my glasses must have been dirty -- shame on me. I think I fried it because it now produces
                                            Message 21 of 21 , Nov 28, 2006
                                            • 0 Attachment
                                              Scott:
                                              1) My problem on the temp sensor. I installed it backwards, my glasses
                                              must have been dirty -- shame on me. I think I fried it because it now
                                              produces 1.5 v at room temp. I'll order a fresh one in my next batch of
                                              stuff.
                                              2) Can't help you on this one. If the command is there to set temp
                                              offset, I haven't found it in the command file -- maybe I just don't
                                              know what name to look for.
                                              3) I have a 4.7K resistor installed in the 2211 circuit (as R8). My
                                              board is a reasonably early B version. I have replaced the C1 cap which
                                              was .1 uf with a .01 cap. Decode is working much better. Can I use the
                                              CALIBRATE ALT function with the jumper set for loop back (JP1-2+3) as a
                                              50% duty cycle until I get a CD or some other source of audio. Maybe I
                                              should just use another TNC in calibrate mode as the data source -- I
                                              have TINY2's, AEA PK96's, and TAPR2 clones all of which produce
                                              alternating tones. A 'scope to observe is no problem for me. I will
                                              get a CD however when I can get around to it.
                                              -----
                                              (((
                                              I am having a bit of a problem setting the deviation level on the
                                              OpenTracker 1. What is the recommended method of keying it up to
                                              measure the deviation produced by the radio (HT, Mobile or whatever)? We
                                              are running several of these and some of them are not being decoded as
                                              reliably as I would like by TNC's with 2211's in them.
                                              )))

                                              Elmer

                                              scott@... wrote:
                                              >
                                              > Yeah, that's weird. Did you check the voltage on the temperature
                                              > sensor? It should read 10 mV per kelvin, so at room temperature it
                                              > should be around 2.9 volts.
                                              >
                                              > I could have sworn I added a temperature offset command - I'm going to
                                              > have to go check on that.
                                              >
                                              > Do you have a 5.1k or 51k resistor installed on the 2211? Is your
                                              > board a B or C? Have you tried tuning it using an external audio
                                              > source, like the APRS TNC test CD? You can use the alternating tones
                                              > to set the demodulator to 50% duty cycle.
                                              >
                                              > Scott
                                              >
                                              > ------------------------------------------------------------------------
                                              > *From:* tracker2@yahoogroups.com [mailto:tracker2@yahoogroups.com]
                                              > *On Behalf Of *EM Sharp
                                              > *Sent:* Saturday, November 25, 2006 5:36 PM
                                              > *To:* tracker2@yahoogroups.com
                                              > *Subject:* [tracker2] Firmware build 54030
                                              >
                                              > Should I be looking for a hardware problem?
                                              > My OT2 while running on build 54030 gives a Temp of B9C when the Temp
                                              > Offset is set to 16. With other settings the display is also not what
                                              > I would expect.
                                              >
                                              > Should I be looking for a hardware problem or is there a problem with
                                              > the firmware and/or configuration program?
                                              >
                                              > Is there a way (Command or otherwise) of setting the offset from
                                              > Command Mode without going back to the Configuration program?
                                              >
                                              > I am still running with the release B values in the filter for the
                                              > 2211 decoder and the unit is not doing too well and is VERY sensitive
                                              > to audio level. Are the values given in the 9/10/2006 Tracker2
                                              > Revision the best current ones to be used? In other words, should I
                                              > update the card with these components to improve decode?
                                              >
                                              > Elmer
                                              >
                                              >
                                            Your message has been successfully submitted and would be delivered to recipients shortly.