Re: [tracker2] Re: Tracker 2- Nuvi 350- What do I need?
- A lot of effort is going into NOT splitting the T2 and T3 code, so that
the T2 will be continually updated for the foreseeable future rather
than putting it into maintenance mode and only getting infrequent bug
Regression testing still has to be done on all of the target devices
(the OTUSB also shares the same source code), which takes time. And the
nuvi ack bugs are notoriously inconsistent and dependent on quirks in
the nuvis themselves. The nuvi was never designed to send messages to
multiple destinations on an unreliable channel, which complicates the
user interface issues.
If you've got a setup where you're sure APRS messages are getting
through properly but the nuvi/T2 combo is consistently failing, I'd be
happy to involve you with the testing process.
On 4/21/2012 4:24 PM, Me wrote:
> I guess the large elephant in the room would be, why is Argent data
> spending so much time developing the Tracker 3 when the tracker 2
> doesn't even work properly yet? I am not trying to be a jackbutt, I am
> legitimately curious. Has Argent data given up on the tracker 2 in favor
> of the tracker 3, and therefore you do not want to waste time developing
> a product that is going to be phased out anyway?
> "If you're having consistent messaging problems on a T2, let me know and
> I'll get you an
> early copy of that firmware to try out."
> I'm sorry Scott, but this is frustrating. You know I've been having
> trouble with messaging.
> Over 16 months ago I posted this message:
> To which, you replied:
> > -----Original Message-----
> > From: Scott Miller <scott@...>
> > To: tracker2 <firstname.lastname@example.org
> > Sent: Sat, Dec 4, 2010 4:09 pm
> > Subject: Re: [tracker2] Messages not being awk'd?
> > Ok. I'm going to be spending some time nailing down what's going on
> > with the nuvi message acks. Doing it right means wiring up a
> > bidirectional tap to watch the FMI traffic and adapting my FMI test code
> > to show the packets going back and forth. I've already determined that
> > both the 350 and the 1300 can get into a mode (even when not navigating)
> > where they won't even attempt to send messages, and the 'sent' messages
> > disappear without going to the outbox.
> > Even if it's all Garmin bugs, I need to take some time to reproduce them
> > under controlled conditions so I can (hopefully) get Garmin to do
> > something about them.
> > Scott
> On three separate occasions, I have posted logs and asked the group for
> input, and it always starts with "It's Garmin's fault" and ends with a
> "I've got to do this .... and that...." and then nothing; no firmware
> updates, no progress, no correspondence. I know you know who I am...
> I've pestered you in emails offering to beta test for you, and the
> emails get no reply. I've finally reached a point where I'm willing to
> scratch my 1300's and go with 350's. Now I am told they too have a
> messaging issue. If I buy these cables, and the message awking bug still
> exists with the 350, I will not be a happy camper.
> I know you are under pressure, and there are deadlines with the T3...
> but business in ham radio is mostly word of mouth. Any previous
> commitments you've made to your existing customers need to take
> precedence over your new project. The time for empty promises is over my
> friend. I am willing to work with you and help you help me... but I've
> got over 16 months, and $1000 invested in this project, and it's about
> time you help me get two APRS stations that can reliably send a message
> to each other.
> I am eagerly awaiting your response....