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

13885Re: [tracker2] Re: T3-135 Alinco Board not responding

Expand Messages
  • Scott Miller
    Apr 6, 2012
    • 1 Attachment
    • 38 KB
    Sure, let's see if it comes through as an attachment...

    Scott

    On 4/6/2012 2:17 PM, Ron N9SZV wrote:
    > Mine seems to still be working ...but is there any way you can post a
    > photo of where the trace is and where to cut it?
    >
    > Ron N9SZV
    >
    > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>,
    > Scott Miller <scott@...> wrote:
    > >
    > > Ok, got the first return back today and I think I have an answer.
    > >
    > > The returned unit had a blank firmware block that was causing the
    > > constant malfunction, but that's a symptom, not the root cause.
    > >
    > > It looks like the real problem is that in adapting the T3 to the 135
    > > board layout the transmit-now input got assigned to the wrong pin on the
    > > connector. When you plug a serial cable in, it can cause erratic
    > > operation. It seems likely that in this case it caused a failure during
    > > the firmware update attempt.
    > >
    > > So why wasn't this caught in testing? We've got one Alinco DR-135T
    > > that's permanently at the test bench for testing and development
    > > purposes, and it's been plugged and unplugged so many times that one
    > > wire on the connector failed. It looks like the failed cable kept the
    > > problem from popping up here.
    > >
    > > The quick fix is to cut the trace that leads from pin 2 of U3. On the
    > > top side of the board, this trace ends in a via near U1.
    > >
    > > The next board rev will correct the pin assignment, and I'm planning to
    > > put a solder jumper inline to make sure it's unconnected by default.
    > > The input is only needed if you want to wire up an external transmit-now
    > > (or counter) switch and it should be protected from accidental exposure
    > > to RS-232 voltage levels.
    > >
    > > If you have a T3-135 and don't want to cut the trace yourself, contact
    > > me off-list for an RMA and we'll send a return shipping label if you're
    > > in the US.
    > >
    > > Scott
    > >
    > > On 4/6/2012 6:55 AM, wilson.darcy@... wrote:
    > > > Ok, my thread has bounced around a bit...
    > > >
    > > > This particular case appears to have been operator error.
    > > >
    > > > My unit is DOA. No communication via rs232 or USB.
    > > >
    > > > --- In tracker2@yahoogroups.com <mailto:tracker2%40yahoogroups.com>
    > <mailto:tracker2%40yahoogroups.com>,
    > > > "Ron N9SZV" <n9szv@> wrote:
    > > > >
    > > > > update, I used the OTWinCfg software:
    > > > > http://www.argentdata.com/support/otplus.html
    > > > >
    > > > > It to a bit for it to connect to my T3-135 TNC com port it kept
    > > > transmitting on and off and then the config page came up I had to
    > add my
    > > > location..call...change A to 9600 and mode to Kiss clicked on write to
    > > > TNC. I then started Lynn's APRSIS32 program up and it started to
    > work it
    > > > is Digi and sending all my beacons out!! Will keep running let
    > every one
    > > > know if it stays working
    > > > >
    > > > > Ron N9SZV
    > > > >
    > > >
    > > >
    > >
    >
    >
  • Show all 30 messages in this topic