Suunto 5

[dulko79]

I have read in dcrainmaker’s pre-review that 24/7 HR tracking is significant load for battery - approx. 3 % per hour. Has anyone else noticed such behaviour? Is this normal or temporary problem due to beta software and will be fixed later with updates?

[Fiox89]

@dulko79 from what I know is “expected” behavior which also happens on other models too. Continuous heart rate readings requires a lot of battery power, as does sleep monitoring. Maybe there will be more reliable information soon

[NicolasP]

@dulko79 I have a SST and I think that he said the same. However I can confirm that I have never experienced such battery consumption.

[Dimitrios Kanellopoulos]

Nope for sure not 3%

[Saketo Nemo]

@dulko79
Ray says that ? Mmmm…very strange !

[dulko79]

@Saketo-Nemo was that a serious or sarcastic question?

[Saketo Nemo]

@dulko79 second one

[Luís Pinto]

https://the5krunner.com/2019/06/12/suunto-5-review/

[Brad_Olwin]

@Dimitrios-Kanellopoulos said in Suunto 5:

Nope for sure not 3%

Agreed not 3%

[dulko79]

Agreed not 3 %

[whl_89]

I bought my girlfriend a s5 and after a fews runs i am a bit confused because the ascent recorded by the watch is about 50% of the real ascent. I use the ssu. I know s5 has no baro but at least it should record the GPS ascent which is about the same i her from the ssu. Is this a known issue?

[Saketo Nemo]

Have you tried a full vertical track, without d- ?
Going from 300m to 800m should results 500d+, in S5 and also in SSU.

In tracks where there are many up and down you will not have the same results because GPS device store d+ only each 7m gained, BARO device each 3m.

btw, 50% less is too much…

[suzzlo]

@whl_89 Same here with SSSW (no baro). Are ascend step sort? Usually in my 10-15k run with +400m always have less than +200m

[whl_89]

@Saketo-Nemo i just made two runs with ups and downs but both around 50% of actual ascent. I mean i am aware of the non existing baro in s5 but this huge differences are really bad for a 300€ device

[whl_89]

@suzzlo mixed ascents but shouldnt there bei an algorithm to overcome those recording gaps within those 7m?

[Saketo Nemo]

just my curiosity: can you share the link of the two activity ? (also in pvt if you want)

[whl_89]

@Saketo-Nemo I will upload them later

[whl_89]

@Saketo-Nemo

S5:
link text

SSU:
link text

[Dušan Ković]

Out of curiosity, I wanted to see the altitude diference, so I imported both to QS:

S5:

SSU:

Both have similar graph shape and are in similar altitude ranges, but SSU seems a bit jagged compared to the S5 which looks smooth. Not sure which one is correct. But I’m guessing that SSU has more altitude difference because all those small spikes, also bigger drops in altitude on multiple places.

[whl_89]

@Dušan-Ković If i plan this route in komoot or Suunto App altitude differences of ssu is quite correct and s5 ist about 50%. SSU works fine i think