This site uses cookies to offer you a better browsing experience. Find out more about how to manage cookies, or dismiss this message and continue to use cookies.

privet01

About

Username
privet01
Joined
Visits
3,152
Last Active
Roles
Member
Points
228
Badges
7
  • NUVI 2340 upgrade - make space on the SD card

    SD cards are pretty cheap. I'd just get a 16GB class 4 or better card. I have had trouble with brands though. I bought a PNY 4GB class 4 that wouldn't wouldn't work in my nuvi205w, but a sandisk 16GB class 4 is recognized. The PNY card does work in other devices.

    Your current SD card doesn't contain a preloaded map from Garmin does it?
  • HOLY COW.... which one?

    If you only view them as assistants that might make a mistake occasionally, then they might be helpful.

    At least if it gets you into the same situation again, you can direct your anger to it. Misplaced though it is. <<grin>>

    Here is a link to Garmin's comparison of the two.....
    https://buy.garmin.com/en-US/US/catalog/product/compareResult.ep?compareProduct=135455&compareProduct=524447

    I don't use these types of gps's. So I can't really tell you much from experience. However I've seen posts here and elsewhere. I think the praise outweighs the cursing. But realize that map data which this device depends on may be inaccurate in some areas.
  • Garmin's Ascent and Track Distance is always more then others..

    I'd imagine garmin winds up purchasing an "off the shelf" barometric sensor package for each of it's devices. And in quantities equal to the planned manufacture life of the unit. But as each device has a different design/manufacture time frame for both Garmin and the sensor manufacturer, that many Garmin device are getting barometric sensors that may or may not be as good as another. Or require different massaging of their data because of the accuracy and resolution of their data.
    I know that my edge500 was touted as being accurate to 50 feet, but the later edge510 and 800's are accurate to 10 feet. Yet both will show at least two feet of change as you move about.

    Again, at least to me, it's comparing apples and oranges.

    Comparing data for gps tracks from different times of the year can be apples and oranges too as the satellites are not geosynchronous and some times are in a position for a good fix and other times not.
  • Dakota 20 and Garmin Connect

    I finally took the time to look up the Dakota 20. It's not as old as I was thinking so it has a better chance being fully compatible with Garmin Express (GE) and Garmin Connect (GC).

    In the overview it does mention that you can upload activities to GC. But in the optional accessories it only list a temperature sensor, the Garmin Tempe as the only available fitness sensor you can connect it to.

    The manual states that it can pair with a Garmin heart rate monitor and a Garmin cadence sensor but does not mention anything about the Garmin Tempe..... but that's an occasional or maybe not so occasional point of confusion Garmin creates at times.

    Nor does the manual mention anything about GC. As well it doesn't state what file formats it accepts.

    At the Garmin Forums in the Garmin Express section, a search on "Dakota 20" pulls up several old posts that might be useful/interesting to the OP.

    So it still looks like nothings for certain between GC and the Dakota 20. And experiences may vary between different users.

    The frustrations of trying to get the Dakota to work with GC may not outweigh the frustrations the OP has with Basecamp. Basecamp does get easier the more you use it.
  • Coordinates not available!

    Thought it might be useful to give a coord that I can't enter. Interestingly, I've just tried this one and I can't enter above 5 for the Long either!

    N44.20.653 W001.05.907

    Can anybody else enter that on a Nuvi 2595?
    What coordinate format do you have your nuvi set to use? Garmin devices I'm familiar with are very particular about the format you enter your coordinates. I don't recognize the format your's are in as you have two decimals in each coordinate.

    I suspect what you need to do is substitute a space for the first decimal in each coordinate if that is in fact how you are entering them in your nuvi.