Error loading waypoints from device

etrex 30 with factory firmware (mar 2012 I believe it was 2.30).

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.

Upon reflection I realize that I may have played some part in the corruption of the GPX files:

Being in heavy use for over two weeks, the batteries were naturally being replaced/recharged on an almost daily basis. It was not my intention to capture tracking data and I did not know that tracks were being recorded.

It is quite possible, even likely that during the many battery changes I may have yanked the batteries without powering down or that the batteries ran down. Had I not been recording tracks, that would be immaterial, but since I was, it is just possible that the batteries go yanked while the device was updating a track.

It would be an extraordinary coincidence of events, and indeed, for this recording schema I think there is an onus on the device to recover gracefully so it is still a system software defect.

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've averaged waypoints using Beta 2.71 and the problem remains. Regarding batteries, my batteries were fresh.

I have this problem with my Montana 650, firmware version 4.20. After averaging a waypoint Basecamp will not load the waypoint file.

I found the problem with corrupt gpx files, at least for my Montana. See my post at:
https://forums.garmin.com/showthread.php?20958-Waypoint-averaging-corrupts-the-userdata-gpx-for-Basecamp&p=143643#post143643

I know this thread is old, but I thought I'd jump in here anyway.

I'm here looking for a solution to a similar problem. I'm getting an error like this when I connect my Fenix up to BaseCamp. But it's only happened after I shared a waypoint from my 450 to the Fenix. If I delete the bad GPX file from the Fenix manually and then load up BaseCamp, it loads up fine. I looked over the XML file but really didn't see (or know) what might be wrong with it. I might try going over it again after reading COLEMAN's post above when I get a chance.

This is my first post on the forum btw :cool:

Waypoint averaging corrupting GPX file in eTrex30

As a few in this thread have experienced, I have had my eTrex30 corrupting the GPX file on the unit when I have used waypoint averaging. It seems less likely to happen if the GPX file has fewer waypoints in it. So, if I know I need to do waypoint averaging I will just put the few waypoints I need on the GPS and remove the rest (putting them back on later from Basecamp). But I have found it's still not a guarantee of success. I'm running the latest firmware V4.30
This bug is driving me nuts!

This is a device not BaseCamp issue. Please contact Product Support for help.