Measured distance in swimming is wrong.
-
@Johnkokk can you send logs (it is done via the app, in the settings menu) after this happens? I am forwarding this thread to Suunto, but logs after the issue happens would help the developers more.
-
This could be a bug, or the freediving distance is different from the openwater swimming distance. Anyway, I reported it to Suunto.
-
@isazi
I don’t think that should matter. As you can see on the map, the route is marked correctly.This route corresponds to a certain distance, which the watch should report correctly.
I’ll send the log files whenever i can
-
@isazi said in Measured distance in swimming is wrong.:
@Johnkokk can you send logs (it is done via the app, in the settings menu) after this happens? I am forwarding this thread to Suunto, but logs after the issue happens would help the developers more.
I sent them right now, but i don’t know what log it really sent.Should i do that right after i get out of the water ?
-
@Johnkokk I am not saying that I am right, but the freediving mode is not made to track openwater swimming, so there is a chance that it measures something different, e.g. only the above/under water parts.
-
In freediving we don’t travel underwater
Even the marked route on the map, is the one that i swim on the surface.
I think this is what it SHOULD report back.There is also a field called DISTANCE in the report of the watch.
Thanks for your help by the way.
-
@isazi I encountered the same phenomenon in Vertical after a recent update
The owner of the watch sends a log after each workout.
When a link to the training was sent to me the distance shown works out Note that measuring distance by bike and running is normal only when swimming in open water this happens -
@Johnkokk I just heard it will be fixed with next firmware release, thanks for reporting it!
-
@isazi thank you
-
I have the same issue , with the free dividing mode.
For open water swimming and pool swimming the distances are correct. -
@isazi said in Measured distance in swimming is wrong.:
just heard it will be fixed with next firmware release, thanks for reporting it!
Can we have an approximate date on this fix ?