problems with my S9B

[isazi]

@Luis-Duarte said in problems with my S9B:

@isazi but your s9 its Baro?

Yes it is.

[Luis Duarte]

@isazi ok

[Luis Duarte]

@André-Faria yes i have yestarday
I go to train today

[Brad_Olwin]

@Luis-Duarte I wear my watch over the jacket or shirt nearly all winter for most of my activities. I rarely if ever have issues with altitude readings. Occasionally yes, but as I stated before that can be due to ferocious winds we can have here in the mountains.

[Luis Duarte]

[Luis Duarte]

This was the problem today
Not lucky with my whatch

[sartoric]

@Luis-Duarte
Who are you? The Flash?

[Brad_Olwin]

@Luis-Duarte I have had this problem before, it is rare. One morning I ran from CO, USA to Spain…I too was very fast:)

[Efejota]

I had a huge difference in altitude yesterday having a short ski walk with my S9B. Any explanation? GPS signal was clearly bad in the beginning, but I cannot understand that it took so long to get the correct altitude. How could I share the file for you experts to check (the activity is already in QS)?

[cosme.costa]

@efejota said in problems with my S9B:

I had a huge difference in altitude yesterday having a short ski walk with my S9B. Any explanation? GPS signal was clearly bad in the beginning, but I cannot understand that it took so long to get the correct altitude. How could I share the file for you experts to check (the activity is already in QS)?

Yesterday was some issues with GPS (mainly Sony chip), Garmin was affected too.

https://www.dcrainmaker.com/2021/02/tech-tidbits-garmin-gps-offsets-again-and-powertap-units-discontinued.html

[A Former User]

I don’t understand why just a sleeve can effect as bad the sensor. I’ve got in past many Casio Protrek and never had this kind of problem.
Maybe a firmware update will correct it

[freeheeler]

@g287-sf
I’ve had a protreck, too… many years back. this one had a twin sensor to assure no wrong measurements

[pilleus]

@g287-sf said in problems with my S9B:

Casio

I use two G-SHOCK watches too and the ascent and altitude are spot on. Even more exactly than my SSU.

[cosme.costa]

@g287-sf said in problems with my S9B:

I don’t understand why just a sleeve can effect as bad the sensor. I’ve got in past many Casio Protrek and never had this kind of problem.
Maybe a firmware update will correct it

Yesterdays issues were due issues with Sony chips. I have an S9B and I have had a SSU with the same placement and holes of the baro and I haven’t had issues with altitude that I can recall. I always wear the watch over the sleeve but I also pay attention that the fabric is not covering the holes (before running while running I do not pay attention to it). My running partner has an S9B too, he wears it in the left arm and I in the right and we have always very consistent results, as an example today we did intervals, in total 16 km up an down, and my ascent was 73 m and his was 71 m…

I also have discovered that is better that you let de watch some minutes before start running in the sport screen so Fusialti can do its magic.

[freeheeler]

@g287-sf
here’s what the sleeve can do. It’s not basically the case that the sleeve below the watch is bad, it depends on the type of garment and how wet it is.
The dark green is with the watch over the sleeve as I usually wear it for any activity. The graph is pretty accurate.
The light green is with the sleeve fully pulled over the watch together with a glove causing pressure from the other side… hence, watch tight to the skin. I assume the holes were blocked and towards the end I finally started sweating a tiny bit and that’s why the graph went nuts.

[Fenr1r]

@freeheeler Was that earlier research and analysis or off the cuff?

[A Former User]

@freeheeler

whaouu ! maybe Suunto can do something to “detect” false info and correct it “making a dual analyze” with topo map and Gps data to synchronise them

[freeheeler]

@fenr1r
second

[freeheeler]

@g287-sf
like strava does? …corrected in 2 seconds…

[A Former User]

@freeheeler yes as you say buddy, like an other third party does in 2 seconds.