It should be much higher than that.  If you pull the diodes and it's
still that low, the MCU might be blown.  You can send it back in any
time and we'll check it out here.

Scott

On 1/14/2013 8:39 PM, Brian Amos wrote:
> I haven't followed the schematic completely, but is 2ohms a normal
> resistance between the cn4 5v pin and ground? and if not then is this
> likely the cause of the chip not booting?  Looks like I may have to
> replace the diodes anyway...
>
> Brian
> KF7OVD
>
>
> On Mon, Jan 14, 2013 at 3:10 PM, Brian Amos <bamos1@...
> <mailto:bamos1@...>> wrote:
>
>     The 12v supply was a battery, and the 5v supply was my laptop during
>     the previous testing, they were not connected at the same time.
>
>     D3 is gone D4 is gone too... (both easily repaired I believe), however:
>
>     Feeding 5v from a regulated power supply into CN4 produces no led
>     activity.  My best guess is that somehow the main chip had some
>     failure when the power cycled quickly, that must have blown out D4
>     and D3. My only other explanation is that the leds went at the same
>     time as D4 and D3 and the chip is working but showing no visible
>     manifestation. I will check out that (remote/very remote)
>     possibility tonight by trying to get a computer connection to the
>     unit while powered from CN4.
>
>     Maybe it's worth while to note that I recently purchased the unit
>     and since I got it more than once it has either stopped responding
>     or has switched into a constant ptt engaged state when turned on.
>     Every time I have had to use the erase device and load firmware
>     option as it wasn't able to find the device otherwise (always using
>     usb connection).  Although every time I have been able to correspond
>     it to something such as the plug not being completely in the radio
>     when it was turned on, or having the tracker plugged into the
>     cigarette lighter when starting the vehicle, ie. user error.  When I
>     was traveling out of town and it wouldn't light up it had been
>     plugged into a 5v usb cigarette lighter adapter (possibly a 1amp
>     adapter) that was powering the tracker and my telephone.  A spring
>     broke on one of the side rails on the usb cigarette lighter adapter
>     and the unit became loose in the socket and the power connection
>     flickered on and off a couple of times before I noticed that my
>     phone was complaining and I unplugged it.  I assumed that as it
>     would easily be read by the computer when I got home, but when that
>     didn't happen I looked to the list archives for help, but couldn't
>     find anything. I hope my problem will be a word of warning to all,
>     make sure your tracker power isn't allowed to shut off and on
>     quickly and repeatedly, or you may have a similar problem as I have.
>
>     Thank you,
>
>     Brian
>     KF7OVD
>
>
>     On Mon, Jan 14, 2013 at 2:32 PM, Scott Miller <scott@...
>     <mailto:scott@...>> wrote:
>
>         Was it connected to anything else that had a separate ground return?
>
>         Scott
>
>         On 1/13/2013 2:49 PM, Brian Amos wrote:
>          > some further testing shows that D3 has 12v in and nothing
>         out, so that
>          > is probably the culprit, although c3 seems to not be
>         functioning either
>          > (no voltage potential across the cap), so I assume whatever
>         happened
>          > happened caused those two at least to malfunction (possibly
>         the voltage
>          > regulator as well).
>          >
>          > If this is the case, why would it not function using power
>         from the usb?
>          > And why would all this happen on the 12v input area when I
>         was using it
>          > with the 12v supply side unhooked and powering from a 5v
>         regulated supply?
>          >
>          > Brian
>          >
>          >
>          > On Sun, Jan 13, 2013 at 1:06 PM, Brian Amos <bamos1@...
>         <mailto:bamos1@...>
>          > <mailto:bamos1@... <mailto:bamos1@...>>> wrote:
>          >
>          >     Using your 12v cigarette lighter adapter into a 12v battery:
>          >     I get 12 v in from the DB-9
>          >     U1 registers no voltage difference between the CN4 8 pin
>         (ground)
>          >     and either the 12v or the 5v side of the voltage regulator.
>          >     The diode D4 shows no voltage on any of the pins either.
>          >     R-11 shows 12v on the left and ~.6v on the right
>          >
>          >     With 12v unplugged and using 5v usb power:
>          >     D4 shows 5v on top pin
>          >     cn4 pin 1 shows no voltage
>          >
>          >     I am going to try to make time to check for a broken
>         trace this
>          >     afternoon.
>          >
>          >     Glad to know that this list is customer service.
>          >
>          >     Thank you,
>          >     Brian KF7OVD
>          >
>          >
>          >     On Fri, Jan 11, 2013 at 11:10 PM, Scott Miller
>         <scott@... <mailto:scott@...>
>          >     <mailto:scott@... <mailto:scott@...>>>
>         wrote:
>          >
>          >         What's the 12v power source?  If it's one of our
>         tracker cables
>          >         with a
>          >         cigarette lighter, unscrew the tip and check that the
>         fuse is OK.
>          >
>          >         The left side of the voltage regulator is the input
>         and the tab
>          >         is the
>          >         output.  You should see 12v at the left side, and 5v
>         on the
>          >         right side.
>          >            Diode D4, down and to the right from there, separates
>          >         regulator power
>          >         and USB power.  You should see 5v at one of the legs, and
>          >         slightly less
>          >         than that at the center pin.
>          >
>          >         Scott
>          >
>          >         On 1/11/2013 6:57 PM, Brian Amos wrote:
>          >          > Its not getting 5 volts with the usb powering it
>         or with 12v.
>          >         The odd
>          >          > thing is with 12v power source the voltage
>         regulator isn't
>          >         getting 12v
>          >          > either. Looks like I may have to call customer
>         service Monday...
>          >          >
>          >          > Brian
>          >          > KF7OVD
>          >          > On Jan 11, 2013 10:57 AM, "Scott Miller" wrote:
>          >          >
>          >          >  > If you've got a voltmeter, you can check the
>         output of the
>          >         regulator and
>          >          >  > see if it's getting 5v.
>          >          >  >
>          >          >  > Scott
>          >          >  >
>          >          >  > On 1/10/2013 3:08 PM, bamos1 wrote:
>          >          >  > > I was using the otusb plugged into a 5v usb
>         adapter plug
>          >         on my vehicle
>          >          >  > > and the power flashed off and on quickly, now
>         the otusb
>          >         will not light
>          >          >  > > up with either 12v or connected to the USB. I
>         have
>          >         determined that the
>          >          >  > > 5v usb converter is loose and appears to have
>         lost
>          >         contact on hitting
>          >          >  > bumps.
>          >          >  > >
>          >          >  > > No lights come up but it appears to be
>         drawing power
>          >         from the usb host.
>          >          >  > > Windows and linux both are not recognizing
>         the device
>          >         either.
>          >          >  > >
>          >          >  > > How can I fix this?
>          >          >  > > Thanks,
>          >          >  > >
>          >          >  > > Brian, KF7OVD
>          >          >  > >
>          >          >  > >
>          >          >  >
>          >          >  >
>          >          >  >
>          >          >  > ------------------------------------
>          >          >  >
>          >          >  > Yahoo! Groups Links
>          >          >  >
>          >          >  >
>          >          >  >
>          >          >  >
>          >          >
>          >          >
>          >
>          >
>          >         ------------------------------------
>          >
>          >         Yahoo! Groups Links
>          >
>          >
>          > tracker2-fullfeatured@yahoogroups.com
>         <mailto:tracker2-fullfeatured@yahoogroups.com>
>          >         <mailto:tracker2-fullfeatured@yahoogroups.com
>         <mailto:tracker2-fullfeatured@yahoogroups.com>>
>          >
>          >
>          >
>          >
>          >
>
>
>
>         ------------------------------------
>
>         Yahoo! Groups Links
>
>
>         tracker2-fullfeatured@yahoogroups.com
>         <mailto:tracker2-fullfeatured@yahoogroups.com>
>
>
>
>
>

