Best Helpful Content
Software version 7.50 was released this morning for the DriveSmart 55. Maybe it will help your situation.
The FM coverage is very poor, you will only get it in major cities. I live 50 miles from Philadelphia and used to commute daily. I could not get any traffic data until I was about 20 miles from the city, which was too late to make a major change in my route. There are large areas with no coverage along the NJ Turnpike, even when you are close to NYC.
I don't think there's any list of what stations offer it, and that's not something the user is supposed to even know about. The device should automatically lock onto the strongest signal (if any). If you go into the developer settings, I think it will give you some data about this, but I haven't looked for awhile. The method for accessing this varies by device, on some of them you need to go to the volume screen and hold your finger on the top right corner. On other models you hold your finger in the middle of the speedometer in the trip computer (IIRC).
The traffic data comes from HERE (formerly Navteq). At one point Garmin claimed that it was augmented by data they receive from users with the smartphone link app. Not sure if that is still the case.
IMO, the FM traffic is useless if not downright misleading. I stopped using it long ago.
House numbers are based on the street name, not the highway name/number, so if searching for an address the street name is needed if travelling through it should not matter what the street name is.
Yes, for the handhelds it needs to be in the Garmin folder.
Thanks for keeping us updated- maybe this will help someone else.
FWIW, if the old firmware had tide data, you can revert to it. Old versions are archived on this site (which is well-known, but NOT an official Garmin site)
Note that these are actually the installers for the firmware and not the firmware itself. To revert, you will need to change the filename to GUPDATE.GCD and copy it to your GPS. I have gotten confused by all the different "flavors" of Garmin devices, which require that file to be copied to different locations. But I *think* the GUPDATE.GCD file needs to be in the \Garmin directory on the GPS. Maybe @sussamb can confirm this?
When you restart your GPS, it *should* ask if you really want to install firmware that is older than your current version. If you agree, it will then go through the installation process. This may take a little while, so be sure you have good batteries in the device, since a premature shutdown could be disastrous.
Also be sure that you have good backups of all your user data (maps, waypoints, tracks, etc) just in case. It's good practice to just copy the entire contents of internal memory to a folder on your computer periodically. I would also remove the SD card before doing a firmware update/downgrade. If there's already a GUPDATE.GCD file on the GPS, then that is the installer for your current firmware. You might want to save that for future use, if needed (although you could download it again from the link I posted).
Afraid not. But the 'new' tag seems to still work ok. The number of views of a topic has also been broken for many months and might not be working properly.
The truth is that this site is not overly active (the same fate as all GPS dedicated sites actually) so maintenance of the software is not a high priority by the poers that be.
I have a Montana, not sure how it might be different. However, if I go to Setup > Routing and choose Hiking or Pedestrian for activity, there is a menu for off-route calculation. What have you selected there? If you choose prompted, it should alert you when you go off-route.
However, if you choose Direct Routing as an activity, you will not have an off-route calculation menu.
I've been using GPSRs since the 1990s. Started w Magellan, and was pretty happy with them. For some reason, I changed to DeLorme PN-20, and followed the upgrade path, ending w PN-60. I was pretty happy with them, despite the arcane UI in the Topo and Street products, and the way they made significant changes to the UI. I am an active mountain biker, road biker, hiker, outdoor everythinger ;-), and use my GPS on my motorcycle and in my car. I guess there might be better auto GPSRs, but because I use my 60 all the time, I am used to it. And when moto or driving, I tend to memorize routes, anyway, so all the GPS does for me is provide reminders, or give me a shot at recovering from changed travel plans (accidents, construction, etc.) I'm pretty flexible and patient on the road. Life ain't perfect.
So...I decided it was time to upgrade to a newer device...larger screen, better response, connectivity...and bought a 66st. One of the first things I did was to go for a ride and see how it tracked. I plugged it into a late model car, just like I do w my PN-60, and it died. Never restarted. I contacted Garmin, and they said that they wanted to look at it, and swapped me for a new one. I still tried to use the new one on the road, but with a USB condom.
Now, there are a lot of good tech things about the 66st, but it's gotta actually do what I do.
I used BaseCamp. Garmin says that it is deprecated. Soon to be retired. Not under current dev. But should still work...sorta, it seems.
I loaded an OSM street map.
I exported my DeLorme waypoints (hundreds), and imported into BC.
I made custom waypoint symbols, because I am used to using them in the PN-60.
I put them in the correct place for BC and on the 66st.
I used BC to block-assign custom symbols to my waypoints. So far, so good.
I synced. No waypoints????? I contacted Garmin Tech Support. They didn't know what was up. I investigated (hacked) and found that BC was calling them 'Custom 3', for example, and the 66st wanted '003'. Hmmm...no way around that...I tried.
I tried using Garmin symbols in BC...I didn't want them...but figured that I'd see if that worked...well, it does...but not always...seems that BC calls a symbol Fred, and the 66st calls the same symbol Sally. What's a girl to do?
I tried to config it to my uses...you know, move the map, route, waypoint, etc. menu icons around so that the stuff I am most likely to use is at the top. It kept Quitting and rebooting. Not good. Eventually, it died to the point that it no longer really would do anything, except reboot back to the 'choose a language' prompt, so I returned it for a new one.
#3: The saga continued. I really thought I'd eventually get it to work. I can't send way points from BC, where it is convenient to assign all my custom symbols. I /can/ import them into Explore, and send them from there...BUT Explore won't let me use custom symbols, and I REALLY don't like the stock Garmin symbols. And even at that, Explore does not have a block assign of symbols, so I need to change hundreds of them one at a time. Not.
BC won't send routes to the 66st (at least not for me). Maybe it would if I renamed my custom symbols to 'Custom x'. Explore will. But I find annoying the constant complaining of Connect that my Bluetooth is turned off. BT is there for my convenience, not Garmin's.
For 2019, it is really not ready for prime time. Internally, very nice. But as a tool, not up to 2006 standards. The tools to manage it, and the way reconfiguring works on the 66st, are simply inadequate.
The internal stuff seems to work OK. I gave it a place to nav to, and it did. But that's not how I use it, and I really don't want to give up all my waypoints, custom symbols, tracks, and routes. So I sent #3 back, too. To me, it is just an expensive toy. I'll revisit it an a year or so, but in the meanwhile, I still have the PN-60, with its outdated maps, and GaiaGPS, which I find worth exploring. And paper and mental maps and compasses, which never let me down ;-)
tried my Nuvi 2797via one of these meters plugged into my USB3 port with a fully charged GPS and it shows 4.85V with a current starting at 0.880A (880 mA) settling down to 770mA.
That could be a hefty drain on many a computer port and it is recommended that the GPS be fully charged before connecting to a PC.
Lowering the screen brilliance to about 50% reduced the consumption to 330mA, this could be a simple solution if power consumption is the issue.
I will do a bit more experimentation as I have experienced many false start attempting Nuvi connect to W10 and just persevered, maybe it is time to track it down.