- Mar 18, 2015
- 432
- 1,242
- Funster No
- 35,485
- MH
- Summit Prime 640
- Exp
- Since 2014
We've just been to Ludlow (from Surrey) for a wet and windy New Year.
We opted for the Garmin Camper Sat Nav as you could programme in the MH size and add avoidances such as narrow lanes. We were therefore somewhat surprised on Wednesday that it routed us cross country taking almost a straight line route. One road it was telling us to use even had a "unsuitable for large vehicles" sign at the entrance. Fortunately the wife was quick with the road map and re-routed us where we'd expected to go.
It tried the same thing coming home today told us to turn left out of the site, then first left up a lane. We'd walked up that lane yesterday and it was no way suitable for a MH. So we switched the damn thing off and made our own way to the M5.
We have it set on "Fastest Route" as "Shortest Route" definately went in the straightest line from day 1.
I've double-checked all the setting and been through all the Garmin FAQ's (emailed them now). Completely baffled
Is anyone else getting these problems? I don't recall it doing it last summer so suspect a dodgy update has taken place. Has anyone found out how to fix this?
We opted for the Garmin Camper Sat Nav as you could programme in the MH size and add avoidances such as narrow lanes. We were therefore somewhat surprised on Wednesday that it routed us cross country taking almost a straight line route. One road it was telling us to use even had a "unsuitable for large vehicles" sign at the entrance. Fortunately the wife was quick with the road map and re-routed us where we'd expected to go.
It tried the same thing coming home today told us to turn left out of the site, then first left up a lane. We'd walked up that lane yesterday and it was no way suitable for a MH. So we switched the damn thing off and made our own way to the M5.
We have it set on "Fastest Route" as "Shortest Route" definately went in the straightest line from day 1.
I've double-checked all the setting and been through all the Garmin FAQ's (emailed them now). Completely baffled
Is anyone else getting these problems? I don't recall it doing it last summer so suspect a dodgy update has taken place. Has anyone found out how to fix this?