Me and my wife (Venu2) recorded a walk. Mine 7.58km, her5.86km O_o
From a gpx file of the route found on a site it's clear that her distance is the good one.
Recorded with all system and 3d velocity and 3d distance on
Me and my wife (Venu2) recorded a walk. Mine 7.58km, her5.86km O_o
From a gpx file of the route found on a site it's clear that her distance is the good one.
Recorded with all system and 3d velocity and 3d distance on
Yeah, turn that 3D off and try again. I am interested if it will be shorter than on Venu2 after that...in Auto Select mode.
I have the known distance (6.3km) I used to run and logged with multiple watches…
I had a distance issue I discussed on another thread. To summarize, my morning walk under clear sky (which I have done many times) started showing 6-8% shorter distance after updates 12.23 and on (including…
Yeah, turn that 3D off and try again. I am interested if it will be shorter than on Venu2 after that...in Auto Select mode.
I have the known distance (6.3km) I used to run and logged with multiple watches, including V800 and Timex GPS with SiRFStar III chip I think which cannot be more precise.
I will try to do 3 same runs this week - Auto Select, All System and GPS only to compare recorded distances. No newer firmware in that period for sure.
On the MTB ride I mentioned on the altitude post my FR955 has shown 19.84km (Auto Select) , Grit X 20.10km. Same 20.10 was shown in Komoot on my phone, on friend's Venu and Suunto 9.
The other thing that bothers me is the recorded track itself in Garmin Connect. The track is all the way couple meters by the road or path, over the roofs of the houses or trees for example. When I check the same activity synced to Strava...it is spot on the road/path.
So I went for 2 runs/jogs today with FR955 Solar and Polar V800. I forgot to charge the Grit X.
Same route, same starting and finishing point, one run after another.
First run:
Garmin FR955 (Auto Select) - 6.41km, max altitude 420m, V800 (GPS only) - 6.45km, max altitude 432m. All glued up, unused for over a month, Polar was brilliant, altitude wise in the first run. I calibrated Garmin yesterday at about 250m. Again, calibrated it manually at 432m today. FR955 started to be behind V800 for about 30m after the first km.
Second run:
Garmin FR955 (All Systems) - 6.40km, max altitude 416m, V800 - 6.36km, max altitude 436m. Calibrated it again, for the second time today. HOW CAN IT BE 16M OFF, JUST A HALF AN HOUR AFTER THE CALIBRATION. It was more off than before calibration. Sunny day, no weather change.
This time FR955 was ahead of Polar all the time...about 20m more, then Polar lost another 20 in the last km somewhere.
I was convinced that Auto Select on FR955 on 12.27 was rubbish, but now I don't know... now that barometer bothers me more.
I wasn't keeping an eye on the battery, but after two runs - about 2:12 (yes, I know I am slow;)) the battery went from I think 72% to 61%. First run Auto select, second All systems, no music, H7 HRM over bluetooth.
I will repeat the same test with Garmin and Grit X if weather is going to be fine in 2 days. Now rest time.
BTW, I also noticed after every longer and harder session my recovery time is always 96h. I don't know if that is the max. number. Is someone from Garmin fan of Liam Neeson...or Luc Besson
I had a distance issue I discussed on another thread. To summarize, my morning walk under clear sky (which I have done many times) started showing 6-8% shorter distance after updates 12.23 and on (including 12.27). It took me a while to figure it out but this is what is going on:
1. All the measurements are in All+ Multiband, 3D distance and speed off, every second, walk activity.
2. When I reduce my left arm motion (not motionless but a smaller swing), the 955 will show the correct distance. Also, the GPX and FIT distances are nearly identical.
3. When I use my natural arm motion, the watch distance is consistently short by about 6-8%. The GPX (exported to Strava or other programs) shows the correct distance, but the FIT distance (also on Strava) is the same as the one shown on the watch.
4. My Fenix 7s SS shows the correct distance independent of arm motion, or anything else I throw at it....
There was a similar phenomenon discussed on the Fenix 6 forum where the distance discrepancy was attributed to the other sensors (accelerometer, etc.) distance compensation. However, it never concluded whether it was a HW or SW issue.
I raised this issue with customer support. It was sent to engineering but haven't heard from them yet.
That's interesting...but I had shorter distance while the watch was mounted on a bike. In August, on previous firmware without SatIQ/Auto Select, while it was on All systems the distance was 20.07...that is closer to 20.1 what most other devices had shown. Two days ago, same setup and same route, with Auto select, as I mentioned it had shown 19.84km. I had other bike/run/walks where I see shorter distances with Auto select. I will change it to all systems till the next, I hope, improved firmware/algorithm.
I had another same run/walk today. At 432m today it showed 412m. Everytime less and less.
Interesting thing is I calibrated the altitude at that point to 432, it wrote calibration completed, waited for couple of seconds, checked again - 411m after calibration.
It only showed the correct altitude after the second calibration. The distance with Smart system is within 10m, but less than last time while Polar Grit X had approximate 20m, 30 more than Garmin.