I have a GPSMAP 295 and suspected it might have the same problem. I noticed
today that Garmin has added version 2.40 to their downloads page. The
description of the change from ver 2.30 to 2.40 reads, "Added processing to
detect the movement or deletion of any aviation database waypoint and update
all routes and goto history with the new data."
I attempted to download 2.40 but the link took me to 2.30. I called Garmin
tech support and spoke to Scott. He verified that the link to 2.40 actually
pointed to 2.30. He said he'd report the problem. It should be fixed today.
The new version 3.60 for the GPSMAP 196 has the same description and appears
to point to the correct update.
Jon
Cool, Jon, thanks for the notification! This newsgroup can take a lot of the
credit for getting this fixed. John Bell picked up my report on the newsgroup
and documented it in a way that Garmin couldn't ignore. Thanks to all who
contributed to this effort!
Dave
Remove SHIRT to reply directly.
"Jon Woellhaf" <jonwo...@comcast.net> wrote in message
news:0EMwb.303206$Tr4.959505@attbi_s03...
Yes, what you are missing is that there is a bug in the datbase updating
process, when a fix is moved between database updates, and the GPS receiver has
a stored route that contains that fix. Do a search at groups.google.com for "Who
moved SAV, forgot to tell Jepp?"
Remove SHIRT to reply directly.
Dave
> Yes, what you are missing is that there is a bug in the datbase updating
> process, when a fix is moved between database updates, and the GPS
> receiver has a stored route that contains that fix. Do a search at
> groups.google.com for "Who moved SAV, forgot to tell Jepp?"
Hmm. I hope that they flag flight plans altered by moving waypoints. It
could render a flight plan "wrong" from the pilot's perspective...or at
least cause one to consider using a different waypoint.
Yes, one would pick that up when loading the flight plan. But it would be
nice to have a list of impacted flight plans ahead of time.
- Andrew