Error loading waypoints from device

Former Member
Former Member
I keep getting an error when trying to load up waypoints from my etrex 20 in Basecamp, at the moment I only have a handful stored but they are in three seperate files (stored on different dates) my unit shows up after connecting, the green bar underneath start moving across indicating data transferr then right at the end I get the following error

There was a problem communicating with etrex unit id *********
An error occured while reading the following file G:/Garmin/gpx/Waypoints_28-MAR-12

Only a couple of the waypoints show up in Basecamp but on the unit they are all there and work fine!
  • I've tried to see examples of this on my Etrex 20 but can't duplicate it. Saving waypoints directly onto my Etrex results in an entry as you describe, but it loads fine into Basecamp.

    I think the first thing I would do is try a fresh install of Basecamp and see if that solves it.
  • Former Member
    0 Former Member
    I doubt this is a problem with BaseCamp, this is probably some invalid gpx files. Check you eTrex for gpx files and try to Import them into BaseCamp. Post the ones you cannot import and we can take a look why they are bad.
  • Former Member
    0 Former Member
    This stopped briefly but has started happening again, it seems to start playing up if I have restored the waypoints back onto my device from My Collection in Basecamp, it puts all the waypoints back on collectively in 1 file called waypoints, all the waypoints on my device still show up and work fine!
    Can I change my username from my email address? And WHY does it keep telling me my username and password are wrong everytime Itry and sign in? I have used these for years GRRRRRRRRRRRRRRRRRRRRRRRRRR
  • Former Member
    0 Former Member
    I keep getting an error when trying to load up waypoints from my etrex 20 in Basecamp, at the moment I only have a handful stored but they are in three seperate files (stored on different dates) my unit shows up after connecting, the green bar underneath start moving across indicating data transferr then right at the end I get the following error

    There was a problem communicating with etrex unit id *********
    An error occured while reading the following file G:/Garmin/gpx/Waypoints_28-MAR-12

    Only a couple of the waypoints show up in Basecamp but on the unit they are all there and work fine!


    This has happened to me with both an Etrex 30 and a 62s when I do waypoint averaging. I've found that MapSource is more forgiving and will load these files, and once MapSource has saved them, I can load them into BaseCamp and transfer them back to the GPSr.
  • Former Member
    0 Former Member
    Funnily enough I tried waypoint averaging the other day and after that the problems started (again)
  • Former Member
    0 Former Member
    I notified product support of this on 1/3/12. On 1/10/12 they said "Thanks for the information". Might be a good time to jog their memory, using the link Falagar provides above.
  • Former Member
    0 Former Member
    I was on the phone to them yesterday for nearly an hour!!!!!!!!
    Funnily enough I was told they had not come across this problem before!
    I have sent an email describing the problem with images of errors etc.
  • Former Member
    0 Former Member
    Can I change my username from my email address?


    Please contact product support about changing your username. Link is below.
  • Former Member
    0 Former Member
    etrex seems to be corrupting its gpx files

    etrex 30 with factory firmware (mar 2012 I believe it was 2.30). I purchased it just before a trip to Indonesia. While there, I recorded 4 to 8 waypoints daily for two weeks.

    After about 5 days, I noticed that the waypoints taken that day were disappearing from the waypoint manager.

    The next day everything resumed working.

    What I did not know:

    The etrex apparently stores waypoints in a GPX file that is started daily (or something resembling daily). i.e. there is a new GPX file created daily.

    When I returned home and attempted to retrieve the waypoints, I kept getting an error message about invalid waypoints.

    On examing the device storage, I discovered one GPX file for each day that I was recording waypoints.

    I laboriously inspected each of the gpx files and found one that was corrupted. All the formatting was gone. It was condensed to a single line, and and incomplete segment of a track description was inserted in the middle of it.

    After removing the broken track segment from inside an incomplete waypoint description, I fixed the waypoint description XML, and then reformatted the file by hand to appear exactly as the others do. Strictly speaking the reformatting should not be necessary by XML syntax. I have no knowledge of the Garmin XML parser or its limitations, so I did it just to be sure.

    All of this editing was done to the files on the device and changes were saved directly to the device.

    The outcome: Everything worked just fine after that. All the waypoints and all the data onboard became available to Basecamp and I have not had any difficulty since then. The missing waypoints (the ones that disappeared from the onboard waypoint manager while in Indonesia) reappeared.

    I believe you have a corrupted GPX file and until you fix it or remove it, you will continue having problems.

    I have since updated the Etrex 30 firmware to 2.7 and have not had any difficulties yet, but I am not using the device the same way so I do not know if the file corruption problem is fixed.

    I have just now extracted and save all my data and am about to do a complete reset on the device, and will take many waypoints per day for several days to see if the problem persists.
  • Former Member
    0 Former Member
    This is a recurring problem, when it happens I delete the GPX file and then add the waypoints again, everything is ok for maybe a week then it does it again. It really is a pain, and what makes it worse is that they show up on the device! I have actually had an individual waypoint gpx file fail to read in Basecamp as well (ie just ba single waypoint stored on its own on a particular day) it's as if the device is failing to write the data properly, it needs addressing :mad: