if you can ask any friend or relative to help you:
setup Suunto App on their smartphone,
create an account there
create an account in partner tool, for example https://runalyze.com/, it’s free
setup connection with this third-party service in Suunto App
in SuuntoLink login to your new Suunto App account
record some workout and sync it via SuuntoLink
= you’ll see your workout and get track in Runalyze
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.
@theguyfromthesummit The storm alarm will go off when the pressure drops sufficiently. I believe that do not disturb will turn that off but I am not totally sure. Mine will go off a day or two before storms as we have major fronts come through that drop the air pressure. I should add that my two S9 Baros and my A3P ALL simultaneously Storm Alarm at home. At least I know they are consistent:)
I would argue for the Sunrise/Sunset it is there and the only watch that you can customize the extent you want for this is the S7. If you argue that the watch faces on the S9 have no ability to customize, I am in total agreement on this and there are posts long ago asking for this. I suspect it will never happen. For example, a number of the S9 watch faces duplicate data, the Hero face has a graphical display of battery charge and a battery charge indicator as well. I do not understand the logic in this but…it is not going to change, unfortunately.
Exactly what @andrasveres links to you.
Suuntolink should do exactly what you think it didn’t : sync activity from watch to Suunto app cloud + sync your legacy watch settings and routes and POIs from MC Web to your watch.
Sure it is not that simple, but it is like that.
@titus_fromnewtown I feel your disappointment, but if I think what were the premises before the release of SL4… well, it could have been even worse. I have recently upgraded my A1 with an A3P and I am very satisfied and happy to keep doing the same things I did. I want to believe that Suunto has made a great effort to listen to user feedback.
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).
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.