05-28-2016 15:56
05-28-2016 15:56
here is a comparison of a walk activity I did today to see how accurate my Blaze is compared to a $500.00 Garmin fenix3. I have been fine tuning the stride length on my Blaze over the past week by doing walks amd calculating the stride length using the distance and step count, and getting an average over a weeks worth of walks.
The Garmin has built in GPS with GLONASS (which I have turned on), and it is pretty accurate. With this walk the distance between the Blaze and the fenix3 is less than a tenth of a mile, and I have adjusted my stride lenght based on the distance from the fenix3 and the step count from the blaze.
Also, I wore the Garmin chest strap monitor during this walk to compare how accurate the Blaze optical sensor was compared to a chest strap monitor. It was within 1 BPM most of the time, and never more than 2 BPM at any time.
Here are the screen shots for each...
Fitbit Blaze
Garmin fenix3
05-29-2016 05:49
05-29-2016 05:49
Good to see you around @bcalvanese and thank you for taking the time to do this and sharing it with us!
Help others by giving votes and marking helpful solutions as Accepted
05-29-2016 18:51
05-29-2016 18:51
Thanks @FerdinandFitbit .
The Garmins are extremely buggie as far as the software goes, and the only thing that works well on the fenix3 is the GPS and heart rate monitor (chest strap), so at least I found something I can use it for.
I actually tried the new Garmin vivoactive HR and returned it within a few hours due to buggieness (if thats a word), and got the Blaze.
05-30-2016 00:33
05-30-2016 00:33
06-02-2016 04:42
06-02-2016 04:42
Agree with Garmin and their sloppy software. It seems that they always rush products for release and then clean up afterwards. Not a good way to go about it. People complaint that Fitbit or Polar take too long to release software. Well, I'd rather them get it right prior to release rather than have it be buggy.