Scott,

Thanks for the helpful response. I'll have to pull the units from the boat and
do some bench testing. Something has gone amiss.

Marc

--- In tracker2@yahoogroups.com, Scott Miller  wrote:
>
> Hi,
>
>  > The current system consists of:
> > 1. OT1m
> > 2. VX150 2m radio (power switched by OT1m)
> > 3. GPS receiver (always powered)
> > 4. Comet B-10 antenna
> >
> > The system has always drawn too much power. (I.e., 4d battery drops
> > below 12.0 VDC after 1-2 months, which is much faster than
>
> Have you put an ammeter on it to check what it's drawing?  The GPS
> receiver will probably draw around 50 mA, and an OT1m maybe around 12 mA.
>
> For current models, you can expect about 20 mA for the OTUSB and around
> 70 mA for the OT3m, though that should drop with future firmware updates.
>
> > 1. Tracker with low stand-by current.
> > 2. Ability to power-down the radio and GPS until needed.
> > 3. 5W or more.
> > 4. Ability to plug-in laptop to send and receive Winlink email. (lowest
> > priority)
>
> The T3 has higher standby current, but it's also going to be your best
> bet for Winlink.  I've been doing a lot of work in the last week to get
> connected mode applications working smoothly using KISS.  Some of that
> will carry over to the OTUSB.  A few tweaks will also go to the T2 but
> it doesn't have the extra RAM the newer units do.
>
> No GPS power-down yet, but as time allows I'll be experimenting with
> low-power modes on various GPS receivers.
>
> Scott
>

Dear All,

We are using 2 units of T2s as mountain top WIDE digipeaters for 2M
and 70cm.  As we are seeing very low usage on the 70cm side, we would
like to add some other packet services such as BBS and/or Winlink.

I understand this has been asked before, but I like to get a final
confirmation whether the T2 can support digipeating of BBS and/or
Winlink packets?  I have tried looking around and I see that the T2
does not support Winlink when connected to a host computer, but am not
sure if this would work as a digipeater.

Thank you.

73,
Sion Chow Q. C.,
9M2CQC, WQ2C

Hi,

I've been doing a lot of testing with the T3 lately for connected mode
use, and there are a couple of easy tweaks I can back-port to the T2.
If you've got a setup you'd like to test (that you can access easily to
update) let me know and I'll send you a new firmware version.

Scott

On 1/15/2013 5:58 PM, Sion Chow Q. C. (9W2QC) wrote:
> Dear All,
>
> We are using 2 units of T2s as mountain top WIDE digipeaters for 2M
> and 70cm. As we are seeing very low usage on the 70cm side, we would
> like to add some other packet services such as BBS and/or Winlink.
>
> I understand this has been asked before, but I like to get a final
> confirmation whether the T2 can support digipeating of BBS and/or
> Winlink packets? I have tried looking around and I see that the T2
> does not support Winlink when connected to a host computer, but am not
> sure if this would work as a digipeater.
>
> Thank you.
>
> 73,
> Sion Chow Q. C.,
> 9M2CQC, WQ2C
>
>

Scott,

This is the T2 firmware to support connected mode packets?  I would
not mind testing, but let me see if I have a spare T2 to do this
first.  Another one has been sent for packaging for another hill top
digi.

Has there been any previous success getting connected packets digied
via the T2 in the past?

73, Sion, 9M2CQC


Quoting Scott Miller <scott@...>:

> Hi,
>
> I've been doing a lot of testing with the T3 lately for connected mode
> use, and there are a couple of easy tweaks I can back-port to the T2.
> If you've got a setup you'd like to test (that you can access easily to
> update) let me know and I'll send you a new firmware version.
>
> Scott
>
> On 1/15/2013 5:58 PM, Sion Chow Q. C. (9W2QC) wrote:
>> Dear All,
>>
>> We are using 2 units of T2s as mountain top WIDE digipeaters for 2M
>> and 70cm. As we are seeing very low usage on the 70cm side, we would
>> like to add some other packet services such as BBS and/or Winlink.
>>
>> I understand this has been asked before, but I like to get a final
>> confirmation whether the T2 can support digipeating of BBS and/or
>> Winlink packets? I have tried looking around and I see that the T2
>> does not support Winlink when connected to a host computer, but am not
>> sure if this would work as a digipeater.
>>
>> Thank you.
>>
>> 73,
>> Sion Chow Q. C.,
>> 9M2CQC, WQ2C
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

> Scott if you were to look at low power modes then it would be worth
> switching to the binary protocol and looking for a GPS module with hot
> start capabilities.   I think it wouldn 't be too hard to then put in a

I'll probably start with the GT320FW.  I've got specs on the Prolific
binary format around here somewhere.  I'm mostly not sure how good the
first fix or two will be.

> could somehow get the PARAM information into the TNC so that APRS.fi can
> give us pretty graphs of battery volts etc.   I'd certainly be willing
> to buy/build/test such a unit.  I've got two boats to test it on (yes

Do you mean from an NMEA stream?  Send me samples and I'll see what can
be done.

Don't be surprised if I'm not very responsive this week, though.  Parts
are due in tomorrow morning and we'll be going flat out for a day or two
trying to get caught up.

Scott

To clarify, this is to support packets (digi'd or through KISS) used by
connected mode applications, and is *not* a connected mode AX.25 stack
in itself.

The most important thing I found is that some very small packets were
getting dropped as invalid.  No APRS packet would be that small, so it
hadn't turned up in APRS operation.  It shouldn't affect digi operation,
though, because the presence of a digi path would make it larger than
that threshold.

Scott

On 1/15/2013 6:48 PM, Sion Chow Q. C. (9W2QC) wrote:
> Scott,
>
> This is the T2 firmware to support connected mode packets? I would
> not mind testing, but let me see if I have a spare T2 to do this
> first. Another one has been sent for packaging for another hill top
> digi.
>
> Has there been any previous success getting connected packets digied
> via the T2 in the past?
>
> 73, Sion, 9M2CQC
>
> Quoting Scott Miller scott@... <mailto:scott%40opentrac.org>>:
>
>  > Hi,
>  >
>  > I've been doing a lot of testing with the T3 lately for connected mode
>  > use, and there are a couple of easy tweaks I can back-port to the T2.
>  > If you've got a setup you'd like to test (that you can access easily to
>  > update) let me know and I'll send you a new firmware version.
>  >
>  > Scott
>  >
>  > On 1/15/2013 5:58 PM, Sion Chow Q. C. (9W2QC) wrote:
>  >> Dear All,
>  >>
>  >> We are using 2 units of T2s as mountain top WIDE digipeaters for 2M
>  >> and 70cm. As we are seeing very low usage on the 70cm side, we would
>  >> like to add some other packet services such as BBS and/or Winlink.
>  >>
>  >> I understand this has been asked before, but I like to get a final
>  >> confirmation whether the T2 can support digipeating of BBS and/or
>  >> Winlink packets? I have tried looking around and I see that the T2
>  >> does not support Winlink when connected to a host computer, but am not
>  >> sure if this would work as a digipeater.
>  >>
>  >> Thank you.
>  >>
>  >> 73,
>  >> Sion Chow Q. C.,
>  >> 9M2CQC, WQ2C
>  >>
>  >>
>  >
>  >
>  > ------------------------------------
>  >
>  > Yahoo! Groups Links
>  >
>  >
>  >
>  >
>
>

On Tue, Jan 15, 2013 at 8:42 PM, Matthew Cook <vk5zm@...> wrote:

> Scott if you were to look at low power modes then it would be worth
> switching to the binary protocol and looking for a GPS module with hot start
> capabilities.   I think it wouldn 't be too hard to then put in a script
> that allowed us to switch profiles when the boat starts to move, which then
> switches from a 30min update rate to a smart beaconing routine taylored for
> yachts/power boats.

We already have the scripting capability, profile switching based on
speed, and fixed rate/SmartBeaconing. Using the binary protocol
however would mean that you would be limited one one specific GPS, or
series of GPS as each one will have a proprietary communications
protocol. NMEA is a common language.

> It's then just a simple matter of switching the HT at
> the appropriate time. It would also be nice if we could somehow get the
> PARAM information into the TNC so that APRS.fi can give us pretty graphs of
> battery volts etc.

You can do that with scripting right now. Not many places display the
telemetry parameters. If you are only wanting to get the parameters
into aprs.fi, you can simply send the parameters once, and they will
"stick" for a very long time.

>  I'd certainly be willing to buy/build/test such a unit.
> I've got two boats to test it on (yes I'm greedy and likes my
> boating/fishing), and a mate of mine has a shiny new sports car that sits in
> his garage that wants one also.   Definitely food for thought.

Pony up the pennies... you've got 95% of what you are asking for
sitting on the shelf!

The OT+ will do everything you want except talk in a proprietary
binary mode to the GPS of your choice, and poll it for a position.

--
James
VE6SRV

I see that there are two "legacy serial ports" (non-USB) on the T3-135. One is
router to the DB-9 on the back of the radio (pins 2/3/5), and one is internally
routed to the Alinco motherboard.

First let me explain that I am not using an Alinco, but instead interfacing this
to a Motorola Maxtrac radio. I am trying to send either KISS or command line
interface out through the front RJ-45 connector.

But no matter what I hook up, I can't seem to get any serial data out of the
system...

I can configure the TNC using OTWINCFG, but only through the USB port it seems.

So my questions are:
1) Which serial port (A or B) in OTWINCFG is the rear connector?
2) What do the TXD and RXD pins that are routed to the Alinco motherboard do?
Can they also be used for control/KISS?
3) Can the unit be configured through one of its serial ports instead of through
USB?

