Nuvi 52 Moving Average

[Jan Horn]

I noticed for the first time that the moving average on my Nuvi 52 is rather over optimistic. As can be seen in the screenshot the max speed was 144kmh and the moving avg 214kmh and all this in a Ford Fiesta. I have never reset the unit since I got it. It has recorded a total distance travelled as 2995 km and a moving time of 13:03. Doing the calculation the 214kmh is correct. The 2795km seem to be way off bearing in mind the trips I have done with the unit on so far. I have emailed Garmin let's see what they say?

[dasilvarsa]

Using the device in GPS Simulation mode can sometimes cause these artifacts.
Lets see what Garmin Says! I guess "Hard Reset".

[fugglefeet]

I have also seen this with my Nuvi 200 and Nuvi 2200, especially when you have switched of the unit and travelled a vast distance (around 400km) and then switched the device on to navigate. It seems to throw this anomaly.

Darryl

[Jan Horn]

I have seen it on the E Trex a few times specifically if you start driving when it has not picked up the satellites by the time you drive off. In this case I have only used it on long trips with no traveling in between. In retrospect the 2795 km travelled is correct but the traveling time is about half what it should be I would expect about 26 hours. I have updated the firmware about 3 or 4 times during the time,it could be that during one of the updates the traveling time was reset but not the rest of the data. I have done a reset of all the data and will keep an eye open and see what happen.

[fugglefeet]

I had a look now at my Nuvi 2200 to see if it has recently thrown the wobbly and I did see that my max speed was 198km/h. Now that I think about it, it's not impossible with my new toy, as this thing can go ...... very fast!!

Darryl

[Jan Horn]

Down loaded the trip logs total traveling time around 26 hours and the traveling distance around 2800km. Somewhere along the line the time got reset and the distance not.

[fugglefeet]

Possible software/firmware glitch that Garmin are still trying to sort out? Since you have raised it with Garmin, let's see what they say about it. I'm now just as curious.

Darryl

[Jan Horn]

A hard reset seem to have solved the problem