Running in a tunnel caused issues in the total distance computation

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

[halajos]

This bug is definitely there in FW 2.20.30, confirmed by my unusual ‘cave run’, as I described here: https://forum.suunto.com/post/107721
@Dimitrios-Kanellopoulos can my data help to fix it?

[tuxella]

I ran into the same issue today, in a shorter tunnel.

I was with a friend running with a suunto 9 peak as well, and she had the same issue.

Links to our activities:
https://maps.suunto.com/move/thomas430851/63302284911a6a6cd8036306
https://maps.suunto.com/move/oliviacolle/63302566d56fb73077f414e4

Let’s hope the next firmware fixes this.

[isazi]

@tuxella thanks I’ll report this today, hope that from your activities they can fix it.

[halajos]

@isazi I have an example with 2km in a cave counted twice, hopefully it can also help: https://maps.suunto.com/move/halajos/63132dce955dae0f3a247721

[isazi]

@halajos what I can share is that the developers at Suunto are looking into this and plan to fix the issue. Unfortunately the next firmware release is already closed (and it is very close), so this will have to wait until the one after. I will keep you posted with information, if I get updates.

[Jaka Vogrincic Bizjak]

Hello,
It is something new about tunnel issue. I have a short tunnel (280 m) but the same issue. In the tunnel my pace on S9 is like Kipchoge

When the new version it will be released.

Thanks, Jaka.

[grillaume]

Hello, any news about the distance counted twice ? I can report the same problem with my Suunto 9, v2.23.24… in the same tunnel as the previous messages in Paris

[isazi]

@grillaume it is fixed with next software update, available very soon if nothing happens.

[Jaka Vogrincic Bizjak]

@grillaume now with the last update the problem is solved. I tested it yesterday in a tunnel. All OK with distance and pace.