Running in a tunnel caused issues in the total distance computation

[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.

[ddausw]

the same as before with my watch. the tunnel length is counted twice. in wuppertal there are many tunnels on my running routes. the evaluation is hardly useful.

that seems to be a software bug and could be eliminated well 🤨

[Dimitrios Kanellopoulos]

Hi all, we might have a fix for this on the next release. Hold on there.

[Likarnik]

@dimitrios-kanellopoulos Looks good after two tests with new firmware, thanks

[ddausw]

The update does not result in a major improvement. Some tunnel distances are calculated correctly. Other tunnel distances are not evaluated correctly. Does it depend on tunnel length and GPS accuracy? I will verify it.
Is it possible to downgrade to firmware 2.13.18? Everything worked fine there.

[Dimitrios Kanellopoulos]

@ddausw please dont confuse posts. This was a bug fix for double distance.

Distance in tunnels can vary due to calibration and other factors

[Likarnik]

Hm, looks like my tunnel is stubborn one Yesterday I ran my route again and bug has returned It was always 5,9km-6km, then bug arrived and route expanded to almost 6,5km, fix was at 6,2km (not perfect, but ok) and now again at 6,44km. Tunnel is around 230m in length, so running out and back 0,5km is added. I’ll test again and send logs…

[tuxella]

I did another test this morning (first time since a couple of months and firmware releases), and the tunnel was counted twice again

Firmware version: 2.20.30

You can find the track here: https://maps.suunto.com/move/thomas430851/6267d46cecb30d719c92f7d0

[Brad_Olwin]

@tuxella Not clear on the issue here, I looked at your track. You did an out and back and went through the tunnel 2 times. correct?

[tuxella]

@brad_olwin Yes, I went past the tunnel for ~250m before going back into the tunnel.

I did the same thing and illustrated it here: https://forum.suunto.com/post/80538

[ddausw]

After the firmware update to 2.20.30, the tunnel distances are calculated incorrectly. It looks like the old bug (double tunnel distance) has crept back in.
Surprisingly, the tunnel distances are calculated correctly with the Bike setting.

My suspicion is that the error is something related to FusedSpeed.