Jolly good.
On todays's 250 mile jolly around 7 passes, my Nav V and my chum's 590 both failed at exactly the same points, multiple times. The only way to force the two devices to locate satellites was to stop the route, turn the devices off and restart. Both devices functioned quite normally at first. They then both started to act up in parallel, losing their satellite connections and being completely unable to display the bikes' correct positions. At one point we were most definitely hooning up the Susten Pass, with the device displaying the bike hurtling up the A2 motorway. At another point, we were hurtling down the Furka Pass, with the device displaying a bike apparently hurtling across fields or (I guess) fresh air.
The trip log, which I have kept, makes interesting viewing, stopping and starting each time the devices lost their satellite connections. The 250 mile route breaks up into no less than 45 segments, the longest of which is 28 miles, coinciding exactly with the uninterrupted travel we enjoyed when first setting off. When the devices performed properly, the track log shows the normal wiggly lines, broadly inline with the route; exactly as you would expect. When the devices were unable to locate any satellites at all, the track lines are dead straight (as you would expect) sometimes miles removed from the bike's actual position. They will then jump into the correct location, when the satellite reconnection is made. Overlaying the route ridden with the track makes amusing viewing.
Other amusing bi-products were:
The device becoming so engrossed with hunting satellites and / or displaying the position to be in a river or on the top of a mountain, that it thought it was dark, so switched to its night time screen, basically mostly blacked out. The only way to turn it back to daytime was to stop, turn off the device and reboot it.
I have my device set to 'prompted recalculate' yes or no. God knows what would have happened had it been on auto-recalculate. The device froze several times, touching 'No' having no effect.
So, to summarise: That is two broadly similar up-to-date Garmin devices, both running identical routes, both failing at the same multiple points, with the same cause and the same end effect. I have a second Nav V with me, so I'll try that one, too.
PS Both devices had performed faultlessly on the ride down from Calais to Interlaken. Mine had been as good as gold in the Ardennes, the week before. Give them uninterrupted clear satellite views and all is well. Name the satellite connection a bit hooky and the wheels start to come off....
As you say, take a map as a back up, and keep calm.
