Race 2 accuracy
-
I was thinking this was about the titanium Race 2 because It seems you all are comparing the Race 2 titanium with the Vertical 2 titanium.
But the thing is I have the Race 2 steel and I’m seeing a little discrepancy of what I have recorded with Garmin. But my watch is very new (2 days) and I need much further testing.
There’s also something very strange with the Race 2 (at this very new moment for now). When I import a GPX track (downloaded from Garmin Connect) into Komoot to have the turn-by-turn indications while navigating with the Race 2, is like the indications are a bit later than they should (just some few seconds). When there’s a roundabout, or a turn it seems the watch pop-ups the remaining indication a bit later or even after the turn or roundabout.
I need more testing but I’m posting this because I don’t know if it can be related with the issue you are posting here. And the thing is that those tracks are working fine in Garmin and other brands.
Or perhaps does not have sense at all, but using the same track for both the Race 2 and the Vertical 2, perhaps there’s a mechanism to see if there’s any delay with the GNSS of the Race 2.
I’d be interesting if someone could test the navigation with the same track and indications with the Race 2 and the Vertical 2 to see if there are GNSS discrepancies. -
@dreamer_ Mine is the Race 2 steel version and it seems to measure short.
-
And I thought I was the only one having this issue. I compare my usual route with all my other watches which include apex 4, pace pro , pace 4, ultra 2, polar grit x2 and Suunto race 2 invariably falls short in terms of distance. Not by a lot but about 100-150m shorter for a 10km run .
-
@leafs93 I can confirm that. Same experience here.
Time to settle this with a measuring wheel.;o) -
I can add to and confirm too short distance here as well. This is near ideal view to the sky.
I get between 0,5& - 1% too short. This is measured over tracks I have ran a thousand times and confirmed with multiple various gadgets.
I’m with an R2 titanium.
-
I have confirmation, that Race2 indeed measures a little short, compared to other models.
cannot share more details, but the watch works as designed.t6, S6, Elementum Terra, Ambit 3 Sapphire, Spartan Ultra Copper, Traverse Alpha, S7 Graphite LE, S9B Ambassador, S9P Titanium, S9PP Titanium, Vertical All Black, Race Titanium Charcoal, Race S Titanium Courtney, Run Lime, Race 2, Vertical 2 Titanium
-
@Egika said in Race 2 accuracy:
I have confirmation, that Race2 indeed measures a little short, compared to other models.
cannot share more details, but the watch works as designed.Thanks for the reply!
-
@Egika I’m a bit confused by this… does this mean there’s likely to be a fix or are you saying it doesn’t need fixing?
Race 2, Forerunner 265, Huawei GT6 Pro.
-
@jjpaz I have a large number of trail runs with Race2 and V2 and they are essentially identical. I can share data, several different firmware and from 45 min to 7h trail runs. I am in the US with mostly open skies. Part of the observations may depend on the environment as I believe all of you that see shorter distances with R2. However, maybe not a firmware bug but maybe design differences including antennas. I always see fewer satellites connected to R2 than V1 or V2. Could impact distance when GPS conditions are more challenging.
-
@shamilt1 this will likely not change.
-
@Egika So unless I’m reading this wrong, Suunto either know that it measures distance a little short, but it was designed to do so…( I can’t understand why this would be the case!) or it’s not significant enough to address in an update. Personally I think it’s disappointing that it won’t be addressed.
-
@shamilt1 said in Race 2 accuracy:
Suunto either know that it measures distance a little short
It measures shorter than the other models. The question is is it more accurate, though?
-
@2b2bff I wrote about this before, but from my n=1 sample size, the Race 2 measures short, and is further from true distances than other watches from Suunto, COROS, and Garmin. I’ve measured it against a measuring wheel. Also, recent race performances by elites wearing the Race 2 in certified road races also have it measuring a bit shorter than race distances.
-
@2b2bff said in Race 2 accuracy:
It measures shorter than the other models. The question is is it more accurate, though?
Nordic Walking on a measured loop of 2260 m:
March 31
Loop Race S Garmin 955 1 2277 m 2259 m 2 2263 m 2263 m 3 2267 m 2262 m 4 2255 m 2267 m April 19
Loop Race 2 Garmin 955 1 2244 m 2261 m 2 2241 m 2263 m 3 2244 m 2267 m 4 2242 m 2272 m 5 2238 m 2265 m On measured straight paths, errors were smaller.
-
@2b2bff I don’t think so…surely all the other devices can’t be wrong?
Additionally, when I plot a route on footpath or the Suunto app, the Race 2 always returns a shorter distance than the plotted route too…my other watches don’t. This is mainly on canal towpaths so not a lot of cutting corners going on…but plenty of weaving round walkers etc. that could add a few meters.
But it appears it’s not going to be looked at and I’m struggling to see why this would be.
-
@shamilt1 you cannot address it easily. You cannot add 0.5% distance to everything, because there are situations where it does not measure short.
-
@shamilt1 ran a marathon at the weekend and measured 45metres out (short)…which seems very decent, especially with some distance of that being spent on narrow streets with tallish buildings.
My km auto-lap buzzes were generally bang on, or up to maybe within 10-20metres when passing the course distance markers through until at least 30km…(I stopped caring/noticing beyond that!).
-
@Nigel-Taylor-0 I’d certainly settle for that over such a distance. In comparison, my last run was 14k and my Race 2 measured 90 meters shorter than my other watch, so not as good as you got.
I understand it may not be an easy fix, but let’s hope the boffins decide to take on the challenge and get it sorted…it’s the one thing that bugs me about this otherwise excellent watch. -
Hi,
To contribute to the thread, today I did a mountain bike ride with my Race 2 Titanium and a Garmin 530. The difference was only 40 meters: Race 2, 30.98km vs Garmin 530, 31.02km.
Regards -
I’m commenting to myself to point out that, however, the distance after applying Strava’s distance correction increased to 31.45 km. I assume Strava performs the correction using 3D distance (taking into account the terrain’s elevation), which in this case was 840 m of positive elevation gain.
Related to this, does anyone know if this parameter can be applied to the distance calculation? I haven’t seen it on Suunto, but Garmin has the option, although it’s disabled by default.
Regards
