Related

Basecamp communication problem

Former Member
Former Member
I originally created a number of waypoints on Basecamp, then exported them to my GPS. I later modified the locations of many on my GPS. Basecamp now gives me an error message and no longer shows these waypoints.

The Basecamp message I get when I connect:
There was a problem communicating with Oregon 450T
An error occurred while reading the following file(s):
E:/Garmin/gpx/Route.gpx

I am able to see everything else from my GPS on Basecamp.
  • Former Member
    0 Former Member
    It seems like when you modified the data on your GPS, the file it wrote out (Route.gpx) somehow became invalid. One solution is to delete route.gpx on the GPS. That will also mean that you won't see that route on your GPS anymore.
  • Former Member
    0 Former Member
    I tried eliminating the route using the relocated waypoints on my GPS. That didn't fix the problem. I then eliminated all the subject waypoints as well as the route on Basecamp, keeping the relocated waypoints on my GPS. That didn't do anything either. When I removed the file from my GPS, I did not get the error message, but also did not see any of the relocated waypoints. In the end, I wrote down all the waypoint coordinates and manually entered them into Basecamp, then transfered to my GPS. This was a pain to do (about a dozen waypoints), but the only thing that fixed the problem. In the future should I remove the waypoints from Basecamp prior to connecting my GPS with relocated waypoints?
  • Former Member
    0 Former Member
    NeoLite,

    How are you handling the use case where waypoints with the same name but different detail information, e.g. location coordinates, etc. exist in Basecamp's list(s) and on the device?

    It seems to me this use case requires something like:

    - force a proper sync action, e.g. possibly replace the oldest with the newest or rename the oldest by adding a number to the end, etc and tell the user what was done, or,

    - ask what sync action to take, e.g. delete, rename, whatever, or,

    - pop a dialog window describing to the user how to manually fix the situation, e.g. list the problem waypoints and tell the user they need to be deleted or renamed in Basecamp or on the device. Optionally, it would be nice if all of the offending waypoints could be displayed in a new list in Basecamp to make it easier for the user to find and fix.

    Just a thought.

    ...ken...
  • Former Member
    0 Former Member
    I just got a GARMIN GPSMAP 62s and I have exactly the same problem but with tracks.

    I originally created a track o Google Earth and export it to GPX or GDB and import them into Basecamp, then exported them to my GPS. I later modified the track in my GPS (for example the color). Basecamp now gives me an error message and no longer shows the track:

    The message I get when I connect:
    An error occurred while reading the following file(s):
    E:/Garmin/gpx/Track.gpx

    Please Help Me!
  • Former Member
    0 Former Member
    The track color problem in the GPX is a fairly well documented issue. Upcoming device firmware and the next version of BaseCamp will resolve this issue. Note that both parts are needed, not either/or.

    In the short term, if you are comfortable editing the XML in your GPX file you can just delete the extension that specifies the track color inside of that track.

    The part to delete will look something like this:
    <extensions>
    <gpxx:TrackExtension xmlns:gpxx="www.garmin.com/.../v3">
    <gpxx: DisplayColor>Green</gpxx: DisplayColor>
    </gpxx:TrackExtension>
    </extensions>
  • Former Member
    0 Former Member
    You can retain the indentation of code snippets like your XML example if you use the "code, /code" tags instead of "quote, /quote".

    <extensions>
    <gpxx:TrackExtension xmlns:gpxx="www.garmin.com/.../v3">
    <gpxx: DisplayColor>Green</gpxx: DisplayColor>
    </gpxx:TrackExtension>
    </extensions>

    ...ken...