S9 barometer problems
-
@Dimitrios-Kanellopoulos And if I remember the earlier update was in earlier in the spring.
-
@Anssi-Auvinen correct.
-
@Dimitrios-Kanellopoulos : It might be useful to check this activity, that showed a similar behaviour on Monday: https://quantified-self.io/user/b8N0uPCCIxbEKbOPC3wYZMdRP8A2/event/5d0113bf1a5b3af0bc8e360b6c8ddcab1ecdf1647d68d6609bb77180d3c117c1
No wind, clean sensor, latest firmware.
-
@Efejota I looked at this but there is nothing to compare to, what is the problem?
-
@Brad_Olwin different altitude start / end by same place 100m.
-
@Dimitrios-Kanellopoulos Yes, but not only that. You can see that there were several loops and a progressive descent on the lowest point before the small ascent.
-
@Efejota yes yes. That to me looks quite bad. Is it like this all the time ?
-
@Dimitrios-Kanellopoulos To be honest, sometimes I noticed differences, but never paid much attention. The other day it was quite evident and remembered it when I read the post. I can check other activities to see when happened.
-
@Efejota keep a decent look for future ones.
-
@Dimitrios-Kanellopoulos said in S9 barometer problems:
@Efejota keep a decent look for future ones.
Maybe FusedAlti did not activate for this. I do not see a calibration change when FusedAlti typically activates.
-
@Brad_Olwin it can well be.
-
@Brad_Olwin When should it happen? I mean, I assumed that it worked automatically, but, if it were the case, when does it kick in? It might be possible that the activity that I shared was started without my usual warm up.
-
Dimitrios Kanellopoulos Community Managerlast edited by Dimitrios Kanellopoulos 25 Sept 2020, 18:58
@Efejota it happens like this:
if the average vertical error for the GPS altitude is low for x amount of time and the current altitude difference is less than the error, it triggers.
-
@Efejota Here is an example, often the shift in altitude can be more abrupt than this one. Here the S7 did not need to enable FusedAlti but the S9 did. I circled where FusedAlti activated for the S9 and you can see the profiles then match each other.
-
Last saturdays ride 136 km’s bike race: S9B elevation 1060m+
https://quantified-self.io/user/0NQynLXMmLPswXyjLJcHqdLJvam2/event/VPak9mH6lqgyzX7qpLsOGarmin edge 530: 1607m+
Garmin edge 830: 1419m+
Garmin edge 830: 1380m+
Garmin Edge 530: 1401m+
Polar M460: 1575m+
Garmin edge 520+: 1,232m+
Garmin edge 520: 1279m+
Polar Grit X: 1,626m
Wahoo ELEMNT BOLT: 1474m+ -
Found also one Suunto Spartan ultra result with 1422m+.
-
@Anssi-Auvinen I think you should contact support, maybe you baro is defective, more comparing with the SSU. Or, checking your values, it is the algorithm itself. I mean, according to the values your lowest and highest altitude are relatively close, so to get these more than 1000 m of ascent is with relative small uphills, Suunto has certain thresholds to trigger the ascent counting, I do not know the values for biking but for running are 3 m for baro and 7 m for non baro in some minutes. Depending on these thresholds some brands can overcount or undercount (suunto tends to undercount).
What I would do is repeat the same route several times and see if the ascent is consistent among activities. If they are, i would tend to believe that the sensor is OK. Then I would do a soft reset, if nothing improves or you already have done it, I would reflash the firmware, maybe something is corrupt.
-
@cosmecosta Yes, I will contact support again. I don’t know have you read the whore thread, but seems that may barometer is not sensitive as it used to be. It used to give more meter but now it cannot react as fast as it used to do.
-
@Anssi-Auvinen said in S9 barometer problems:
@cosmecosta Yes, I will contact support again. I don’t know have you read the whore thread, but seems that may barometer is not sensitive as it used to be. It used to give more meter but now it cannot react as fast as it used to do.
Yes I read all the thread. But, did you try the hard reset, reflashing the firmware? Maybe you save some days without the watch.
-
@cosmecosta Yes, I have done the hard reset last week.
