problems with my S9B
-
@isazi but your s9 its Baro?
-
@cosmecosta i have some friends with this whatch and they dont have any problems.
So I think the problem is with my baro.
but i will try again as you are saying
Thanks -
Just a simple advice: wear it on the right wrist if u use whr
-
@Saketo-Nemo next training I will do.
Thanks -
Hello Luis,
Just for the sake of it, have you tried re-installing firmware and reset after?
Also, after reset, sync with SA, wait about 30min for the agps settle down and before starting waiting for good fix. -
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi ok
-
@André-Faria yes i have yestarday
I go to train today -
@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.
-
-
This was the problem today
Not lucky with my whatch -
@Luis-Duarte
Who are you? The Flash?
-
@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:)
-
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)?
-
@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.
-
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 -
@g287-sf
I’ve had a protreck, too… many years back. this one had a twin sensor to assure no wrong measurements -
@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.
-
@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 itYesterdays 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.
-
@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.
living sideways
