Doubt about Suunto 9 Baro altimeter/barometer calibration
-
@TELE-HO AFAIK if you manually calibrate the altitude while recording an activity, fused-alti will be disabled. not if you calibrate it before an activity. would be nice to see this activity in MC
because allways when fused-alti calibrates the altitude for more then around 8 meters, you see the pressure change in the baro diagram. -
@TELE-HO Is it possible for you to merge this one and the recorded one in to one graph? Maybe quantified.io is helpful? I did nor use it yet, but have seen a lot of such stuff is done in there by others…
-
@johann-fuehrer Jup that is possible
-
@mario_b
yes I am aware that you switch off fused alti when manual calibrating during an activity recording.
Here’s the sea level pressure with the altitude profile.@Dimitrios-Kanellopoulos
I don’t know who to do an overlay… but if I do an overlay, it would be necessary to have it almost idential from the drawn to the recorded track to have the best comparison, right?
living sideways
-
@TELE-HO update 2 activiteis / routes to QS.
Select them on the table
Press merge
Use the distance axis when viewing -
@TELE-HO for a GPX track you can get “real” altitude information here i.e. https://www.gpsvisualizer.com/elevation but I do not know how exact that is…
-
@johann-fuehrer … it’s a 30m x 30m grid SRTM1
-
Runanalyze!
-
@TELE-HO perfect. i think you’ve being right, as you said, that i could be, because you calibrated it on the gondola.
as you can see, fused-alti is correcting the altitude all the time on the activity to a higher altitude. is the altitude value on the end of the activity nearly correct? -
@mario_b
yes, it is absolutely correct at the end.I just noticed that I’ve had a GPS precision issue for the first 35minutes of this activity anyway. I wanted to redraw the exact route but saw that the signal was off track at the beginning… it does not make sense to overlay my recorded move with a drawn route I think.
-
@TELE-HO so i would say, there is nothing wrong with your watch. looking at the ambient pressure at around 930 (which is not anough for the swiss the last weekend) i think it was only a faulty calibration at start. then fused alti kicked in, and corrected the altitude until it was nearly correct. (>1005 hpa at the end sound more possible too).
-
@mario_b same opinion. Somewhere at 1 h 15 mins after start it started to look ok.
-
@Dimitrios-Kanellopoulos Thanks
. Again, sounds logic.
After my test that I described below I have this doubt: you know with which frequency the S9B take samples of the barometer to calculate and show the altitude? or which is the frequency that update the altitude displayed?I made a simple test using the S9B, Mobile with barometer and Samsung Gear Frontier. I went downstairs one floor (~4m difference).
1st try: S9B not show differences even after ~20sec or a bit more. Mobile and Gear displays the -4m variation instantly, the altitude on these both devices is continuing updating almost on each step that I do down.
I went up. Mobile and Gear displays the variation of +4m. S9B again no differences. After around 5 minutes, I see that the S9B display me a -4m difference (wrong), looks like displays me the value from when I was down, but do not register that I went up again.2nd try: Mobile & Gear again displays correct results instantly and continuously. S9B: I decide give more time waiting on each floor. After few seconds or minute waiting on the lower floor, start to display me a variation of -3m, after few minutes I get the -4m. I went up again, +4m after few seconds or almost a minute.
Results: Mobile & Gear displayed correct value all the times and instantly. S9B worked tricky. One time showed me a correct result but maintained the difference error created on 1st try. 2nd try was perfect, but need sometime to show me the correct values.
-
@flypg I have read about some threshold value which must be reached until an altitude change is recognized by the watch, I think it was about 3m or somewhere in that range. Maybe this kicks in as well …
-
@johann-fuehrer Thanks, yes, this is why I would like know with precision to understand a bit more the watch. I think that also exist some timelapse to process this or display this and this results in the “delay” that I see to display the information.
-
@flypg if it’s the same algorythm that is used in the ambit3 peak for automatic mode then:
When in watch mode, it messures every 10 sec. if you move up/down more then 5 meters in elevation (around 0,6hpa) in 3 minutes, it switches to alti-mode. when your are moving less then 5 meters in 12 minutes the watch switches back to baro-mode -
Thanks @mario_b! Now I can understand for what on 1st try the reaction not was immediately and I got better results on 2nd try.
it messures every 10 sec
Wow, I imagined that should be a lower value, by this I expected a faster response in the update of the altitude readings. But really not need a faster update in watch mode, because for this I have the Sport Modes.
Thanks to everyone again! -
@flypg it counts higher than 3-5m variations in 12 minutes. If you would go a bit more low then both devices should react the same.
That is to wipe out pressure changes as we talked before
-
If you are at a constant altitude (less than 5 meters of vertical movement within 12 minutes), your watch interprets air pressure changes as weather changes and adjusts the barometer graph accordingly.
-
Thanks again to everyone!
Yes @Dimitrios-Kanellopoulos, this explains that on all my attempts I generated a altitude variation > 30m in less than 12 minutes (because I went up and down several times more than the 2 tests).
The only that is not totally clear is the variation of 1st try that the S9B not registered this +4 of when I went up.