Thanks.

Dave Cameron
VE7LTD

> 1) Which serial port (A or B) in OTWINCFG is the rear connector?

Rear connector is port A.  Front (normally input-only on the 135) is B.

> 2) What do the TXD and RXD pins that are routed to the Alinco
> motherboard do? Can they also be used for control/KISS?

The RXD line comes from the data jack on the front of the radio when
it's in data mode.  Maybe it's possible to talk to the radio's MCU as
well, never really spent any time trying to figure that out.  I suspect
that connection is disabled in data mode, but I'm not certain.  Not
relevant for your application, anyway.  The port is fully functional, so
you can use it for any port B mode.

> 3) Can the unit be configured through one of its serial ports instead of
> through USB?

Yes, but only port A.

You might also be interested in the embeddable module version of the
OTUSB/T3 I'm testing now.  The first board rev had some glitches but is
usable with a jumper.  It's smaller than the T3-135 and includes a
regulator and a bunch of I/Os.  I just redesigned it to fit all of the
components on one side of the board and to make room for optional screw
terminal blocks.  Hadn't thought of that originally but my son swiped
one of the prototypes to use as a USB keyboard emulator for his arcade
cabinet project and that configuration worked out nicely.  I'll have the
new board rev in a couple of weeks.

A new rev of the T3-135 is off to the board house for prototyping within
the hour.  This one just fixes a couple of glitches, changes the
connector orientation, and shrinks the board by about 20%.

Scott

Hi Matthew,

I think you've shared some of the documentation with me before, but it's
been a while and I don't remember the details.  I'd be happy to look
over it again and see if I can incorporate some of that into the T3 and
maybe the T2.  Turns out one compiler optimization wasn't enabled and I
have something like 800 bytes to work with on the T2 now!

Scott

