Open Water Swim accuracy can be a frequent topic for discussion in the forum community and for investigation at Garmin. We are always working to provide improvements to device features. Previous investigations…
The most annoying part is that they fix stupid thing like emoticons, bring a bunch of useless upgrades (broken too LOL), and yet, a core activity like swimming receive little attention...
After all those…
I'm sorry to hear that. It sounds like this expensive triathlon watch is not suitable for open water swims. The frustration is increasing!
This watch (and its little brother the 255) is a trainwreck. They will never fix all of the major issue before the end of the lifecycle for this product.
The most annoying part is that they fix stupid thing like emoticons, bring a bunch of useless upgrades (broken too LOL), and yet, a core activity like swimming receive little attention...
After all those watches (swim, forerunners 35/45/55) they should have learned how to record swim metrics. And yet each time is like a new start from scratch.
This watch does not what the garmin advertises. We should all ask for a refund at the same time, that should get their attention!
Have you reviewed Tips to Improve Accuracy of Open Water Swim Activities?
If you've already tried out the tips, I'm happy to investigate. Please let me know if I have permission to reach out via email to gather examples.
The problem isn't the accuracy of GPS reception (which that page talks about): the track looks correct, and, if read out with external tools, has the correct length. But the watch recorded distance is incorrect and does not match.
There are many past threads about this exact problem, e.g. https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/298162/open-water-swim-distance-differs-from-the-track-recorded-todays-swimrun-352m-vs-approx-750m-unacceptable
One consequence of this is that pace for open water swimming is always completely off, in my case it's always 30s/100m slower than reality.
Notice that the above topic is almost 1 year old by now.
I agree, the GPS is very accurate.Our coastline is pretty rocky, I enjoy going around small islands, and I can clearly see the track matching my swim.
I do see small 40-50m segments where the watch doesn't record track points, but they are not likely to increase the distance.
As I said above the watch recorded 5.3km, the exported GPX is only 4.33km. The tracks look exactly the same.I'm probably not a bad swimmer, but 2.49m/stroke seems a bit like a stretch. A lot of the other dynamics dont look realistic either,
Be nice to have all this fixed (pool too, doesn't work either)
Exactly, it's a known algorithm problem that has been unresolved for a long time, although it really shouldn't be that hard to fix.
I am sorry, but I doubt any "investigation" will bring change for the better at this point. I also have a impression with these bug investigations that Garmin customer support is making us jump through the hoops and just going through the motions instead of actually trying to get the problem fixed.