Suunto 7 Altitude Issues
-
@aleksander-h
that is crazy! do you have a chance to test and compare with another S7 or any other baro watch? -
@aleksander-h Well the final 100m or so were pretty much on the money so, if you stick in a 2.1km walk before every activity, you should be calibrated. Or maybe that was fluke.
-
@aleksander-h let’s see if next week’s update helps.
-
@fenr1r said in Suunto 7 Altitude Issues:
@aleksander-h Well the final 100m or so were pretty much on the money so, if you stick in a 2.1km walk before every activity, you should be calibrated. Or maybe that was fluke.
That section actually surprised me. Made me wish I’d done an extra km to see if it had somehow stabilized.
-
@freeheeler said in Suunto 7 Altitude Issues:
@aleksander-h
that is crazy! do you have a chance to test and compare with another S7 or any other baro watch?Good idea. I have an SSU which has served me very well. I’ll do a comparison walk either today or tomorrow.
-
Strange. Synced an activity from my ssu, then switched to my s7 and synes (and IT Aldo Said syncing 1/1 activity), but the S7 activity never showed up in the app .
[Edit] I searched the files system on my phone. Can only find the zip for the SSU activity. Nothing for the S7. I guess the app decided not to sync what it probably considered to be a duplicate. Wish I’d known that ahead of time, as I would have synced the S7 first to see the altitude. The activity is in the diary on the S7, but I can’t find any data files on the watch which might contain the actual activity.
Anyway, I uploaded the json file from my android phone for the activity yesterday and uploaded it to qs. Not sure if it helps at all, but here is the barometer altitude compared to the gps altitude.
Also, here are the graphs for absolute and sea level pressure, which I have absolutely no idea how to inteprete.
As for todays activity, my SSU gave me 80m ascent and 71 m descent. The S7 gave me 198m ascent and 198m descent.
Started and stopped the activity at the same place.
-
@aleksander-h the app should not filter duplicates, as far as I know.
-
@isazi said in Suunto 7 Altitude Issues:
@aleksander-h the app should not filter duplicates, as far as I know.
Strange. I remember something similar happened when I was doing balcony tests. Only one of them actually made it over to the app.
-
@aleksander-h
I remember you need to forget the second watch before you can sync the other watch. But I assume you did that.
It would be interesting to know if Suunto Service would either consider your S7 or your SSU faulty… because obviously one must be wrong -
@freeheeler there is no way I did a 200 ascent during that walk today, and the graph from yesterday is mildly bonkers.
-
@freeheeler and yes, I went through the whole forget thing. I did a 10 second yoga activity on the S7 just now and that came over straight away. Walk never showed up though.
-
@aleksander-h
GPS altitude is darker green, right?
Looks like altitude (=baro altitude corrected by fusedalti) is way more than GPS altitude.
Have you tried a fridge test to avoid facing dirty or faulty sensor? -
@mff73 said in Suunto 7 Altitude Issues:
@aleksander-h
GPS altitude is darker green, right?
Looks like altitude (=baro altitude corrected by fusedalti) is way more than GPS altitude.
Have you tried a fridge test to avoid facing dirty or faulty sensor?Yes, dark green was GPS based.
What on earth is a fridge test ?
-
@aleksander-h
https://forum.suunto.com/post/35403
Test fridge = check if baro sensor is changing altitude with just temperature change. = if yes, either sensor is faulty or just dirty. -
@aleksander-h said in Suunto 7 Altitude Issues:
What on earth is a fridge test ?
It is… wait for it… legendary
But I once heard that some alti change causes by temperature change seems to be normal…?!
-
40 min fridge test result. No idea what it means
-
And a 40 min couch test.
-
@aleksander-h
Official fridge test is without recording acitivity. To avoid any fusedalti things . Just to let the sensor behave alone with temperature. -
@mff73 said in Suunto 7 Altitude Issues:
@aleksander-h
Official fridge test is without recording acitivity. To avoid any fusedalti things . Just to let the sensor behave alone with temperature.I knew I’d mess it up
-
Interesting observation. Most the graphs I’ve posted here show a sudden jump right at the start of the activity. Is there some calibration jumping in as the activity starts?