On 1/16/2013 8:23 PM, Matthew Cook wrote:
> I've already stumped the pennies into a T2 + Alinco HT for my yacht at
> least.  The scripts were easily written, mind you took me a while to debug.
>
> To solve this GPS Power/APRS tracker problem I've been working on a
> MSP430 that sits between the T2 and the GPS.  The MSP430 puts the GPS
> (ublox) into binary low power mode (hot start) and implements a variable
> GPS polling period (based upon speed) and then simply tells lies to the
> T2 every second by sending fake NMEA sentances.  The MSP430 currently
> adds 2mA to my overall consumption.  I've down to 25-27mA depending on
> how to look at the AVO.
>
> The MSP430 sits there and polls the GPS and watches the speed.  If the
> speed starts to change then the GPS polling period is varied, this
> should sound familiar?  Yes I've simply copied the SmartBeaconing(TM)
> algorithm again.
>
> Anyway if we could get a T3 that can read any one of the GPS units in a
> low power (and if necessary binary) mode and poll the GPS for a position
> before transmit then I'd certainly be looking for such a unit.
> Programming my MSP430 is a PITA, since I've got to copy the
> SmartBeaconing parameters out of the T2 and feed them into my software.
> It works but it's certainly not production ready, nor do I wish to
> release/develop this further.  Was just trying to solve the same problem
> as Marc.
>
> I hope that the ideas above gives Scott some thoughts as to how this low
> power GPS mode could be useful.
>
> I've found the hot start mechanism in the Atmel ublox is pretty good,
> meaning the positions when polled are coming out as expected.  The
> prolific chipsets I had no end of trouble with in general.  They were
> not as well supported as the ublox in terms of others having used them.
>
> With regard to the GPS, having a unit that can mount on the deck of the
> boat and sends serial back (hockey puck style) would be preferable to
> say a GPS module within the T3.  An internal module would require an
> external antenna with active preamp to get around the cable loss and NF
> issues, which adds 10-12mA to the overall current consumption; this will
> blow your power budget.
>
> The HT and T2 I've hidden under the deck using the HT rubber duck.  I've
> found that this gets into the local APRS system well when the boat is on
> the hard and isn't too shabby when out to sea.  I'm luck that my boat is
> plywood/fibreglass so no issues with faraday shields etc.  External 2m
> marine antennas aren't easily obtainable here in Australia, I'm
> certainly interested in any suggestions other APRS yachties might have,
> especially dual band inc 70cm :)
>
> 73's
>
> Matthew
> VK5ZM
>
> On 16 January 2013 15:10, James Ewen <ve6srv@...
> <mailto:ve6srv@...>> wrote:
>
>     __
>
>     On Tue, Jan 15, 2013 at 8:42 PM, Matthew Cook vk5zm@...
>     <mailto:vk5zm%40bistre.net>> wrote:
>
>      > Scott if you were to look at low power modes then it would be worth
>      > switching to the binary protocol and looking for a GPS module
>     with hot start
>      > capabilities. I think it wouldn 't be too hard to then put in a
>     script
>      > that allowed us to switch profiles when the boat starts to move,
>     which then
>      > switches from a 30min update rate to a smart beaconing routine
>     taylored for
>      > yachts/power boats.
>
>     We already have the scripting capability, profile switching based on
>     speed, and fixed rate/SmartBeaconing. Using the binary protocol
>     however would mean that you would be limited one one specific GPS, or
>     series of GPS as each one will have a proprietary communications
>     protocol. NMEA is a common language.
>
>
>      > It's then just a simple matter of switching the HT at
>      > the appropriate time. It would also be nice if we could somehow
>     get the
>      > PARAM information into the TNC so that APRS.fi can give us pretty
>     graphs of
>      > battery volts etc.
>
>     You can do that with scripting right now. Not many places display the
>     telemetry parameters. If you are only wanting to get the parameters
>     into aprs.fi <http://aprs.fi>, you can simply send the parameters
>     once, and they will
>     "stick" for a very long time.
>
>
>      > I'd certainly be willing to buy/build/test such a unit.
>      > I've got two boats to test it on (yes I'm greedy and likes my
>      > boating/fishing), and a mate of mine has a shiny new sports car
>     that sits in
>      > his garage that wants one also. Definitely food for thought.
>
>     Pony up the pennies... you've got 95% of what you are asking for
>     sitting on the shelf!
>
>     The OT+ will do everything you want except talk in a proprietary
>     binary mode to the GPS of your choice, and poll it for a position.
>
>     --
>     James
>     VE6SRV
>
>
>
>
> --
> Matthew
> VK5ZM
> 0487 653 245
>
>

Yes Scott, that is correct.

Thanks for the information - we will try that out as time permits.

73, Sion, 9M2CQC



On 16 Jan 2013, at 12:27 PM, Scott Miller <scott@...> wrote:

> To clarify, this is to support packets (digi'd or through KISS) used by
> connected mode applications, and is *not* a connected mode AX.25 stack
> in itself.
>
> The most important thing I found is that some very small packets were
> getting dropped as invalid.  No APRS packet would be that small, so it
> hadn't turned up in APRS operation.  It shouldn't affect digi operation,
> though, because the presence of a digi path would make it larger than
> that threshold.
>
> Scott
>
> On 1/15/2013 6:48 PM, Sion Chow Q. C. (9W2QC) wrote:
>> Scott,
>>
>> This is the T2 firmware to support connected mode packets? I would
>> not mind testing, but let me see if I have a spare T2 to do this
>> first. Another one has been sent for packaging for another hill top
>> digi.
>>
>> Has there been any previous success getting connected packets digied
>> via the T2 in the past?
>>
>> 73, Sion, 9M2CQC
>>
>> Quoting Scott Miller scott@... <mailto:scott%40opentrac.org>>:
>>
>>> Hi,
>>>
>>> I've been doing a lot of testing with the T3 lately for connected mode
>>> use, and there are a couple of easy tweaks I can back-port to the T2.
>>> If you've got a setup you'd like to test (that you can access easily to
>>> update) let me know and I'll send you a new firmware version.
>>>
>>> Scott
>>>
>>> On 1/15/2013 5:58 PM, Sion Chow Q. C. (9W2QC) wrote:
>>>> Dear All,
>>>>
>>>> We are using 2 units of T2s as mountain top WIDE digipeaters for 2M
>>>> and 70cm. As we are seeing very low usage on the 70cm side, we would
>>>> like to add some other packet services such as BBS and/or Winlink.
>>>>
>>>> I understand this has been asked before, but I like to get a final
>>>> confirmation whether the T2 can support digipeating of BBS and/or
>>>> Winlink packets? I have tried looking around and I see that the T2
>>>> does not support Winlink when connected to a host computer, but am not
>>>> sure if this would work as a digipeater.
>>>>
>>>> Thank you.
>>>>
>>>> 73,
>>>> Sion Chow Q. C.,
>>>> 9M2CQC, WQ2C
>>>>
>>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Okay, so like a dummy I read the pin numbers on the connector wrong....

So my problem now is I somehow have the TNC in a mode whereby when I try to
access the TNC using the USB port, it sends messages with my callsign and some
random text (actually transmits).

It is like I have the USB in "converse" mode, and I can't seem to get it out.

I have tried talking to the TNC using WINOTCFG through serial port A and USB,
and it is not talking, just causing a lot of TX's flooding my local airwaves
with garbage....

Are the USB and Port A settings combined somehow? It seems that if I set the
serial port configuration for Port A, the USB port seems to follow.

Dave Cameron

--- In tracker2@yahoogroups.com, Scott Miller  wrote:
>
> > 1) Which serial port (A or B) in OTWINCFG is the rear connector?
>
> Rear connector is port A.  Front (normally input-only on the 135) is B.
>
> > 2) What do the TXD and RXD pins that are routed to the Alinco
> > motherboard do? Can they also be used for control/KISS?
>
> The RXD line comes from the data jack on the front of the radio when
> it's in data mode.  Maybe it's possible to talk to the radio's MCU as
> well, never really spent any time trying to figure that out.  I suspect
> that connection is disabled in data mode, but I'm not certain.  Not
> relevant for your application, anyway.  The port is fully functional, so
> you can use it for any port B mode.
>
> > 3) Can the unit be configured through one of its serial ports instead of
> > through USB?
>
> Yes, but only port A.
>
> You might also be interested in the embeddable module version of the
> OTUSB/T3 I'm testing now.  The first board rev had some glitches but is
> usable with a jumper.  It's smaller than the T3-135 and includes a
> regulator and a bunch of I/Os.  I just redesigned it to fit all of the
> components on one side of the board and to make room for optional screw
> terminal blocks.  Hadn't thought of that originally but my son swiped
> one of the prototypes to use as a USB keyboard emulator for his arcade
> cabinet project and that configuration worked out nicely.  I'll have the
> new board rev in a couple of weeks.
>
> A new rev of the T3-135 is off to the board house for prototyping within
> the hour.  This one just fixes a couple of glitches, changes the
> connector orientation, and shrinks the board by about 20%.
>
> Scott
>

