Race 2 accuracy

Egika

shamilt1

@Egika Thank you ️

jjpaz

@EzioAuditore I am not aware, that anything has been changed in the distance measurement with the recent update.
And I have also seen the Race 2 measuring less than Vertical 2. Just I have not made a bug from this, as I am not sure, it is one. A slightly less distance does not affect me in a negative way. Plus it is not clear, if less is actually wrong…

Hi @egika

Time ago, when I started using Race 2, I opened a thread with my tests and results comparing against Vertical and Race S.
Here is an example, if you want (and have time): https://forum.suunto.com/topic/14375/race-2-gps-cadence-and-distance-accuracy-vs-previous-suunto-models/63

The behavior is always the same (and it’s replicable and easy to verify) so there’s something different in Race 2 in comparison to other Suunto watches. I don’t know if it’s better or worse but different for sure.

Egika

@jjpaz thank you! I added your information

Finnjf

@Egika adding my N of one, I also find it measures consistently different from every other watched I’ve used (a few from COROS, Garmin, and other Suunto watches, the Vertical 2, Race S, and Race). More telling, though, is those other watches all measure very close to my measuring wheel. The Race 2 measures shorter than my wheel, so in my experience, the Race 2 does indeed measure short. Thanks for your help on this!

jjpaz

@egika Yesterday I tried Race 2 with the new software and the behavior is the same regarding distances and paces as previous software:

Left: raw GPS distance showed (10.17km).
Right: postprocessed final distance showed (10.01km).

First one is the GPS data recorded distance (similar to the recorded by other devices and the “corrected distance” by Strava for example. Second one is the “filtered” distance saved in FIT file data and showed by the watch ((tipically the other watches would show 10.16km with the 10.17km raw distance).

First one is always similar in all the devices. Second one only differs (shortened, 1%-1.5%) in Race 2. In every activity, both running, walking or riding the bike.
So it seems Race 2 performs a different data processing than his other “brothers”.

dreamer_

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.

shamilt1

@dreamer_ Mine is the Race 2 steel version and it seems to measure short.

leafs93

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 .

Svenning

@leafs93 I can confirm that. Same experience here.
Time to settle this with a measuring wheel.;o)