there shouldn’t be a reason whatsoever for excluding it from transfer to SA
Oh but Suuntolink does not exclude power data, samples are sent to SA service, though summary values (min/max/avg) are indeed missing - https://forum.suunto.com/post/57611
Apparently it doesn’t make much difference at SA service end nor in app itself.
The way I see it, roles and responsibilities between Suuntolink and Suunto App are quite different when comparing data flows during syncing, at least for Ambits.
Suuntolink uses different API endpoint for syncing activities, something specifically crafted only for Ambit line (or at least it seemes it’s currently used only for Ambit line). So Suuntolink is free to send out pretty much anything it can and crafting something SA-compatible out of it is the role for that Amibit-specific-API-endpoint. In a way it’s quite neat, in theory it adds possibility to add Ambit-specific pieces to Suuntolink sync layer without touching that part in mobile apps (less braking changes and test cases for SA, less affected users when something goes wrong). And handling most of that data processing/transforming at server side with a piece that only affects Ambit users has the same benefit, there’s less risk breaking things for majority of users. And generally such proxy layers are also helpful for keeping down the complexity of data models.
But for end users it just means that if something is taken as granted for Spartans/S-line, it might take a looong time (infinity in the worst case) before it gets (re)implented for Ambits in SA.
Why so hard to get a route from SA into the watch?
that’s this recently discussed cache issue either in the watch or SA, I’m not sure… (sorry for being offtopic here).
I create a comoletely new route, completely new name, toggle add to watch, sync and when I want to use this route it shows me any random earlier created route… did that 4 times, 4 different random earlier routes. The data is always correct, but the route track is wrong… only the 5th attempt finally worked
I am new to Suunto. What is the difference between Running Performance Index and est. VO2max. (When looking on the run in Movescount, recorded with Ambit3 Peak).
Thanks very much for your help.
As my understanding Running Performance Index is the estimated VO2max calculated with Firstbeat algorithms. but what is est. VO2?
This is an old thread but,
Running performance From ambit3 accounts for your vo2 max fitness AND running efficiency. You can do that easily and much more accurately now with stryd, lookup Running Efficiency formula.
Example two runners can have different vo2 max but finish race at same time, difference is running efficiency(mostly).
They use specific weight lifting trainings to your core and leg muscles to improve muscular oxygen absorption efficiency (leg) and running form(coremuscles), particularly hem strings for people genetically predisposed for such injuries (for those who have their genome sequenced, there is a specific gene that if you don’t have many copies of it you are prone to it)
vo2 max just aerobic fitness (you max input of oxygen) it is estimated from average value of many factors.
MC Est vo2 is (Was) estimation of your current oxygen intake. Sort of like IF but 100% is for for 12minutes instead an hour on TP.
@aqzaxs I kept the lowest HR on whichever value the calibration test updated. I don’t think these test are only to detect the lowest value, hence there is a clear calibration result in the service menu, it also detect and store more data in the watch that is not visible for us. Maybe someone knows more about it, I surely don’t.
Can’t recall exactly, but if you modify the value through Movescount then after you sync your watch the tests will return calibration phase (not 100% sure though).
@jsuarez The message from the OP on this particular post was referring to the S9B stating this Hope in the future the S9B can have something like this apps, so much flexibility (through suunto plus?), so I answered. Since this was directly addressing the S9B there was no need to qualify the SuuntoPlus statements.
A bit late noticing this but I was a little disappointed with the battery life of my vertical. I expected about 10hrs on GPS best but usually get about 8. When I queried this with Suunto the response was that linking it to a HR belt knocks the duration down (and to a foot pod or cadence sensor), so using the HR belt 8 hrs was about right. I tried using it on GPS good setting instead but the watch lost GPS signal a few times part way through runs and never reacquired it - in fact I had to reset the GPS before the next training session before it would get a signal. The watch kept recording time, altitude and distance (distance presumably from fused speed) but on download the track just ended part way through the route. This didn’t occur in woodland or built up areas either, it happened in open fell country.
OK, I see reasons for having more screens than available so I stand corrected but @Mff73 may have solved the issue in an ingenious way…I will have to test this out as I would like multiple graphs sometimes as well. One change I would like to see is the ability to scale the graph as we can scale the route on the Navigation page. Kudos to all of you for the great responses!
@Umer-Javed sounds good! my watch also showed the ambient pressure too high. compared to other ambits. at around 2hPa. when altitude is the same, the pressure should also be the same.
(but i have to say, it’s a “nice” to have, when it fits, specially when you are using the watch without GPS too. (i don’t track every evening hike). so it’s nice to look on your phone in a brake while hiking. and see if the barometer fits the next airport value. but i would not care anymore about it. over time, it could get inaccurate too.
FusedAlti uses the GPS to calibrate the barometer. so even if your barometer is not working correctly the gps calibrates it to the same value. but i am glad i bought it. i think such a simple “workhorse” watch will never be build again.
@ivansalas Also, if it looks like you’re setting off without a good fix, attach the watch to the top/shoulder strap of a rucksack (if anyone’s got one) with its face getting as much sky as possible on the ascent. That both improves the watch antenna-satellite geometry vs swinging by your side AND means it will be harder for you to get annoyed at seeing the wrong altitude every time you glance at your wrist.
Re-don the watch when you notice it’s getting things right or when your friends get fed up with your checking.