Discussion: Difficulty uploading from Garmin
in: Orienteering; The Website
Jun 12, 2013 8:58 AM
#
Tom:
Hi there,
Anyone else having issues uploading over the last few days using batch upload? For some reason its telling me that my device is not supported. It is still uploading to garmin connect so wondering if its an attackpoint issue?
Tom
Anyone else having issues uploading over the last few days using batch upload? For some reason its telling me that my device is not supported. It is still uploading to garmin connect so wondering if its an attackpoint issue?
Tom
Jun 12, 2013 2:14 PM
#
ken:
Hi Tom,
The "unsupported for reading data" message you are seeing is coming from the Garmin plugin. You will get a message like this if the plugin tries to download from something that looks like a watch, but isn't, like a USB memory stick or SD card (Some Garmins legitimately present themselves as USB drives). I can see from my end that this is what is happening to you.
If the plugin finds only one "device", Attackpoint will try to download it without telling you which one, which can mask problems like this. If you have any other usb things like that attached, you might want to try unplugging them, at least until you have this figured out.
If the importer is giving you a choice between "An SD card" and your 310, make sure to click the 310. If it's not giving you a choice, then it means the plugin isn't seeing your 310 for some reason. So far I have only heard of this happening for watches that connect via cable (e.g. 305, 210), but actually aren't physically connected for whatever reason.
You can confirm whether this is an AP-specific issue by going to the GC upload page, and seeing whether the 310 device shows up there. (you may be normally uploading to GC automatically via ANT agent, which bypasses the communicator plugin). There is a slightly newer version of the plugin, which might help to install.
Let us know what you find out.
By the way, an immediate workaround that you can use is to chose the "upload files" method of importing, and then pick your tcx or fit files from the hidden ANT+Agent folder (for win7, type in: "%USERPROFILE%\AppData\Roaming\GARMIN\Devices" and then click down into device number and "history" or "activities"). You can pick more than one file at a time.
The "unsupported for reading data" message you are seeing is coming from the Garmin plugin. You will get a message like this if the plugin tries to download from something that looks like a watch, but isn't, like a USB memory stick or SD card (Some Garmins legitimately present themselves as USB drives). I can see from my end that this is what is happening to you.
If the plugin finds only one "device", Attackpoint will try to download it without telling you which one, which can mask problems like this. If you have any other usb things like that attached, you might want to try unplugging them, at least until you have this figured out.
If the importer is giving you a choice between "An SD card" and your 310, make sure to click the 310. If it's not giving you a choice, then it means the plugin isn't seeing your 310 for some reason. So far I have only heard of this happening for watches that connect via cable (e.g. 305, 210), but actually aren't physically connected for whatever reason.
You can confirm whether this is an AP-specific issue by going to the GC upload page, and seeing whether the 310 device shows up there. (you may be normally uploading to GC automatically via ANT agent, which bypasses the communicator plugin). There is a slightly newer version of the plugin, which might help to install.
Let us know what you find out.
By the way, an immediate workaround that you can use is to chose the "upload files" method of importing, and then pick your tcx or fit files from the hidden ANT+Agent folder (for win7, type in: "%USERPROFILE%\AppData\Roaming\GARMIN\Devices" and then click down into device number and "history" or "activities"). You can pick more than one file at a time.
This discussion thread is closed.