Altimeter

freeheeler

@blenedfly
I wouldn’t give up so soon if you like the watch in general.
the altitude is corrected by GPS frequently during an activity. if the last corrected altitude is going wrong again, because of covered holes and hence built artificial pressure (the alti goes doen then), it is likely that you check before it’s corrected again and it shows below sealevel.
It is also visible on the graph. I think no spot in your area is below -100m sealevel.

Try a d dummy activity on your balkony, put the watch somewhere for 30min, leave it alone and observe what it is doing.

blenedfly

@freeheeler I’ll try … because I like the watch

On this graphics I not see any strange, this is a speed graph, not altitude graph. This spikes on the speed in MTB sport mode for me are totally normal. At first time I believed that was created by crossing under bridges or tunnerls, but later I discovered that not. I have between 1 or 3 of this spikes on any activity of MTB of more than 1 hour of duration. It’s common come back from a MTB activity at flatlands with max speed between 80-120km/h…

The altimeter have their own topic, sometimes do have strange behaviors that I can’t explain the origin. Nothing of the logic reasons can be applied, but also not bigger differences like yours of 2000 vs 25.

I can’t explain why, but all the these kind of problems happen to me on MTB or Inline Skating. Running or Trail Running no. Also this happen only with the SWA, I tried to replicate in other apps without using SWA without success, that means that hardware it’s OK. The most strange it’s that I practice the sports in similar areas, that means that the enviroments are clear sky, without trees, without building close, etc, and on MTB with SWA I can repeat this spikes or erros, but on Running this did not happen. I expect more this kind of errors on Running, because the watch it’s not clearly exposed to the sky, on MTB yes, have a perfect exposition to the sky. About if something is blowing air into the sensors: I don’t know if it’s possible, but on MTB/Cycling the baro sensor could be directly exponsed into the wind, I don’t know if this can cause some problem or it’s directly related to something in this sport mode on the SWA.

Also in the past I had the problem of the bug that the S7 reebots or freeze in mid-activity. I don’t know if Suunto worked on this or push some kind of silient update to the S7 because in the last months did not happen again. Normally this happened each 2 months and now already they passed 4 months without problems

Start the activity before did not help, like wait until I have fixed GPS on SWA. Looking the activities this not happen on the start of the activity, that could sound logic, this spikes or strange shifting in the altitude happens after really long time that the activity is started (more than 30’).

@blenedfly said in Altimeter:
@freeheeler
image url)