Race 2 accuracy

[isaac.net]

@EzioAuditore and once again it must be remembered that the GPS data collection of the Race 2 is very good, the problem comes later with the software processing of the information to calculate the distance to be displayed.

[YoeChr]

@isaac.net Is the postprocessing problem only visible in Suunto App, or also on outlets like Strava and TrainingPeaks?

[isaac.net]

@YoeChr the post-processing issue is visible on all platforms that import activity data from Suunto, as this is the total distance data that is sent. In Strava, this can be corrected using the “Correct distance” option for the activity, but this is a web-only option and requires manual execution.

[Egika]

The new update of today introduces a different distance calculation for Race 2.
It should solve the under-reporting of distance.

[Svenning]

Thanks @Egika! Great! I’ll test the GPS tonight right away.

[GiPFELKiND]

@Egika now we run a half Marathon and the Race 2 calculates a Marathon? I never saw a distance Problem at the Vertical 2

[Egika]

@GiPFELKiND said:

@Egika now we run a half Marathon and the Race 2 calculates a Marathon? I never saw a distance Problem at the Vertical 2

this thread is about Race 2.

[jjorgemoura]

@Egika As a Race 2 user, these are good news.
As a Software Engineer, I’m wondering and curious why Race 2 and Vertical 2 have different methods of calculate and/or report distance. Unless is an Hardware related issue.

[isazi]

@jjorgemoura different antenna design.

[isaac.net]

I did a test today: a 9.50km walk (final distance on the Race 2). Strava, after applying the distance correction, showed 9.51km, the same on the Sportstracker map. So, this first test seems promising for resolving the issue

P.S.: If the watch had a live tracking system integrated with the Suunto app itself, it would be perfect for me.

[Finnjf]

Chiming in after the update: SO far the accuracy seems improved in my testing. Over the past two days distance has matched that of other watches (Garmin Fenix 8, COROS Pace 4), and what I would expect from the routes I ran. Hopefully the distance accuracy issue has been resolved!

[MdzOtt]

I understand that the distance accuracy used to affect running more than other activities. I don’t run, but I noticed that my R2 was always a bit short on distance when cycling. Not much, but noticable. Around 300 m on a 50 km ride. It was somewhat frustrating when my ride was just 50.2 km and it was reported as 49.9 (as if I did not reach my target ).
The latest update improved the accuracy. It is still a wee bit short, but it seems that it might be missing <100 m (70-80) (still on a 50 km loop).
In all cases, I compare the Strava distance, a Garmin (Edge Explore 2), and R2. The difference might be also due to different ways each tool treats stops and pauses (I.e., how much distance you have to move or what speed you need to reach before they assume that you are moving again).

[miszczif]

I recently “upgraded” from Vertical to Suunto Race 2 Titanium on bargain (my friend won halfmarathon and it was a prize) But sadly the GPS is sub-par compared to Veritcal.

I did two sessions with my friend who uses Vertical1
Yesterday it was 15x400m reps on road measured with measuring wheel.
Vertical shows most of the reps around 395-400m. My Race2?
385-393m, this is very dissapointing.
4x2k reps on measured road: 1.97, 1.99, 1.98, 1.99
And this was after the recent update.

As a longtime suunto user (Ambit3r, suunto9, suunto9 peak, suunto vertical, suunto race2)
This is the first time I had any doubts about gps accuracy.

[MarTej_cz]

@MdzOtt
Rozdíl 300m na 50km je úplné nic
Ještě k tomu na kole kde je větší rychlost pohybu…
R2- jiný GPS čip
G- jiný GPS čip
S- jiný GPS čip
Každý z nich má úplně algoritmus. A rychlosti správcování dát.

[Svenning]

Test run today with a Garmin.
Race2 passed with flying colors.
A huge thanks to the developers.
Great job, guys.

[MdzOtt]

@MarTej_cz said:

@MdzOtt
Rozdíl 300m na 50km je úplné nic

I fully agree