Trouble Exporting Trip from Basecamp 4.4.7 to BMW Navigator V

Former Member
Former Member
Hi all, am very new to this GPS route planning malarkey, am a design engineer but not very computer-speak literate and have spent most of the weekend figuring out how to use Basecamp at a basic level. I now have our big summer motorbike trip around Europe all set out in Basecamp, which has been great for planning how long each day's riding should be and selecting detours etc.

I thought as a test of getting a trip over to the Navigator unit itself, I'd try planning my daily commute in as a separate new trip and exporting that (and then seeing how you find it on the device, how you tell it you're ready to use that route and how it copes when you deviate from the route etc).

However, when I try to send it to the device, it comes back with "an error occurred while sending the following file(s): gps/temp.gpx" Can anyone shed any light on what I need to do to fix this problem? My test trip is a 60 mile round trip from home to work with only one way-point on the outbound leg.

Thanks in advance for any assistance you can provide.
  • I believe the Nav5 is similar to the Garmin Zumo range, but which one I'm unsure. Instructions for accessing routes sent to Zumos are here, but note that a couple of the models are said to not work well with Basecamp and Mapsource is suggested instead:

    https://support.garmin.com/support/searchSupport/case.faces?caseId=%7B65814150-50b3-11dc-4ec8-000000000000%7D

    Note there are specific Zumo forums at www.zumoforums.com where you may find better advice on your Nav5.
  • Former Member
    0 Former Member over 9 years ago
    Thanks in advance for any assistance you can provide.


    I have a Nav V and have not experienced this problem. So here is what I would try: Make a simple route in BC....NOT a trip. I do not use the Trip Planner, just click the Route tool. Assuming you have CNEU as your map, just create a test route with three points, start, middle, and end (which you did, but do a new one).

    Right click it in the left pane, then "Send to", scroll down and select the Nav V Internal Memory. You should see a little green line and then a green check mark in the internal memory line when it's finished.

    Now, dis-connect the Nav V, start it up, and then go through these steps:

    1.When the device is first powered on, the message 'New routes found. Import to Trip Planner?' will appear, Touch Yes
    2.Select each route you want to import
    3.Touch Import
    4.Go back to the Main Menu
    5.Touch Apps
    6.Touch Trip Planner

    There is considerable confusion about the semantics of Route vs. Trip in everybody's minds, including Garmin's! I prefer to think of a trip as a collection of routes, and instead of dealing with Garmin's idea of Trips, whatever that is this month, I simply create a folder that includes all the routes and waypoints on my upcoming trip in BC, name each route to something that makes sense to me, like Day 1, Day 2, or Stuttgart to Munich, etc. There have been difficulties with the Trip Planner App in BC and certain devices, so I simply never use it and have no problems. I can do this in my head, anyway. After all, if I'm only going to make one German trip this summer, all I care about is which roads I'm going to use an any given day.

    Then I delete all the existing routes in the Nav V, (done through the Trip Planner applet), hook it up to the computer, and load only that trip folder's contents. Now I don't have to page down through a bunch of irrelevant routes. When I get home, I reload whatever local routes I want.

    Your difficulty may have arisen because of the method you used to import, try the above word for word.:)
  • Defect in BaseCamp 4.4.7

    Hi,

    I am having the same problem with the Garmin Oregon 600t and the Phoenix 3. Basically, BaseCamp errors when an export of any type is attempted. I call support and was passed on to their development team. Long story short: There have not been enough issues/complaints to Garmin about this problem to support a fix. I was able to downgrade the version of BaseCamp to 4.2.5 and it worked fine there. Just have to put up with the annoying messages to update.

    Sam