My 1030 flashed up an firmware update this morning and I choose to let it do its thing. After a few minutes the pedals stopped flashing in anyway, so I decided to head out. Tried again a few times and it seemed to just time out. Later on I kicked off the upgrade again and spun the crank every 30 seconds, or so. 10+ minutes later a message indicating the upgrade was complete came up.
In my case, based on no science whatsoever, I think the pedals just went to sleep half way through the upgrade
Updated to 3.3 and right pedal missing issue even worse! Had to switch off right pedal!!! Do not Update!!! Need help from Garmin before dropouts but possible to ride, now no way to use!
Mine worked 3 times and again drop every few seconds
I have an 810 so cannot update the vector 3 software through the head unit. I've tried all the things others stated on this thread to get the latest version 3.3 to update on IOS GCM but it doesn't recognize the new update and keeps indicating that v3.0 is the current version. Does anyone have a resolution to this issue? This is more than frustrating. I lost my cycling dynamics when I updated to v3.0 - now they have a fix in v3.15 / 3.3 and theres another problem preventing me from updating to the new version.... GCM was just updated from the App Store yesterday so I have the latest version of that. How do I get GCM to recognize the new update v3.3???
As per other thread, what’s your head unit and GCM version? Also do you know anyone with a head unit that supports upgrades eg E1030, E1000, E520?
GCM just updated yesterday, I think to 4.5.2 if I’m not mistaken. I do not know anybody that has a compatible Garmin head unit that I could use for the update either.
I finally got the "Update available" message in GC for iOS 4.5.2 this morning - started the update (iPhone 7), blue bar moved, it kept moving, pedals started blinking, and... "Update Failed". :(
I hit "Retry" for half an hour (pedals where blinking all the time) at which point I gave up, rebooted the iPhone (Pedals stopped blinking). GC didn't let me try a second time: I am back to the "Firmware 3.0 is the latest version" loop.
Man, I think I won't ever step into a plane which relies on Garmin devices for navigational purposes, and while the idea of the Descent MK1 sounded really interesting to me, having my computer reboot at 40m is nothing I want to experience. The hardware is fine but I have no idea what they are doing software-wise. Looks like the contracted GC to some kid hacking away happily. *sigh*
So, I have a friend borrowing me his Edge 520 tomorrow and shall attempt to update using his computer (question to Garmin: why can't I update the Vector 3 using my Mac and its USB ANT+ dongle?). I am a little bit unsure what to do exactly when following https://www8.garmin.com/support/download_details.jsp?id=11909. Since there is no direct download, do I simply
(1) connect the Vector 3 to the Edge 520 via ANT+ (2) connect the Edge 520 to Garmin Connect on my Mac using a USB cable (3) ??? (4) happily use my Vector 3 running 3.30
IBM-compatible PC running Windows 2000 or later operating system and an available Com 1, 2, 3, or 4 port.
PC Interface Cable for your GPS unit. The PC Interface Cable may be purchased through your local Garmin distributor or ordered direct from our Online Store.
you come across as somebody not working very diligently on there support documents, don't you think?
There I was thinking I was one of the lucky ones. I had been on 3 short rides (fw 3.15) without issue – until this evening.
It was the first ride since updating to 3.30 and I had extended periods of no power being reported from either pedal. At one point I had ‘Error Code 8000’ appear on my Edge 520 (fw 12.53); not sure what that means as it’s not in the in the sticky thread. I was also recording it on my 935 (fw 8.0) which mirrored the dropouts seen on the 520. Looking through the data I hd
The pedals were in GCM (4.5.1) and I know there had been issues with this in the past but I was under the impression this was fixed. Maybe I’m wrong. I’ve now removed them.
It was the first ride since updating to 3.30 and I had extended periods of no power being reported from either pedal. At one point I had ‘Error Code 8000’ appear on my Edge 520 (fw 12.53); not sure what that means as it’s not in the in the sticky thread. I was also recording it on my 935 (fw 8.0) which mirrored the dropouts seen on the 520.
The 8000 error code is a conflict indication. You have a mismatched setting (one of crank length, cycling dynamics or auto-zero, most likely) between the Edge and the 935. As a result, the pedal is spending all its communication bandwidth trying to arbitrate between the two head units. I'm pretty sure that the 935 defaults its cycling dynamics configuration to be 'on' so that might be the root cause.
Thanks for the quick reply t_smit. I've checked the setting and they are the same between the units. Although, as far as I can see, the 935 does not have the option to enable/disable cycling dynamics. Only to set the crank length and auto-zero.
Would a mismatch between either the Edge/935 and GCM cause the same error?
