This may be a hardware question, in which case apologies for posting it here, but it begins with BaseCamp 4.2.4 (Mac).
The discrepancy shows up on my zumo 660 and I strongly suspect it is platform-agnostic and it may have more to do with the GPS than BC, so mods feel free to delete if that is the case. But...
If I create a series of routes in BC, my usual method is to export them as GPX files which I store on the SD card in my zumo. I use enough vias and "real" waypoints to make sure the routes do not get mangled during a recalc and I set the the zumo to "prompted" to avoid unnecessary recalcs. I then import the routes as needed. For my upcoming ride to NC & TN, I created 18 routes. Of those, about half changed during a recalc, which I always force after importing just to flight check things in advance of a trip.
But here's the odd thing. All were created in BC using the Motorcyling activity, no avoidances, fastest time. The ones which passed the flight check -- after a forced recalc on the zumo showed no changes -- all showed up in the zumo recalc screen with Fastest Time already selected. All of the routes which flunked and did change during the forced recalc, showed up with Shortest Distance selected on that screen. All were created using Fastest in BC.
Why would some routes and not others "think" they were created using Shortest? All were done on the same map version, which is also the same version in the zumo (2014.40).
Any ideas?
Thanks,
-dan
