Garmin Update
here is my original review of the Garmin 705 i did link
Today i went out for a long ride did some serious power tests and was looking forward to getting home and reviewing my data, but when i connected my unit to the computer and tried to download the file all i got was distance, time, ave speed, av power and av cadence. i them tried a few “tricks” i have used in the passed to get files to work, but without luck
Lately there seems to be the growing problem that my 705 seems to corrupt files after rides. i would say about 1 in 4 rides creates a bad TCX file. most times i can fumble around and get some sort of data out the corrupt file. today – nothing
There are ways to fix these broken files and guys on the internet who check through the xml, there are even a few applications that try to fix them. This is all very well, but it should not be an issue to start with. Garmin a selling a top end product that should deliver its users the features they expect. They have released numerous new versions of the firmware but the fault seems to stay. The garmin forums run hot with complaints from other users who seem to have the same problems as me.
You can understand that it is very frustrating. If it was not for this ongoing issue the 705 would be perfect, but lately i just don’t have the confidence in it that i used to.
if your experiencing the same problems please check out this forum for help
https://forums.garmin.com/forumdisplay.php?f=21
or email this guy
Dario Costa dario(AT)teambikeolympo.it



Just to answer a few q’s and explain my setup
i have a powertap SL hub, a 705 with latest version firmware.
post every ride i stop the recording, wait about a min, then reset the recording, wait another minute and then turn it off.
i use a mac with windows 7 parallels. files are copied off unit using finder in mac, then boot windows and import into sportstracks and wko+
files are them deleted out the history directory on the unit
on the advice of “garmin”
i rolled back to version 2.9 and deleted all files and user prefs on the unit,
so far so good, seems to have fixed the issue