The message it is sending is

$~R/*reset*~R

It transmits this out as a message over and over and over again. But the TNC is
not listening it appears, because it never goes into configuration mode.

Any ideas?

Dave

--- In tracker2@yahoogroups.com, "ve7ltd"  wrote:
>
> Okay, so like a dummy I read the pin numbers on the connector wrong....
>
> So my problem now is I somehow have the TNC in a mode whereby when I try to
access the TNC using the USB port, it sends messages with my callsign and some
random text (actually transmits).
>
> It is like I have the USB in "converse" mode, and I can't seem to get it out.
>
> I have tried talking to the TNC using WINOTCFG through serial port A and USB,
and it is not talking, just causing a lot of TX's flooding my local airwaves
with garbage....
>
> Are the USB and Port A settings combined somehow? It seems that if I set the
serial port configuration for Port A, the USB port seems to follow.
>
> Dave Cameron
>
> --- In tracker2@yahoogroups.com, Scott Miller  wrote:
> >
> > > 1) Which serial port (A or B) in OTWINCFG is the rear connector?
> >
> > Rear connector is port A.  Front (normally input-only on the 135) is B.
> >
> > > 2) What do the TXD and RXD pins that are routed to the Alinco
> > > motherboard do? Can they also be used for control/KISS?
> >
> > The RXD line comes from the data jack on the front of the radio when
> > it's in data mode.  Maybe it's possible to talk to the radio's MCU as
> > well, never really spent any time trying to figure that out.  I suspect
> > that connection is disabled in data mode, but I'm not certain.  Not
> > relevant for your application, anyway.  The port is fully functional, so
> > you can use it for any port B mode.
> >
> > > 3) Can the unit be configured through one of its serial ports instead of
> > > through USB?
> >
> > Yes, but only port A.
> >
> > You might also be interested in the embeddable module version of the
> > OTUSB/T3 I'm testing now.  The first board rev had some glitches but is
> > usable with a jumper.  It's smaller than the T3-135 and includes a
> > regulator and a bunch of I/Os.  I just redesigned it to fit all of the
> > components on one side of the board and to make room for optional screw
> > terminal blocks.  Hadn't thought of that originally but my son swiped
> > one of the prototypes to use as a USB keyboard emulator for his arcade
> > cabinet project and that configuration worked out nicely.  I'll have the
> > new board rev in a couple of weeks.
> >
> > A new rev of the T3-135 is off to the board house for prototyping within
> > the hour.  This one just fixes a couple of glitches, changes the
> > connector orientation, and shrinks the board by about 20%.
> >
> > Scott
> >
>

I think I am getting somewhere - So if I plug the USB into my linux computer and
read /dev/ttyACM0 at 9600 baud, I can see the data from the channel coming
across, and I can see that the USB port is in CONVERSE mode.

So I press CTRL-C and I get a cmd: prompt. Multiple CTRL-Cs just return more
cmd: prompts. But anything I type at that prompt is just send out the TNC in
converse mode again. It appears that my TNC is stuck in converse mode, and I
can't get it out. Attempts to connect to OTWINCFG either through serial port A
or USB always end up in the word $~R/*reset*~R being send out of the TNC in
converse mode.

I really wish I could find a way to get this thing to go back into OTWINCFG so I
could reflash and start fresh.

help?

--- In tracker2@yahoogroups.com, "ve7ltd"  wrote:
>
> The message it is sending is
>
> $~R/*reset*~R
>
> It transmits this out as a message over and over and over again. But the TNC
is not listening it appears, because it never goes into configuration mode.
>
> Any ideas?
>
> Dave
>
> --- In tracker2@yahoogroups.com, "ve7ltd"  wrote:
> >
> > Okay, so like a dummy I read the pin numbers on the connector wrong....
> >
> > So my problem now is I somehow have the TNC in a mode whereby when I try to
access the TNC using the USB port, it sends messages with my callsign and some
random text (actually transmits).
> >
> > It is like I have the USB in "converse" mode, and I can't seem to get it
out.
> >
> > I have tried talking to the TNC using WINOTCFG through serial port A and
USB, and it is not talking, just causing a lot of TX's flooding my local
airwaves with garbage....
> >
> > Are the USB and Port A settings combined somehow? It seems that if I set the
serial port configuration for Port A, the USB port seems to follow.
> >
> > Dave Cameron
> >
> > --- In tracker2@yahoogroups.com, Scott Miller  wrote:
> > >
> > > > 1) Which serial port (A or B) in OTWINCFG is the rear connector?
> > >
> > > Rear connector is port A.  Front (normally input-only on the 135) is B.
> > >
> > > > 2) What do the TXD and RXD pins that are routed to the Alinco
> > > > motherboard do? Can they also be used for control/KISS?
> > >
> > > The RXD line comes from the data jack on the front of the radio when
> > > it's in data mode.  Maybe it's possible to talk to the radio's MCU as
> > > well, never really spent any time trying to figure that out.  I suspect
> > > that connection is disabled in data mode, but I'm not certain.  Not
> > > relevant for your application, anyway.  The port is fully functional, so
> > > you can use it for any port B mode.
> > >
> > > > 3) Can the unit be configured through one of its serial ports instead of
> > > > through USB?
> > >
> > > Yes, but only port A.
> > >
> > > You might also be interested in the embeddable module version of the
> > > OTUSB/T3 I'm testing now.  The first board rev had some glitches but is
> > > usable with a jumper.  It's smaller than the T3-135 and includes a
> > > regulator and a bunch of I/Os.  I just redesigned it to fit all of the
> > > components on one side of the board and to make room for optional screw
> > > terminal blocks.  Hadn't thought of that originally but my son swiped
> > > one of the prototypes to use as a USB keyboard emulator for his arcade
> > > cabinet project and that configuration worked out nicely.  I'll have the
> > > new board rev in a couple of weeks.
> > >
> > > A new rev of the T3-135 is off to the board house for prototyping within
> > > the hour.  This one just fixes a couple of glitches, changes the
> > > connector orientation, and shrinks the board by about 20%.
> > >
> > > Scott
> > >
> >
>

They're not linked, but the console will only work on one at a time,
with preference for USB.  Port A could be stuck in TEXT mode, but that's
not an option for the USB port.  If it's in KISS mode, a bunch of
control-C's should fix it.  TEXT mode too, if you've got the recent beta
firmware.

And you should always be able to get into otwincfg on the serial port
from a cold start.

Don't feel bad about reading the pin numbers backwards, the connector
wound up backwards on the T3-135, the same mistake I made and later
fixed on the T2-135.  I think the library part was numbered backwards or
something.  The fix was easy enough, just mount the connector on the
other side of the board.

Scott

On 1/17/2013 11:05 PM, ve7ltd wrote:
> Okay, so like a dummy I read the pin numbers on the connector wrong....
>
> So my problem now is I somehow have the TNC in a mode whereby when I try
> to access the TNC using the USB port, it sends messages with my callsign
> and some random text (actually transmits).
>
> It is like I have the USB in "converse" mode, and I can't seem to get it
> out.
>
> I have tried talking to the TNC using WINOTCFG through serial port A and
> USB, and it is not talking, just causing a lot of TX's flooding my local
> airwaves with garbage....
>
> Are the USB and Port A settings combined somehow? It seems that if I set
> the serial port configuration for Port A, the USB port seems to follow.
>
> Dave Cameron
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> Scott Miller wrote:
>  >
>  > > 1) Which serial port (A or B) in OTWINCFG is the rear connector?
>  >
>  > Rear connector is port A. Front (normally input-only on the 135) is B.
>  >
>  > > 2) What do the TXD and RXD pins that are routed to the Alinco
>  > > motherboard do? Can they also be used for control/KISS?
>  >
>  > The RXD line comes from the data jack on the front of the radio when
>  > it's in data mode. Maybe it's possible to talk to the radio's MCU as
>  > well, never really spent any time trying to figure that out. I suspect
>  > that connection is disabled in data mode, but I'm not certain. Not
>  > relevant for your application, anyway. The port is fully functional, so
>  > you can use it for any port B mode.
>  >
>  > > 3) Can the unit be configured through one of its serial ports
> instead of
>  > > through USB?
>  >
>  > Yes, but only port A.
>  >
>  > You might also be interested in the embeddable module version of the
>  > OTUSB/T3 I'm testing now. The first board rev had some glitches but is
>  > usable with a jumper. It's smaller than the T3-135 and includes a
>  > regulator and a bunch of I/Os. I just redesigned it to fit all of the
>  > components on one side of the board and to make room for optional screw
>  > terminal blocks. Hadn't thought of that originally but my son swiped
>  > one of the prototypes to use as a USB keyboard emulator for his arcade
>  > cabinet project and that configuration worked out nicely. I'll have the
>  > new board rev in a couple of weeks.
>  >
>  > A new rev of the T3-135 is off to the board house for prototyping within
>  > the hour. This one just fixes a couple of glitches, changes the
>  > connector orientation, and shrinks the board by about 20%.
>  >
>  > Scott
>  >
>
>

Is that on the serial port or USB?

Scott

On 1/17/2013 11:15 PM, ve7ltd wrote:
> The message it is sending is
>
> $~R/*reset*~R
>
> It transmits this out as a message over and over and over again. But the
> TNC is not listening it appears, because it never goes into
> configuration mode.
>
> Any ideas?
>
> Dave
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> "ve7ltd" wrote:
>  >
>  > Okay, so like a dummy I read the pin numbers on the connector wrong....
>  >
>  > So my problem now is I somehow have the TNC in a mode whereby when I
> try to access the TNC using the USB port, it sends messages with my
> callsign and some random text (actually transmits).
>  >
>  > It is like I have the USB in "converse" mode, and I can't seem to get
> it out.
>  >
>  > I have tried talking to the TNC using WINOTCFG through serial port A
> and USB, and it is not talking, just causing a lot of TX's flooding my
> local airwaves with garbage....
>  >
>  > Are the USB and Port A settings combined somehow? It seems that if I
> set the serial port configuration for Port A, the USB port seems to follow.
>  >
>  > Dave Cameron
>  >
>  > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> Scott Miller wrote:
>  > >
>  > > > 1) Which serial port (A or B) in OTWINCFG is the rear connector?
>  > >
>  > > Rear connector is port A. Front (normally input-only on the 135) is B.
>  > >
>  > > > 2) What do the TXD and RXD pins that are routed to the Alinco
>  > > > motherboard do? Can they also be used for control/KISS?
>  > >
>  > > The RXD line comes from the data jack on the front of the radio when
>  > > it's in data mode. Maybe it's possible to talk to the radio's MCU as
>  > > well, never really spent any time trying to figure that out. I suspect
>  > > that connection is disabled in data mode, but I'm not certain. Not
>  > > relevant for your application, anyway. The port is fully
> functional, so
>  > > you can use it for any port B mode.
>  > >
>  > > > 3) Can the unit be configured through one of its serial ports
> instead of
>  > > > through USB?
>  > >
>  > > Yes, but only port A.
>  > >
>  > > You might also be interested in the embeddable module version of the
>  > > OTUSB/T3 I'm testing now. The first board rev had some glitches but is
>  > > usable with a jumper. It's smaller than the T3-135 and includes a
>  > > regulator and a bunch of I/Os. I just redesigned it to fit all of the
>  > > components on one side of the board and to make room for optional
> screw
>  > > terminal blocks. Hadn't thought of that originally but my son swiped
>  > > one of the prototypes to use as a USB keyboard emulator for his arcade
>  > > cabinet project and that configuration worked out nicely. I'll have
> the
>  > > new board rev in a couple of weeks.
>  > >
>  > > A new rev of the T3-135 is off to the board house for prototyping
> within
>  > > the hour. This one just fixes a couple of glitches, changes the
>  > > connector orientation, and shrinks the board by about 20%.
>  > >
>  > > Scott
>  > >
>  >
>
>

The USB port should never be stuck in converse mode - it doesn't have
TEXT mode as an option.

Try a cold boot on port A.  It'll try to talk to otwincfg before it even
loads the configuration.

Scott

On 1/17/2013 11:58 PM, ve7ltd wrote:
> I think I am getting somewhere - So if I plug the USB into my linux
> computer and read /dev/ttyACM0 at 9600 baud, I can see the data from the
> channel coming across, and I can see that the USB port is in CONVERSE mode.
>
> So I press CTRL-C and I get a cmd: prompt. Multiple CTRL-Cs just return
> more cmd: prompts. But anything I type at that prompt is just send out
> the TNC in converse mode again. It appears that my TNC is stuck in
> converse mode, and I can't get it out. Attempts to connect to OTWINCFG
> either through serial port A or USB always end up in the word
> $~R/*reset*~R being send out of the TNC in converse mode.
>
> I really wish I could find a way to get this thing to go back into
> OTWINCFG so I could reflash and start fresh.
>
> help?
>
> --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> "ve7ltd" wrote:
>  >
>  > The message it is sending is
>  >
>  > $~R/*reset*~R
>  >
>  > It transmits this out as a message over and over and over again. But
> the TNC is not listening it appears, because it never goes into
> configuration mode.
>  >
>  > Any ideas?
>  >
>  > Dave
>  >
>  > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
> "ve7ltd" wrote:
>  > >
>  > > Okay, so like a dummy I read the pin numbers on the connector wrong....
>  > >
>  > > So my problem now is I somehow have the TNC in a mode whereby when
> I try to access the TNC using the USB port, it sends messages with my
> callsign and some random text (actually transmits).
>  > >
>  > > It is like I have the USB in "converse" mode, and I can't seem to
> get it out.
>  > >
>  > > I have tried talking to the TNC using WINOTCFG through serial port
> A and USB, and it is not talking, just causing a lot of TX's flooding my
> local airwaves with garbage....
>  > >
>  > > Are the USB and Port A settings combined somehow? It seems that if
> I set the serial port configuration for Port A, the USB port seems to
> follow.
>  > >
>  > > Dave Cameron
>  > >
>  > > --- In tracker2@yahoogroups.com
> <mailto:tracker2%40yahoogroups.com>, Scott Miller wrote:
>  > > >
>  > > > > 1) Which serial port (A or B) in OTWINCFG is the rear connector?
>  > > >
>  > > > Rear connector is port A. Front (normally input-only on the 135)
> is B.
>  > > >
>  > > > > 2) What do the TXD and RXD pins that are routed to the Alinco
>  > > > > motherboard do? Can they also be used for control/KISS?
>  > > >
>  > > > The RXD line comes from the data jack on the front of the radio when
>  > > > it's in data mode. Maybe it's possible to talk to the radio's MCU as
>  > > > well, never really spent any time trying to figure that out. I
> suspect
>  > > > that connection is disabled in data mode, but I'm not certain. Not
>  > > > relevant for your application, anyway. The port is fully
> functional, so
>  > > > you can use it for any port B mode.
>  > > >
>  > > > > 3) Can the unit be configured through one of its serial ports
> instead of
>  > > > > through USB?
>  > > >
>  > > > Yes, but only port A.
>  > > >
>  > > > You might also be interested in the embeddable module version of the
>  > > > OTUSB/T3 I'm testing now. The first board rev had some glitches
> but is
>  > > > usable with a jumper. It's smaller than the T3-135 and includes a
>  > > > regulator and a bunch of I/Os. I just redesigned it to fit all of
> the
>  > > > components on one side of the board and to make room for optional
> screw
>  > > > terminal blocks. Hadn't thought of that originally but my son swiped
>  > > > one of the prototypes to use as a USB keyboard emulator for his
> arcade
>  > > > cabinet project and that configuration worked out nicely. I'll
> have the
>  > > > new board rev in a couple of weeks.
>  > > >
>  > > > A new rev of the T3-135 is off to the board house for prototyping
> within
>  > > > the hour. This one just fixes a couple of glitches, changes the
>  > > > connector orientation, and shrinks the board by about 20%.
>  > > >
>  > > > Scott
>  > > >
>  > >
>  >
>
>

We may have something to go on here.

I created a group photo album called "OT2m Poison Packets"
You must view these pictures at original size to read them...


There is a pic of the frozen OT2m LCD screen showing a packet from K0HAX with a
bogus distance of 6316 miles. (OT2m HUD.png)

I looked at my aprs station data in APRS.fi and my last position packet was
2013-01-18 @ 00:56:34  (k0jdd.png)

I looked at the k0hax aprs station data for around that time and there is a
packet with bad mic-e data on 2013-01-18 @ 01:04:13 (k0hax.png)

I am working on capturing a DUMP - got to find the serial adapter and get the PC
booted up.  Might be Saturday morning.  I will email it to Scott asap.

Good work, that's definitely something I can use.  And if you manage to
get a dump, that would be wonderful.  Also the INFO command output, and
whether or not the RX LED is responding.

I've looked at the code again and nothing immediately jumps out at me.
Most of the heavy lifting is done before the packet gets displayed on
the LCD.  There are plenty of opportunities for mangled packets to get
crazy values, and this one looks like it did, but it also made it
through all of the parsing (short of the waypoint output) and it should
be almost ready to be discarded from the packet queue.

*Most* of the time a major failure will cause an (almost) immediate
reset due to an invalid instruction or watchdog timeout.  It's still
possible to get it stuck in a loop if it happens in just the right
place, and if the unit is still responding then it means something more
subtle is going wrong, like the packet buffer somehow becoming so
corrupted it can't process anything.

Scott

On 1/18/2013 8:06 PM, JohnD wrote:
>
>
> We may have something to go on here.
>
> I created a group photo album called "OT2m Poison Packets"
> You must view these pictures at original size to read them...
>
> There is a pic of the frozen OT2m LCD screen showing a packet from K0HAX
> with a bogus distance of 6316 miles. (OT2m HUD.png)
>
> I looked at my aprs station data in APRS.fi and my last position packet
> was 2013-01-18 @ 00:56:34 (k0jdd.png)
>
> I looked at the k0hax aprs station data for around that time and there
> is a packet with bad mic-e data on 2013-01-18 @ 01:04:13 (k0hax.png)
>
> I am working on capturing a DUMP - got to find the serial adapter and
> get the PC booted up. Might be Saturday morning. I will email it to
> Scott asap.
>
>

The RCV light was still responding whenever the APRS radio was receiving.

As I was trying to plug in the serial cable the unit reset.  :-(
I had to do it blind, and I probably shorted a few pins in the DB9 socket. I
left the cable attached... I will get a DUMP when it happens again.


BTW - do you want DUMP or DUMP ALL along with INFO?

I had built a cable for my tracker a while back but I found out about the ot3m
-- bought it and ready to get it up and running !!

I had built it for my htx 242 based off the byonics m7p cable --
http://www.byonics.com/cables/m7p.png

It has pin 7 12v and pin 6 as ground -- will this cause any issues when I plug
it into the ot3m or should I take those pins out of my connector

Here is what I built
http://i1353.photobucket.com/albums/q661/kj4vyi/A13107B2-E01D-4162-952D-AC86468F\
F739-10065-0000011D334AD3F1_zps9db687f7.jpg

http://i1353.photobucket.com/albums/q661/kj4vyi/2127185D-85D8-434F-8D63-D8ABA989\
84B3-10065-0000011D3130064A_zps8a3bfffc.jpg

I added power poles to the serial side and the rj45 side du to the radio being
installed in the back of the truck and the ot3m in the front of the truck --
used a cat6 cable will be connected to the nuvi350 with the fmi cable

Any issues y'all could think of by leaving the pin 6 & pin 7 in -- can you power
the ot3m that way or not -- I skimmed the manual for an answer but I think I'll
skim again

Thanks

Chad
Kj4vyi

That is weird - Port A and the USB were linked. If I typed letters on the USB
through the linux console on /dev/ttyACM0 at 9600 baud, I read them on the
serial port connected to port A at 9600 baud.

I can't seem to get it out of TEXT mode. I have moved onto T3-135 number 2 :)

The USB was definitely in text mode - Hooked at 9600 baud, everything I typed
went straight out the air via the TNC.

Is there any way to hold a pin to ground to force a base configuration? I think
I have tried everything to get this thing to read in OTWINCFG.

Will leave it for a few days and see where I get.

Dave


--- In tracker2@yahoogroups.com, Scott Miller  wrote:
>
> They're not linked, but the console will only work on one at a time,
> with preference for USB.  Port A could be stuck in TEXT mode, but that's
> not an option for the USB port.  If it's in KISS mode, a bunch of
> control-C's should fix it.  TEXT mode too, if you've got the recent beta
> firmware.
>
> And you should always be able to get into otwincfg on the serial port
> from a cold start.
>
> Don't feel bad about reading the pin numbers backwards, the connector
> wound up backwards on the T3-135, the same mistake I made and later
> fixed on the T2-135.  I think the library part was numbered backwards or
> something.  The fix was easy enough, just mount the connector on the
> other side of the board.
>
> Scott
>
> On 1/17/2013 11:05 PM, ve7ltd wrote:
> > Okay, so like a dummy I read the pin numbers on the connector wrong....
> >
> > So my problem now is I somehow have the TNC in a mode whereby when I try
> > to access the TNC using the USB port, it sends messages with my callsign
> > and some random text (actually transmits).
> >
> > It is like I have the USB in "converse" mode, and I can't seem to get it
> > out.
> >
> > I have tried talking to the TNC using WINOTCFG through serial port A and
> > USB, and it is not talking, just causing a lot of TX's flooding my local
> > airwaves with garbage....
> >
> > Are the USB and Port A settings combined somehow? It seems that if I set
> > the serial port configuration for Port A, the USB port seems to follow.
> >
> > Dave Cameron
> >
> > --- In tracker2@yahoogroups.com ,
> > Scott Miller wrote:
> >  >
> >  > > 1) Which serial port (A or B) in OTWINCFG is the rear connector?
> >  >
> >  > Rear connector is port A. Front (normally input-only on the 135) is B.
> >  >
> >  > > 2) What do the TXD and RXD pins that are routed to the Alinco
> >  > > motherboard do? Can they also be used for control/KISS?
> >  >
> >  > The RXD line comes from the data jack on the front of the radio when
> >  > it's in data mode. Maybe it's possible to talk to the radio's MCU as
> >  > well, never really spent any time trying to figure that out. I suspect
> >  > that connection is disabled in data mode, but I'm not certain. Not
> >  > relevant for your application, anyway. The port is fully functional, so
> >  > you can use it for any port B mode.
> >  >
> >  > > 3) Can the unit be configured through one of its serial ports
> > instead of
> >  > > through USB?
> >  >
> >  > Yes, but only port A.
> >  >
> >  > You might also be interested in the embeddable module version of the
> >  > OTUSB/T3 I'm testing now. The first board rev had some glitches but is
> >  > usable with a jumper. It's smaller than the T3-135 and includes a
> >  > regulator and a bunch of I/Os. I just redesigned it to fit all of the
> >  > components on one side of the board and to make room for optional screw
> >  > terminal blocks. Hadn't thought of that originally but my son swiped
> >  > one of the prototypes to use as a USB keyboard emulator for his arcade
> >  > cabinet project and that configuration worked out nicely. I'll have the
> >  > new board rev in a couple of weeks.
> >  >
> >  > A new rev of the T3-135 is off to the board house for prototyping within
> >  > the hour. This one just fixes a couple of glitches, changes the
> >  > connector orientation, and shrinks the board by about 20%.
> >  >
> >  > Scott
> >  >
> >
> >
>

I'm unable to install the latest (beta) firmware, I get:

---------------------------
otwincfg
---------------------------
Verify error at block 0xde00
---------------------------
OK
---------------------------

---------------------------
otwincfg
---------------------------
Configuration write failed
---------------------------
OK
---------------------------


I've attempted updating from a local file as well as using the web update and
pointing it to the latest beta firmware.

Any ideas?  It's 100% consistent, I've pulled all other versions of
firmware and am able to successfully write everything but the latest
version.  I have an OTUSB.


Chris

On Thu, Jan 3, 2013 at 12:23 AM, Scott Miller  wrote:

> **
>
>
> > Is this on SVN or somewhere else?
>
> Otwincfg 'web' option. Just posted the new manual update, too. I'll
> update the static links on the site once the new versions are out of beta.
>
>
> > In searching for a copy of the new OTWINCFG, I found there are at
> > least two pointers to OTWINCFG.
> >
> > http://wiki.argentdata.com/index.php?title=OTWINCFG points to
> > http://www.argentdata.com/support/firmware/otwincfg.exe which appears
> > to be n old version.
>
> This should be current. I uploaded a new version today that adds
> 'Result' to the B counter list. The bad links were a result of a site
> reorganization - I missed some relative links that needed to be updated.
> I think I've got them all now.
>
> Next I've got to revisit the OTUSB manual and sync it up with the T3
> manual.
>
> Be sure to ping me if there's anything missing from the site or user's
> manual - I'm making a concerted effort to get all of the documentation
> cleaned up, remove some duplication, and generally make sure you can
> find everything you need regardless of where you come in to the site from.
>
> Scott
>
>
>