Running in a tunnel caused issues in the total distance computation

[Dimitrios Kanellopoulos]

@tuxella I did open a bug report in any case… Something is wrong here.

Strangely while I tested this I didn’t get this issue. so lets let the watch guys figure this out.

[tuxella]

@dimitrios-kanellopoulos Thank you

[Likarnik]

@Dimitrios-Kanellopoulos I had same issue two days ago, but I think never before (I ran quite a lot under that tunnel). I thought it was just a glitch before I saw this topic Will it help with my link too?

[tuxella]

@dimitrios-kanellopoulos Did you have any news on this topic?

[Dimitrios Kanellopoulos]

@tuxella unfortunately no atm. Did it happen again to you ?

[tuxella]

@dimitrios-kanellopoulos I didn’t run in a tunnel since, so it didn’t happen to me

[ddausw]

@tuxella
It Happens all the time to me, when I am Running through a Tunnel.

[tuxella]

@dimitrios-kanellopoulos It happened again today: https://www.suunto.com/fr-fr/move/thomas430851/60e43ed24a1583244136b022

Firmware 2.16.26

[tuxella]

I realised this same tunnel is also on the Paris marathon path: https://storage-aso.lequipe.fr/ASO/egp/marathon-de-paris/mdp20-parcours-habille-200306-fr-bd.pdf (between km 26 and 27)

[tuxella]

I extracted the raw info from the app and uploaded to QS here: https://quantified-self.io/user/JbyRpWWlliUl8tBDkpWbbh73h5B2/event/ZGqqKZigZa7IEonK37xA

[tuxella]

Things got a little better today with a new S9 Peak, but still not good. I ran through the tunnel twice, and it was counted twice only on the way back.

Here is the Suunto move URL: https://www.suunto.com/en-us/move/thomas430851/612e18e6ab2d1145375165cb

[Likarnik]

Any news on this issue? I just ran through a tunnel first time since spring and got wrong distance/pace. Fw is latest.

[tuxella]

I just ran the same route in Paris with the latest firmware on the S9P (2.18.18) and everything looks fine: https://www.suunto.com/fr-fr/move/thomas430851/6153018b2e43996eb53f2b0b

@Dimitrios-Kanellopoulos Do you know if there was a fix recently or if this issue could appear again?

Regards

[Likarnik]

@tuxella nice, tnx for info, I’ll try it too!

[Likarnik]

@tuxella hm, not for me. Tried yesterday and distance is better, but I still got two spikes in pace when I was in tunnel (just after gps was back) and a new PR on 400m - not true. I have 60 runs on this exact route (and even more if I count other runs thru that tunnel) and only after March update this spike appears.

[Dimitrios Kanellopoulos]

@likarnik can you send logs via the suunto app the next time ? and then ping me with your SA account name

[Likarnik]

@dimitrios-kanellopoulos this option, right after syncing activity?

I’ll try to reproduce in the evening, thank you.

[tuxella]

It happened today again: the distance under the tunnel was counted twice: https://www.suunto.com/move/thomas430851/61812f0036da4049ddedc17f

(I sent logs to Suunto)

[tuxella]

Today was a bad day for my watch (S9P) : the tunnel was counted twice

https://www.suunto.com/move/thomas430851/619ce16e0400d73f7c48dc8c

[tuxella]

Another bad day (S9P): https://maps.suunto.com/move/thomas430851/61a61fcae8d0ae379d8af479

Kilometres pace shown in the Suunto App make it clearer:

I can’t run at 0’33/km or even 1’12/km

I’ll wait for the next firmware to post here again.