Black grid… 44.80489°N 20.37743°E

@maxll Was suggested here as well https://forum.suunto.com/post/146463

@sky-runner maybe a silly idea, but what about using multisport ? entering an aid station you switch to any mode you customized for “”“pause”“” at station, and switchback to main one when going out ? if times data are setup correctely, you can have total time and/or current activity time (run or pause time in you case), previous pause and previous “stats”, etc… and you will have all details in SA after.

Cables to the office this week.

@maszop said in Altitude/elevation fallback to GPS: Altimeter data from GPS alone is usually useless. There’s no point arguing about it. you’re right, the are no reasons to replay to you.

@Cezary-Śliwiński I don’t think anything has gone wrong. If Garmin suits you better, get a Garmin. I came to Suunto from a Fenix. I prefer the Suunto, just get what is best for you.

@freeheeler Thanks google in fact .

@Prenj That seems about right, you can’t set up both the compass and the daylight on the face.

GPS is essential for calculating Running Power. It is stated in the watch manual as well: Suunto 9 Peak Pro measures running power from the wrist combining GPS and barometric data. Ensure your weight is correct in the watch settings for the algorithm to work properly. Your weight is set at Settings > General > Personal > Weight.

@sky-runner said in New Suunto Run Watch interface on older models (Vertical, Race, Race S)?: Spinning the crown is difficult when wearing gloves Not on a Coros watch, since the crown friction is much lower than on Suunto offerings <-- My experience: Pace 2 versus Race S. The Coros was a breeze to use even with thick finger gloves; did not try with ski mittens though… Instead I’d say that having to keep the crown pushed in for several seconds to scroll backwards, the Suunto way, is the real elephant in the room. As for other possible transfers from the Run watch to older models, sure! I would like sensible ones, but please not the ‘Fluff’. Back in 2013/2014 Garmin introduced Ground Contact Time on the FR620 and FR920XT, as well as Vertical Oscillation. This, together with the old (useful) data point Cadence, they called Running Dynamics. We spent countless hours on the forum discussing possible ways to make the numbers actionable, with little success. Basically it boiled down to “run faster” to lower the GCT and/or switch from heel striking to mid- or forefoot landing. VO is also lowered by “running faster”, but that’s about it. ‘You is You’ when it comes to running technique, and only mileage and experience will make your body adjust to the safest and most energy efficient running style for Your Body. Same goes for the Ground Contact Time Balance which Garmin squeezed into the RD set in 2015 (not backported to the FR620, you had to buy the new FR630…) The forum discussions were hilarious, and absolutely Zero clarification from Garmin. For example: 51-49 - meaning the GCT was slightly longer on the left foot - did that signify that something in the left leg department (hip, thigh, ankle etc) was weaker, injured or whatever than the right area, OR that your body favoured the left side because the right side was weaker, injured… etc. etc. The suggestions for how to balance a possible ‘imbalance’ took on surreal tones when one of the moderators claimed to having achieved 50-50 by holding one of the arms straight out from the body - this while running… I certainly would not buy a new version Suunto watch based on such frivolous additions.

@ruslan-jefremov часы без пульсометра? В таком случае 0 калорий ожидаемый результат. If no HR is being measured, 0 calories is an expected result. Проверьте показания давления в вашем регионе. Поскольку часы отталкиваются от барометрических данных, штормовое предупреждение может появиться и вне шторма. Если скачков давления в регионе не наблюдалось, можно попробовать почистить сенсор - несколько примеров можно найти на форуме. В крайнем случае стоит обратиться в поддержку. Check baro graphs in your region, there might have been pressure fluctuations with an actual storm. In case there were no significant changes you can maybe try to clean the baro holes. If nothing helps, you can try to contact support.

A bigger problem (albeit related) is losing the correct direction when the route intersects. For example, figure 8 or other variations of the route intersect.

@Mattg576 maybe it’s implemented differently on devices with a crown.

@Maryn @Egika Ok it’s good it works, it was because I tried it sitting at the desk without moving the handle. With a value of 0, you cannot modify anything. mistake on my part, thanks for your help. Have a good day guys

ooh wait yes that’s seems to be the orthostatic test from polar… @isazi in https://support.polar.com/en/support/the_what_and_how_of_orthostatic_test by the section “How do I do an orthostatic test?” the description is quite the same as the fitness test. I’ll get a deeper look on it. I’m little bit confused on why only the v02max is evaluated here, regarding about all we discussed before and the concept of evaluation of the value which is exclusive by red-zone…

@Brad_Olwin Yes, I know this one. I use the orange 26 mm for my 7X and for the SR I bought the Coros one which comes with three pins. So, I’ll buy the same Garmin black nylon one for my SR as well.

@Dan-Cantir Indeed, I changed “location access” to “Always”, and since then the weather forecast has Benn updated automatically multiple times. Thank you. I don’t see why this is necessary (at least I would accommodate having a forecast for the last location where I opened the app), but for now it works and I don’t need to start a synchronisation from my watch anymore.

@Mff73 then it means no battery data, likely Ambit didn’t write it or it wasn’t stored

Maybe to avoid confusion, the option I’m thinking about should be called autobreak to distinguish it from autopause.

@gi0vanni I need phone and SA version, you can send me a PM, thanks.