Garmin Vector Firmware issues
jgsi
Posts: 5,062
A resolutions seems imminent.off the Garmin Forum site..:
not too soon as using them outdoors has been not fit for purpose
not too soon as using them outdoors has been not fit for purpose
Hello,
Since identifying the root cause of the communications problems in the Vector 3.50 firmware we have implemented a fix and are currently doing pre-release testing to validate the system. Testing is going well so far and, if no new issues appear, we anticipate releasing a new Vector firmware version to public Beta next week.
A few things to note about the public Beta process:
This will be Beta firmware and therefore it may have some rough edges, but we anticipate it to be a significant improvement over Vector 3.50 firmware.
Applying the Beta firmware requires an Edge 520, 1000 or FR920XT. Detailed instructions will be posted with the Beta firmware files. Once the new firmware has been applied to Vector, the Vector system will be compatible with any ANT+ compatible display. The production release of Vector firmware will also be available via Vector Updater as usual.
There will be no ability to downgrade if you choose to apply the Beta build. Once you have upgraded, you will have to keep the Beta firmware on your Vectors until there is a production release or another Beta release.
Thank you again for your patience.
Vector-Info
Last edited by Vector-Info; Today at 03:17 PM.
0
Comments
-
Friend has been having loadsa issues with Vectors and his Garmin 500. Majority of the time it looks as though they have been only reading one side as reading are a good 50% down.
Hes got the latest firmware and finds he has to enter and insure its picked up his Crank Length before every ride and still then the data is often rhubarb when downloaded to Garmin site.
Hes got a SRM PC8 head unit on order as he's heard this pairing with Vectors works much better.
Any feedback on that Combination JSGI. It seems a lot of money for him to fork out if there is a Firmware fix in the offering which sorts it.
I take it that this Beta thing is similar to when we use Virtual Power on TR and look for a curve to match the turbo your on?0 -
IMO,, I think Garmin have been guilty of loading far too much into the firmware. increasing the likelihood of bugs... metrics that basically we just dont need as amateur riders - even if you race competitively or not.
I am just not ars5ed about pedal balance etc etc , I just want to see good power data recorded for post analysis.
To say that Garmin have scrwed up.. well if the revised firmware makes the pedal system useable again. all good
otherwise mine are going on Ebay and will be looking into different systems.. but I do like the pedal model.
It is not really a case of headunit fault though.. I also dont use a Garmin or particularly want to.
For others, as an example of what we all mean by a buggy firmware...
us Vector users are getting poor readout... total data drops... under reporting.. especially outdoors for some head scratching reason. I know I aint that classy a rider but even I know that doing 20mph + on false flats dont tally with showing just 90 watts...0 -
Friend has been having loadsa issues with Vectors and his Garmin 500. Majority of the time it looks as though they have been only reading one side as reading are a good 50% down.
Hes got the latest firmware and finds he has to enter and insure its picked up his Crank Length before every ride and still then the data is often rhubarb when downloaded to Garmin site.
Hes got a SRM PC8 head unit on order as he's heard this pairing with Vectors works much better.
Any feedback on that Combination JSGI. It seems a lot of money for him to fork out if there is a Firmware fix in the offering which sorts it.
I take it that this Beta thing is similar to when we use Virtual Power on TR and look for a curve to match the turbo your on?
I strongly suspect he's wasting his money, the issue is with the firmware in the vector pedals not the receiving head unit. He could put that money into a power2max and have an additional power meter, one that's well proven.
Garmin are saying they've identified the issue and will have a fix out in beta next week. Hopefully this is the case but, given Garmin's track record of never actually properly testing any of the new products or updates, then I suspect a beta release will be 'interesting'. The other concern is that they've known about the issue since May and haven't addressed it nor taken the standard step of rolling back the offending firmware so people had a working product. Beyond poor in my view, can only advise anyone not to buy into the garmin ecosystem.0 -
Interesting how they have sat on it from May to now. A company that size and rep surely could have come up with a " fix" quicker than this. Also interesting as it coincides with the release of a raft of new Garmin Head units!
The problem my mate gets with pairing with a 500 is that , firstly he has to set his crank length every ride. All his metrics look okay. although it does drop Power/ Watts frequently. But when he gets back indoors and down loads the metrics for Power are absolute rhubarb as though its only been recording one side.
He was given the vectors so he's not really lost out except on training data. Seems to trust the Pedals but not the head unit to work with them.
I don't really know what Firmware is? I ve got a 500 but don't measure power. Every now and again when I sync to Garmin Express and Connect it will tell me there is a new version of the firmware and I just Sync and it updates it. I take it firmware is just the coding/ algorythms the kit uses to calculate its metrics.
My only experience of Power is Virtual Power on the turbo on Trainer Road. When I first started on that my power readings were very questionable. Using a Cyclops Fluid 2, then JSGI and some others pointed out a Beta Curve to use , which gave figures that I found more realistic.
So would a Beta version of the firmware just make adjustments to calculate power by using the other metrics or are the pedals still measuring like a strain gauge?
I would imagine the later or what is the point on having the pedals as Beta curves are okay in doors but there are too many variables outside.
So without sounding Stupid Beta just means version B then? and they will have changed the software in the pedals.0 -
Have a read of
https://forums.garmin.com/showthread.php?321030-Vector-3-50-Firmware-Status-Update
And
https://forums.garmin.com/showthread.php?55481-Low-power-readings
The issue is with the firmware, ie the software the controls the pedals and pods. The problem manifests itself in communication issues between the two pods, normally frequent drop outs from the left hand pedal. The dropouts can be so brief that you may not notice them but they would result in your average power being artificially low, as you had periods of time wher the power was halved. I've been riding with power for almost two years now so have a good feel for what different wattages feel like, which is how I twigged the issue on my vectors. I suspect that someone new to power may not even notice the issue. On the other hand I've had some examples where the power meter has massively under reported for the whole ride. It seems to be intermittent and inconsistent.
My suspicion on why garmin haven't rolled back the firmware is that this is the firmware version that bought cycling dynamics to the vector. Which seems to be the main thrust of their marketing campaign to sell the things. Irrespective of whether they are selling vectors that actually work....
Firmware is the operating system for the pedals, like windows on your laptop. It's the core software that turns the readings from the strain gauges and accelometers into meaningful data to be transmitted to the head unit. A beta version of software is something that's been tested but not fully, so it's should be solid but not yet production ready. Garmin testing is a standing joke with anyone who has one of their products so a beta version will be full of holes I suspect.
Your friends issue sounds like the firmware problem to me. Lower power readings or dropouts are the symptoms. I would advise him not to order a new head unit and to spend some time on the garmin forum. At the very least he should wait until the firmware is released as a production ready version before spending any money on making vector work.0
