Ambit3 Peak elevation gain
-
@freeheeler yes it is still possible to change the values in movescount
-
so today I went skitouring, I set both profiles (watch and skitouring activity) to altitude, I went to the place (I started from Realp -1538 meters).and then i manually set the reference altitude .Still I see start and end altitude completely wrong. ,respectively 1474 and 1388 ! I suspect I am doing something wrong?
-
@zzmike76
nice, what was your summit?
maybe, what you could have done wrong: setting the altitude manually. It switches off FusedAlti and if there is weather change, hence different pressures, then FusedAlti can’t do its magic.
But the weather is pretty stable between the north and Tessin at the moment afaik… can you share the alti graph? -
@freeheeler easy going, went to Tälligrat
Weather was super stable, my understanding of setting manually the altitude is that it should avoid the FusedAlti discrepancies?
-
@zzmike76
nice summit! I recall it was a lot of “cross country ski style” to get into the valley and to the actual ascent, but very nice slopes
the graph looks alright. The point is with the FusedAlti, and I did not believe this until around 2 years ago, you want this to work. Because it is much more precise than setting a manual altitude and the watch just calculates the difference.
Next time, leave your watch in alti mode (I never used anything else), when you start the activity do it without manually adjustment of alti and just wait for the satellites to lock, then start. Even if the watch shows in Realp 2’000m, it will be corrected throughout the activity. Normally within 15 minutes, and of course on the fly if the weather is shifting -
@freeheeler thanks for the hint, will try in the weekend (next skitour is planned :)) !
-
@zzmike76 i went skitouring today, and noticed the following: while driving the altitude was correct (again in Realp!) at 1530, as soon as I exited the car it started going down…after 30 minutes I started the activity, but noticed that it was mentioning 1340. Once reaching the peak, it was showing the right altitude. As in the other recording, this would mean 200 meters more in ascent. Unfortunately I cannot share the graph as the watch went in pause for a while, but next weekend will try again
-
@zzmike76
why did the watch pause itself?
Do you have any graph or no graph at all? it would be good to see the graph and route you made today.
alti drop could also be related to temperature drop but should be backward corrected with fused alti.
my friend has my “old” A3PS and he had no issues this weekend whatsoever (Obergoms). -
@freeheeler i simply forgot to lock the watch (doh!) and probably pressed inadvertently the pause , am attaching anyway the graph
PS : I suspect the temperature at this point
-
@zzmike76
hmm, ok… this doesn’t look like fused alti was able to do its job
do you have a time and distance scale for this altigraph? I assume the descent was recorded properly, but during the long horizontal the watch was paused. I’m not sure if pausing does affect fused alti.
What if you do a simple and short (20min) activity around your house even with minor ascents. It would be helpful to see how the watch reacts on the alti change etc -
Hi Guys, unfortunately I joined the club as well. The watch worked well until the weekend kicked in, where I noticed several weird stuff.
I have been cycling in the city, and the altitude profile went totally out of the box, and calculated 2939m ascent in 10km, where the altitude profile was from 0 to 3009.
, 
.I thought the the barometer holes were clogged, it happend to me before. I cleared it. Checked the settings, it was on barometric altitude only. After that I turned on fused alti and went for a run and did some hill repetitions to test the altitude measuring. The results: totally flat altitude with -43C celsius
Went home. Restarted the watch, cleaned the holes more. Synchronized the GPS settings, activated the Fused Alti. The next day I went for a run to a well known track (altitude +423m/-423m, with the highest point around 350m ), with the following results:
At the first activity I thought the suunto guys want to boost up a little bit my not so famous stats for the vertical week, but it seems like it not the case. Do You have any other tips/ tricks how should i proceed? Thanks in advance.
-
-
@gábor-tóth
Temperature = -49°C ?
Looks like your baro sensor is faulty.
Eventually soft reset, check the same information directly on the watch to confirm, but … -
@freeheeler that applies for other tours as well, I constantly get +200 meters, which are always added at the beginning when moving to cozy warm car environment to the ugly cold winter time outside
when in the car the altitude is fine, it drops very quickly when going outside. I would expect it to get fixed in 30 minutes, but that does not work -
@zzmike76
maybe you can try to wait before you start the activity and let the watch get settled with the temperature while you put on shoes and the skins on the skis?
but I am close to repeat what @Mff73 mentioned to @gábor-tóth just before
-
@zzmike76 said in Ambit3 Peak elevation gain:
@freeheeler that applies for other tours as well, I constantly get +200 meters, which are always added at the beginning when moving to cozy warm car environment to the ugly cold winter time outside
when in the car the altitude is fine, it drops very quickly when going outside. I would expect it to get fixed in 30 minutes, but that does not workit looks REALLY like a baro sensor HS
Search for “fridge” test , and try it, if altitude change from inside to outside … -
@mff73 said in Ambit3 Peak elevation gain:
ALLY like a baro sensor HS Search for “fridge” test , and try it, if altitude change from inside to outside …
Hi! thanks for the responses. I will give it a try, to use the automatic or the altimeter way of altitude measurement not just the barometric. if it continue to fail, i will search for an authorized service… : /
-
me again…did a 3 days skitour, and this time the elevation difference was huge, something like additional 600 meters per day. The peaks altitude was recorded properly, but the starting point never got fixed by fused. Also this time I was starting from a hut, so there should have been no variance (only inside/outside temperature was different). I think I will switch back to my ssswhr, cannot get such big discrepancies
PS: I did the fridge test and the variance was ok
-
@zzmike76
the total of 3 days is 600m off? 200m per day? Or was it 600m each day of the total ascent that was wrong? And by how much is the start altitude wrong?
Because I can see on my S9B frequently that the start alti is about 10m too low… it looks weird on the graph for roundtrips but is well within tolerance for me -
@freeheeler second day : 600 meters more, third day : 500 more. Starting altitude was always 150-200 meters less
