Basecamp 3.3.1 having trouble communicating with device

Former Member over 13 years ago

Since updating the firmware (to v3.90) on my GPSmap62s, base camp has been giving me an alert "base camp having trouble communicating with device" after which the icon will appear in the devices list, but obviously will not have downloaded any of the data.

This is what I get in my console log immediately following the alert box....

12-02-26 12:09:20.781 AM BaseCamp: Error reading /var/folders/7r/yl73yhtn401bvng9mnhlt7_00000gp/T/tmp51345: Line 11: Specification mandate value for attribute maxlaC0B
Line 11: attributes construct error
Line 11: Couldn't find end of Start Tag bounds

12-02-26 12:09:20.783 AM BaseCamp: Error2 reading /var/folders/7r/yl73yhtn401bvng9mnhlt7_00000gp/T/tmp51345: line 11 column 3 - Warning: <bounds> missing '>' for end of tag
line 11 column 61 - Error: unexpected </name> in <bounds>
line 32 column 3 - Error: unexpected </wpt> in <bounds>
line 44 column 1 - Error: unexpected </gpx> in <bounds>
1 warning, 3 errors were found!

This document has errors that must be fixed before
using HTML Tidy to generate a tidied up version.

12-02-26 12:09:20.784 AM BaseCamp: Error reading /var/folders/7r/yl73yhtn401bvng9mnhlt7_00000gp/T/tmp51345: Line 11: Specification mandate value for attribute maxlaC0B
Line 11: attributes construct error
Line 11: Couldn't find end of Start Tag bounds

12-02-26 12:09:20.785 AM BaseCamp: Error2 reading /var/folders/7r/yl73yhtn401bvng9mnhlt7_00000gp/T/tmp51345: line 11 column 3 - Warning: <bounds> missing '>' for end of tag
line 11 column 61 - Error: unexpected </name> in <bounds>
line 32 column 3 - Error: unexpected </wpt> in <bounds>
line 44 column 1 - Error: unexpected </gpx> in <bounds>
1 warning, 3 errors were found!

This document has errors that must be fixed before
using HTML Tidy to generate a tidied up version.

Does any of that mean anything to anyone? I've tried locating the file using spotlight, but nothing is found.

I would really appreciate any advice anyone can offer. Thanks!

0 Former Member over 13 years ago

In the Finder:

Click Go >
Choose "Go to Folder"

Copy and paste the path from the error message then click GO.

The contents of that folder will open for you.

/var/ is an invisible folder in OSX by default. That is the reason Spotlight cannot find it.

0 Former Member over 13 years ago

Thanks for that!

I got so far as finding the "T" folder, but there wasn't any file within it by the name of "tmp51345". Not that I would know what I would do with it if it were there.

Any idea about the functionality of the files within the var folder and how they might affect basemap?

0 Former Member over 13 years ago

I'd try keeping that folder open while I start up BaseCamp.

Then try to open the offending file with something like "Text Wrangler" from barebones software.

Not very likely that I'd be able to figure out any solution, but at least I'd have lots of information to pass along to Garmin support.

0 Former Member over 13 years ago

Good call. Had the folder open as you suggested. Seems two files are being written; a 'tmp#####' file and a 'tmpXSLT#####' file. They are very transitory, appearing for only a second or two before disappearing. I guess I'll see what Garmin has to say.

Thanks for your help!

0 azdrmn over 13 years ago

Since updating the firmware (to v3.90) on my GPSmap62s, base camp has been giving me an alert "base camp having trouble communicating with device" after which the icon will appear in the devices list, but obviously will not have downloaded any of the data.

Unfortunately there is an issue with the GPSmap62's 3.90 firmware update that will cause it to corrupt data that was on the device before the update. I believe there was a warning that told users to send all their data to BaseCamp and then delete it off the device before updating. Sorry if you missed that warning.

At this point, your only real fix is to delete all the data off your device from Finder. You can go to the /Garmin/GPX folder on your device and delete all the GPX files. Sorry for the inconvenience.

0 daknudsen over 13 years ago

Unfortunately there is an issue with the GPSmap62's 3.90 firmware update that will cause it to corrupt data that was on the device before the update. I believe there was a warning that told users to send all their data to BaseCamp and then delete it off the device before updating. Sorry if you missed that warning.

At this point, your only real fix is to delete all the data off your device from Finder. You can go to the /Garmin/GPX folder on your device and delete all the GPX files. Sorry for the inconvenience.

The issue arises for those not heeding the warning which is spelled out quite clearly to those upgrading from 3.40 (?) or lower. It's a very annoying set of steps to follow, but if you did it correctly, no need to repeat for incremental upgrades after that. Glad I am done with it and sure hope they don't have us jump through those hoops again.