This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error opening current.gpx in BaseCamp

[TABLE]
[TR]
[TD]Garmin DriveAssist 51 LMT-S[/TD]
[/TR]
[/TABLE]
Device is working perfect, but as soon as I connect to BaseCamp I see error, so gpx/current.gpx can't be read.
Now, I can't import tracks to my BaseCamp. I managed to copy this file manually from the device, open it as an xml file. Even more, I have found the exact track, which causes this issue. But I can't find, why it can be broken?
Are there some tool to check/fix the gpx file?

I can manually delete file from device, but it has been recreated by device and can't be open once more neither BaseCamp nor Mapsource.

I asked support but they told me there is no bug :) File is just corrupted ;)
Any advice? Except factory reset of device :)

0 SUSSAMB over 7 years ago

current.gpx is a one way copy of what's in inaccessible memory, so delete it then reboot your Drive, that will then recreate the file ... Hopefully that will fix it.

0 [email protected] over 3 years ago in reply to SUSSAMB

I have the same problem with my Garmin Drivesmart 51 LMT-S. Your advice here did not work. Basecamp says there is a problem communicating with the device. The "current.gpx" file is re-created per your instructions but it still does not work. How do you load gpx files in the Drivesmart 51 and run them? Thanks.

PS...I found that Basecamp WILL send a gpx file to the Garmin. It puts them on the memory card in Garmin\GPX. I can also manually copy them there, too. They will work when I go to Apps, Trip Planner, Saved Trips, and load them. However, I still get the above error messages when I connect the Garmin to Basecamp even though everything seems to work.

0 SUSSAMB over 3 years ago in reply to [email protected]

BC will only place a gpx file on the card if you select the card and not the device.

As for current.gpx file not working, you would need to delete all data from your device as part of it is likely corrupted.

0 [email protected] over 3 years ago in reply to SUSSAMB

SUSSAMB,

I did a reset of the Garmin and that fixed it. Thanks!

0 SUSSAMB over 3 years ago in reply to [email protected]

Great, will close this thread