1747RE: [tracker2] T2-135 lessons being learned
- May 16, 2007The noise is apparently a design flaw in the DR-135 - it gets crosstalk from the data input to the speaker, regardless of the volume setting. You can stop it by installing a 3.5mm plug in the speaker jack to disable the internal speaker entirely.Scott
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Bruce W. Martin
Sent: Wednesday, May 16, 2007 7:43 AM
Subject: Re: [tracker2] T2-135 lessons being learned
I finally got around and put the radio back in the truck to test it out.
It powers up and I know the GPS is working and getting lock but the
tracker never transmits. It seems to be receiving.
Also, I notice that when the GPS is connected to the front GPS port
that there is a rhythmic noise coming from the speaker. If I disable
data or unplug the GPS it goes away. A different GPS plugged into the
DB9 on the back does not produce the noise.
I am heading for Dayton tomorrow morning and will bring it along.
On May 2, 2007, at 6:04 PM, Bruce W. Martin wrote:
> When I start it up I get both the red and green LEDs alternately
> flashing. If I start the config program and restart the radio/T2
> the Green LED is constant on and the program says:
> "Unsupported firmware version. Please upgrade configuration program.
> (ver 255 build 65535 target AP64-H)"
> I ran the downloaded the OT2.s19 firmware and ran the config
> program again replacing the firmware and it came right up.
> Mostly just reporting this so others can benefit from what I learned.
> thanks for your assistance.
> See you in Dayton.
> Bruce, KQ4TV
> On May 2, 2007, at 3:11 PM, scott@opentrac. org wrote:
>> If you open it up, you should see the LEDs blink at power-up.
>> They may be blinking constantly if the firmware is corrupted. As
>> long as it's still blinking, the config program should be able to
>> catch the bootloader and let you reload the firmware. You could
>> probably do it without the config program, too, but you'd probably
>> need to come up with a way to send the right byte sequence to
>> start the XMODEM download mode.
>> If it's not blinking at all, then it's possible the firmware got
>> wiped out completely. As far as I can remember, I've only had
>> that happen with overvoltage conditions, like 9 volts on the IRQ
>> pin. If it is totally blank, then you'll need to send it back for
>> I'll see if I can duplicate the problem myself. I might need to
>> set up the low-voltage inhibit on the processor.
>> From: Bruce W. Martin [mailto:yahoo@...]
>> To: OT2 [mailto:tracker2@yahoogroup s.com]
>> Sent: Wed, 02 May 2007 12:52:15 -0700
>> Subject: [tracker2] T2-135 lessons being learned
>> So, I got my T2-135 and installed it. Easy.
>> After a few hours of trying different serial cables and different
>> computers realized I needed to put the DR-135 in data mode to talk to
>> the T2.
>> Great! I can make changes with my Mac using Zterm or use the
>> latest OT
>> configuration program on Windows. I need to find something other than
>> minicom for Linux.
>> Hooked up the GPS and an antenna and it tracked great.
>> Wanted to see how long the tracker would last on low power with a
>> 3 year
>> old UPS 7AH battery. Not as long as I hoped. Set it up in the
>> truck as I
>> went to work. Left it running with smart beaconing at about 90
>> while moving slow. After work I found the radio power cycling. While
>> under load the battery would drop below some voltage threshold and
>> radio would turn off. Immediately the voltage would go up some now
>> there was no load and the radio would turn on. This cycle went on for
>> who knows how long. Probably a few hours.
>> Now I can't communicate with the T2-135. Have I killed it? Is there a
>> way I can get it back to default condition?
>> Bruce, KQ4TV
- << Previous post in topic Next post in topic >>