Previously Vo2max was calculated via FirstBeat license. Thats no longer the case already with Race. Its Suunto own algo.
As you already know Race has some new features such as Race estimations and sleep stages. Those come from some licenses with other providers.
Suunto atm is at the stage that is developing / evaluating all in house (or at least wants to).
So, its a matter of internal (and external fieldtesting, public surveys) evaluation. So to give an example:
Suunto has developed Running marathon estimations. They work well. They benchmark those against FB , GoMore and other providers. If the result is good they will flip the switch to their own. Thats a no brainer. But when they want to release a model with those features, ie the Race , on launch they can go with whatever provider works better and pay the price to them (per unit usually).
You as users / consumers should keep in mind that Suunto is trying to provide a good solution to increase the consumer satisfaction based on factors such as launch timing, license expiration etc.
To be specific on the following update for the Vertical for example, the resources will be own algo. Same most probably is for running stats estimations (marathon time etc). That means that Suunto will have 2 different algos out there (2 watches with different algos ) and at some point 1 of the 2 algos will align to the best result.
To be honest the running time estimations (marathon etc) work better for me on the tests with SV with the Suunto in house algos than to what Race is using. That doesn’t mean it works better for all.
Bottomline, things will get aligned , but needs time.
I am just hopping on the sleep tracking issue with my Suunto Race. The sleep tracking worked great for the first two weeks, then completely stopped. I didn’t change any settings. I have restarted the watch and after three days of no sleep tracking, did a factory reset yesterday. Still no sleep tracking last night. Somehow it is still tracking my naps though. Kind of frustrated, not sure if I should return the watch or not, I really like it. I contacted Suunto support this morning and they stated it is a known bug and a fix is coming soon. Anybody else having a similar issue or just my device?
@Shuhite I am from Canada as well, and had to return my first Race (defective crown). I had the same experience–I received the refund quickly after shipping it back, and like you it was for the pre-tax amount. I used the chat (I try to use it in the morning). I had them create a ticket about it (and asked for the ticket number–in my experience then don’t volunteer the ticket number). I had heard nothing back after a couple days after the initial chat, so I nagged them again citing the ticket number. The next day I received the for the tax portion too.
Exactly and that’s why I think his observation that the Race reports something around 25 as HRV, tracking overnight and his morning readings are much higher are not comparable (and the Race values may be correct?)
@Brad_Olwin I dare 😅 to confirm, that the sleep tracking works with the nightly resting HR - third night with it is spot on again, so it seems to work fine for me. Also did a nap and the race got it tracked fine. Really great work 😀
@TrailEyes Well we don’t know do we?..I prefer transparency and others maintain secrecy. I neither hide the fact that I am not young, nor do I hide the fact that I am no longer fast, that boat sailed away about 40 years ago:)
I came to Suunto with the Race, after 10 years with Garmin.
I don’t think Suunto emphasises this positive point enough. I think the altimetry is better managed by Suunto, but Suunto doesn’t say it loudly enough.
When I look at the manual for my Race for the FusedAlti™ tools, it says :
“FusedAlti™ provides an altitude reading that is a combination of GPS and barometric altitude. It minimizes the effect of temporary and offset errors in the final altitude reading.
By default, altitude is measured with FusedAlti during exercises that use GPS and during navigation. When GPS is switched off, altitude is measured with the barometric sensor.”
And when I look at the manual for the Altimeter and Barometer widget, it says, among other things :
" Automatic alti-baro profile: Weather and altitude changes both cause a change in air pressure. To handle this, Suunto Race automatically switches between interpreting changes in air pressure as altitude or weather changes based on your movement.
If your watch senses vertical movement, it switches to measuring altitude. When you are viewing the altitude graph, it is updated with a maximum delay of 10 seconds.
If you are at a constant altitude (less than 5 meters of vertical movement within 12 minutes), your watch interprets air pressure changes as weather changes and adjusts the barometer graph accordingly.
It’s a shame that the two pieces of information aren’t available in the same place, I think that would be beneficial.
And I don’t think there’s any mention of the fact that FusedAlti can update past altitudes if it deems it necessary. I think I’ve understood that’s how it works from what you’ve said.
This is a big difference from Garmin, which will never touch the past minutes of an activity. If you do a loop and come back to the exact same place with a 2000m difference (recorded : +4000d+ and -2000d-) Garmin doesn’t get offended at all ; even if a Garmin function is supposed to manage the altimeter with crazy intelligence…
@DrSilverthorn with the exception of one blip at the beginning of one run, it’s worked perfectly fine for me. HR for similar runs using Fenix are very close to this (can’t completely compare due to weather/alcohol intake the previous night).
@GiPFELKiND there are different terminologies, but they basically mean the same. Some refer to them as ventilatory thresholds (VT1, VT2), others as lactate thresholds (LT1, LT2). And MLSS (maximial lactate steady state) as well as critical power/speed are also used, which are different approaches to the upper threshold.
Intervals with active recovery on the treadmill. I like it because of the predefined pace and time I choose with a touch on the cockpit.
Runn, the treadmill sensor, captures the speed and cadence and broadcasts the data via bluetooth to the Suunto Spartan Ultra. Pictures 1 and 2 are showing the data. Cadence is not accurate, but usable.
Picture 3 is showing the real cadence, captured by an IR sensor which is counting the foot steps and broadcasts the data via ANT+ dongle (connected to a Raspberry PI) to a Garmin Forerunner 255. These data are accurate and can be taken for a special cadence training.
Runn gives 170 spm average, the IR sensor 178 spm average, measured over the complete time of the treadmill training.
The Forerunner gives me also the ascent of a treadmill training, because of the Garmin IQ data field for the Runn. This is missing for Suunto watches and a request via email to create a Suunto Plus app was not successful until now.
@SuuntoR Sorry, you are correct. It dims, but in my case it’s still easily readible, unless I’m in bright sun (which is rare where I live this time of the year, I didn’t have Amoled in the summer). The Suunto Race AOD is proper AOD.
…and I was also wrong. This “true always on display” seems only to work when it’s dark enough. I hadn’t ran in the day time until today. So it seems to use ambient sensor or something. In the day on workout mode, the display also on SR dims. But I think the numbers are clear also when it dims (where I live also not that sunny anymore) and little wrist turn works quickly. Its been couple of months since I had an amoled Garmin watch, so it was more sunny. But still I would say Garmin watches dim more than SR, or maybe I remember wrong and being too harsh on Garmin about this feature 😅 pictures with SR on full brightness and “dim mode” attached.