Re: [tracker2] Re: Firmware update
- No, FMI shouldn't have broken anything - worst case, it might confuse
some non-FMI Garmin receivers, but not if they behave like they're
supposed to. I didn't take out any other functions, either. Proto C
should work fine.
Maybe next time I'll go to a switching regulator - they've got some out
now that'll switch to LDO mode under low loads, so I guess it's the best
of both worlds. (Switching noise AND sensitivity to capacitor ESR! =])
> I'm not sure whether you stated previously if adding the FMI code
> affected any other OT2 functions. I loaded the beta version in OT2s
> inluding the ProtoC and used them with the GPSMAP60 as well as the
> Nuvi and did not notice any effects. Was anything dropped when the
> FMI code was added? Are there any issues we need to be aware of
> when we use it with a ProtoC or earlier?
> As a quick warning, I might mention I made up a cable similar to the
> one described by Joe,W0PWJ, and reaffirm his disclaimer. Using one
> might be detrimental to the health of an OT2m using the 78M05.
> Charging currents for the Nuvi with a low battery can exceed 300mA.
> I used a ProtoC with the bigger 78T05 and it got fairly warm. Will
> do a post when I get some more results.
> Graham VE6GW
> --- In email@example.com <mailto:tracker2%40yahoogroups.com>,
> Scott Miller <scott@...> wrote:
> > I promised a firmware update yesterday, but I got into the FMI
> code and
> > started running into problems. I'm still working on tracking it
> > down, and I'm giving up for the night.
> > I've fixed a baud rate setting bug that's apparently been there
> > the beginning, but would only show up in certain specific
> > I also got it to ignore duplicate incoming messages that have
> > been received and ACK'd. This generally happens when the sending
> > didn't get the ACK. This applies to all incoming messages, and
> not just
> > FMI mode.
> > I've changed the command prefix for FMI messages from '!' to '--
> '. It's
> > a lot quicker to type on the Nuvi's on-screen keyboard.
> > I'll post the new firmware as soon as I get the Garmin comm bug
> > out. It's hard to tell if this was something that was there
> before and
> > it just wasn't obvious that it was missing some position packets,
> or if
> > I caused the bug with either the FMI code or the serial handler
> > Scott