Critters
Retired Black Rat
That is brilliant, just about sums up my issues but less distance involved in the deviation. I have uninstalled Basecamp from my laptop and now going to reinstall it to see if that makes a difference.
Zumo 590 and Basecamp - Some Navigation Issues Solved. (Maybe)
- Thread starter jfheath
- Start date
I think they are all compatible until they are not.
The spontaneous recalcs started about 2 years ago?? I do a couple of multi week trips a year and load the routes onto the units of my riding partners. My 660 and the 665 of my partner recalc randomly and not at the same time. I don't think it has anything to do with maps. We always insure we're all on the same basemap. Garmin never figured it out so they said go back to Mapsource. Not really an option for me at this point. I just terminate the route and reload it. It continues from where I am.
Critters
Retired Black Rat
A bit like a lifetime guarantee??
Reginald
cyclepoke
I have a Zumo 550 and the wife has a Zumo 660. Different machines/hardware thus different programming. I don't think Garmin ever thought to program them to react the same. They were probably working on upgrading/enhancing the system. Options are located under different menu locations. My solution was to turn recalculation off on my 550 and have a prompt "Yes or No" for the wife's 660. That way if for some reason we go off route, I know where the original was and the wife's can get us back to it. Handy for going off the route for sight seeing, lunch, or dinner.
Critters
Retired Black Rat
Strangely enough so has the Basecamp for my Macbook, I watched your videos and I'm amazed at the differences between the PC Version and Apple but you have made it clearer to use for me, I don't know how the basecamp tutorial is condensed into two minutes but its fine provided all works as it should I suppose.
Shuey
Site Supporter
- Joined
- Jul 3, 2007
- Messages
- 2,100
- Location
- Niceville, FL
- Bike
- FJR1300 ES, 2018
- SPOT
- LINK
- STOC #
- 7005
My experience is that there is a big difference between "fastest time" and "shorter distance." If you're on an multi-lane highway (think Interstate in the US), "shorter distance" will often route you off the highway at an exit only to have you continue across the cross street, onto the on-ramp to get back on the road you had just left. This happens when the exit is inside the curve of the main road, thus the shortest distance. If you want "fastest time" then choose it. If you want to go exploring choose "shortest distance."
I have both a 660 and 665 and this occurs the same on both.
BTW I really like Basecamp even with it's shortcomings. This thread has been a great discussion.
Shuey
We both have the recalc option off, yet the unit spontaneously decides to recalc. No prompt at all, it just does it. It's a glitch. Garmin says the solution is to use Mapsource. I've never gone back to try their proposed solution.....
This worked like a charm! All of my past routes now have a profile of "none". I just use the motorcycle profile for creating new routes knowing any changes to the profile no longer effect my previously ridden routes.
Help!! OK, got my new 590 and started playing with it. I'm doing a 50CC ride later this year from NY to SF. Google says this is 44hrs of ride time. The 590 says it's almost 46hrs. How can it be slower than google which assumes the speed limit? The mileage is the same and I verified the same route. I have "fastest" selected on GPS with no other avoidances. I do not have the traffic app, so that can't be coming into play. My trusty Nuvi 550 says 41hrs because it assumes a little over speed limit. Any ideas??
Edit- No basecamp was involved here
Edit- No basecamp was involved here
The route in question is essentially one road that is 3000 miles long. I had 2 friends with 590s plug in the same route and they both got an ETA several hours less than what Google showed which makes sense because as you said, the unit learns how fast you ride. Hopefully once I get some miles on it, it will be more accurate.
With MapSource or Streets&Trips, you manually set your driving preferences for each type of road. These calculated a time for your route. The GPS (550 in my case) would come up with a time based on its own calculations, it was rarely the same as the software, but close if your preferences were set properly. The 550 would modify its arrival time based on your speed/traffic/stop signs/lights, and in general I found that to actually average the speed limit you have to go 15-20% faster than the limit. This would be less true if you were slabbing it. But, I never find Google maps times agree with anything, so don't sweat it.