S9 barometer problems

Anssi Auvinen

Quite far from identical.

But i have been thinking also the placement. In ride one the watch was in right hand and in ride two was attached to bike handlebar with suunto accessory.

Tested this also on tuesday ride, where I made 2 uphills with handlebar attachment and 2 uphills on a left hand. qs link

halajos

@Anssi-Auvinen if you wear the watch on your write wrist, the baro sensor is facing toward the headwind. I can imagine this is causing such issue.

Anssi Auvinen

@halajos There was no error when watch was in the wrist, it’s now when it is in the handlebar. And I write with my left hand, so I do not wear it in the write wrist

Dimitrios Kanellopoulos

@Anssi-Auvinen said in S9 barometer problems:

Quite far from identical.

But i have been thinking also the placement. In ride one the watch was in right hand and in ride two was attached to bike handlebar with suunto accessory.

Tested this also on tuesday ride, where I made 2 uphills with handlebar attachment and 2 uphills on a left hand. qs link

For sure this is a difference no doubt. I meant thought that the high is ok. (and the low).

In regards to wind / hand placement

2 potential probs.

As noted headwind (even if it doesnt exist)
Left hand can block the sensor if you push / lean on the bike.

To wipe out completely outside / wind factors imo the best apporach is either the bar or just in a pocket (if you want to be really picky) .

In regards to this:

https://www.youtube.com/watch?v=bPyEtZH3QaU

Anssi Auvinen

@Dimitrios-Kanellopoulos The “old” data with riding in the right hand just seems more accurate so I don’t think the placement is the problem.

Barometer just is just not sensetive enough anymore and is not reacting quick changes of altitude. And theres lots of those when gravel riding here in countryside.

But is the cause that watch is broken or still barometer is too dirty even after cleaning? Or is the problem in the updated software?

Dimitrios Kanellopoulos

@Anssi-Auvinen said in S9 barometer problems:

Or is the problem in the updated software?

The only thing I know is that in the last update we literaly din’t change anything for Alti or GPS

Anssi Auvinen

@Dimitrios-Kanellopoulos And if I remember the earlier update was in earlier in the spring.

Dimitrios Kanellopoulos

@Anssi-Auvinen correct.

Efejota

@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.

Brad_Olwin

@Efejota I looked at this but there is nothing to compare to, what is the problem?

Dimitrios Kanellopoulos

@Brad_Olwin different altitude start / end by same place 100m.

Efejota

@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.

Dimitrios Kanellopoulos

@Efejota yes yes. That to me looks quite bad. Is it like this all the time ?

Efejota

@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.

Dimitrios Kanellopoulos

@Efejota keep a decent look for future ones.

Brad_Olwin

@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.

Dimitrios Kanellopoulos

@Brad_Olwin it can well be.

Efejota

@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

@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.

Brad_Olwin

@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.