@Artem-Lavrynenko - forgot who makes it, but there is a very, very nice timer and GPS tracking display unit that you can put on your boat that does all of this, which might be the best way to go considering that sailing starts are so specialized.
@Dimitrios-Kanellopoulos oh, not intuitive but definitely exists and very useful. Thanks. (I was just lost 5-6 times on a trail run, ha…)
OK, I guess my post is obselete, but may help other spartan users.
@Ville-Halmes yup, pretty much the same thing I experience every time I start an exercise with my HR smart sensor on my Suunto 9. The start up screen shows HR belt has been found and it shows a reasonable HR value. Starting the exercise and no HR is shown for about 30s. Sometimes this shows later after uploading to movescount as zero or 200bpm+ values. All pretty rubbish. This occurred on my first smart sensor with both an old strap and new strap, it also occurs on my new smart sensor on a new strap.
I give myself an answer, since I bought the watch a few weeks ago. With the right settings, without any particular energy apart from the brightness, yesterday I did 6 hours of navigation and I returned home with 40% of battery. Not bad, I had the same average with ambit 3, about 10% / hour
Ok so after much persistence I have an answer from the help line.
The per lap altitude is calculated using maps of the area where you are running but the overall altitude value is based solely on the data collected from the watch ie GPS alone (with the 7m buffer).
This is interesting and helpful.
I should add that there are many things I like about the watch and I feel like a big complainer when that is not the case! Thank you for everyones feedback… especially @Brad_Olwin for a two watch run!
@horvathbotond TBH the Spartan could do with a Barometer widget on a watch face or at least a Baro trend arrows for the past 12 hours that way you can have a quick glance and know what the pressure doing
@sascha I own a Spartan Trainer WHR and I use it with Stryd.
There is the latest firmware. and it works perfect!
You can use and configure Power Zones as described above.
If you run to fast or to slow the watch beeps and vibrates.
Im running with stryd and the Sswhr for more than a half year…
@Jan-Polanec I had the same problem and most of my issue with this is that you have to manually correct the data after upload to Strava every time and thus all your data in Suunto is less accurate. I recommended a Suunto platform improvement that Polar and Garmin already employ on theirs and makes life much better for folks not wanting to spend more $$ on baro watches. There are plenty of people out there that don’t need super precise ascent values during the activity but would like their data after to be correct for analysis. You can see that here and upvote if you think it makes sense: https://forum.suunto.com/topic/4932/suunto-app-platform-native-elevation-correction?_=1600351414011
Ultimately I went with the S9Baro because I have lots of little hills where I live that I want accurate measurement on.
At least regardless of which watch forum you are in, the topic of partially crapped-out POI support applies. It’s just a matter of which POI feature you want and don’t have. Suunto is consistent if nothing else.
Nice to hear, but maybe the 2.8.28 FW is not the solution, but only flashing the watch is what did the trick. Maybe something was messy in your watch and this process clean it.
Btw, happy for you.
@darren_m If too much smoothing is incorporated you won’t see the real-time pace. So it is somewhat of a trade-off, a smooth graph will not reflect the actual changes. FusedSpeed attempts to help with this and I agree with the others.