Nuvi 760 - Trip Information Screen

You must be going faster and farther than you think...Glad it is working ok now...I have a 750 and it seems to work fine.

I've seen those symptoms too - my 760 is 3 days old.

I've also had the Traffic Service warn me of delays 19,000 miles away

Garmin firmware that starts with a "2" is not good - roll on V3!

This has occured on my 750 also the last time was this weekend and it occured after a rare lockup of the unit that required a restart. I will download the track and edit this post with the results later.

edit: Just checked the track for this weekend and there was no sudden 1400 mile jump in the trip. So it's just another glitch that will either be addressed later or will be ignored.

Yes, I notices that, too. I want to be on the trips and vacations my 760 has been on. It seems this happened when I updated to 2.7.

Atleast the GPSr is giving plenty of advance warning for red light cameras. If you are traveling at over 1,200 MPH, it gives you over 15 hrs to prepare for the red light camera 19,000 miles away hahahaha.

Hope they fix this bug. Other than that, my 760 seems to be working just fine.

Well it's happened again. Three times in less than two weeks. I also had another strange event happen today as well. When I went to lunch today the GPS unit was showing me in an area of the city that I had never been in. It even had me in a lake at one point. I zoomed out until I recognized the area and realized that it was over 10 miles from where I currently was, and like I said in an area that I had never been in before. This may have been when the trip data gets corrupted. I didn’t think to check it until later. I had to turn the unit off and on to get it back to normal.

I have to say that although I do like my 760, it's much more unstable then my 650 was. I'm seriously thinking of returning it if things like this keep occurring.

Is it possible I have bad unit or is it more likely bugs in the latest firmware?

And I thought it was the last tuneup!

Personally, I'd suspect the latter. Mine did something similar yesterday (resulting in a max. speed of 712mph)

I have a 760 and it seems to work fine. I usually forget to reset prior to a trip and thus don't have complete trip data. The miles checks seem to be right on as is the speed. Sometimes I question the destination arrival time estimate.

Thinking about it, these strange deviations are probably recorded into the Trip Log. Maybe there's some evidence there worth passing on to Garmin.

I cleared mine out, 5 minutes before I thought of this

That's a good idea. Thanks, I'll pass that along with my support issue.

I just remembered that I'd backed up the whole Nüvi ... sure enough, it shows a load of gibberish when plotted in Mapsource.

The Vertical Profile is highly amusing - it shows me descending from 17500' @ 300mph...

http://geepeeex.googlepages.com/theManwhofelltoEarth.JPG

I think this Sirf InstantfixII technology may not be all it's cracked up to be!

Mine seemed to do it after I went to 2.7. Wonder if that is what is causing the fun? Not really sure. I don't use that part of the GPSr very often, but it is still funny to see I have gone over 300 MPH!
Guess I better not use that to show how fast I was going should I get pulled over!!!

For anyone interested...

Garmin support is recommending that I rollback to firmware version 2.6. They wouldn't come right out and admit that this is a bug but it seems pretty obvious. It does make me wonder though why more users aren't having the same issue. Is it possible that different units in the 7xx series use different components and that the latest firmware is buggy in just some units?

I just bought two 750's and am not having any problems so far with the 2.7 update. Everything seems to be fine in the Trip Info Screen...

Well I rolled back to 2.6 and thought everything was fixed, but this same problem happened again this weekend. It must be something with the unit itself. Garmin said to try the older firmware and if that didn't help to send it in. I'm still in my 30 day return window so I guess it would make more sense to just exchange it with the vendor instead.

The latest update addresses this issue.

Bill