Montana 610 and Basecamp error

Communications issues are sometimes due to a bad cable or choice of usb port on the computer. I would try a different cable if you have one first. Next, try different usb ports on your computer.

If you know Waypoints.gpx doesn't contain anything you want to keep go ahead and delete it. If it does contain data you wish to keep, copy the file to your computer before deleting it from the device. If the file is okay, then you should be able to import it via BaseCamp's File Menu > Import and this would indicate a cable or port issue. If not, you can post it here and someone will look at it to see if they can spot the problem.

Thanks much for this btlaake. I tried a different cable, a different port and a completely different PC. No joy.

I don't have anything on that file that I can't afford to lose (I think), so I deleted and the error message did not pop up when I connected basecamp to the Montana.

I assume that the Montana simply creates a new waypoints file when I next create a waypoint, yes?

Thanks again.

I don't own your device. On my device, each Waypoint created on the device creates a new file called Waypoints#.gpx, where # is absent or a number starting from zero and counting up. When I send Waypoints from BaseCamp to the device, all the Waypoints will be written to a single file using the same naming convention.

I'm sorry that I haven't replied sooner, BTLaake. I deleted the waypoints file and all seems well. thank you

Last week I was sent a .gpx file to check as it resulted in the same error messages as you've attached. Fortunately, although Basecamp could not read it, Google Earth could so from GE it was saved as a .kmz file. The .kmz file was then imported OK into Basecamp and exported as a .gpx then emailed back to the customer.

In case it helps, on another occasion there were waypoints taken on the remote Auckland Islands (near Antarctica) which were obviously quite valuable. The .gpx file was able to be opened as a .csv and that made it easier to sort the data into columns and look at the patterns of text to see if there were any abnormalities. In this case there was a "<" (less then sign) missing from the row of text for 1 waypoint. Noting it's lat/long I then when back to the original .gpx, opened as a .txt and inserted the missing <. Saved it as a .gpx and it then worked.

Tks much for this kiwitonita. I will keep this in mind when/if the error comes up again. Good to know.