This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Measuring too many swimming lengths

hi,

i have my 735xt set to 25 metres, as i swim in a 25 metre pool, and today the watch measured at least 12 extra lengths. i swam approximately 60 lengths and the watch measured 72. i did not have this problem 4 days back, so it could be a bug introduced due to some recent update

here's my swim, where it can be clearly seen how erratically the lengths were measured: https://connect.garmin.com/modern/activity/1512364406
sofware version being 7.10

anybody else encountering this? any explanations?

demonstrating the problem in attached screenshot:
  • I was swimming yesterday and it seems to be ok. I did not count pools after i started using Garmin. According to the time and length it is pretty standard as always. But there where strangely a lot of achievements in the end. Maybe i just swam so good :)
  • Former Member
    0 Former Member over 8 years ago
    I have a similar problem with my 910 Forerunner

    it always add one or two 25 m length when I swim 1 km in a 25 m swimming pool and I have still not found out why
  • I have a similar problem with my 910 Forerunner

    it always add one or two 25 m length when I swim 1 km in a 25 m swimming pool and I have still not found out why


    One or two is ok. it is not measuring real length in meters but only with your strokes and stroke style. So if you made some unnatural move, device can think that you did turn and count extra pool.
    The problem of this thread is huge amount of such extra lengths, not several.
  • this tool can help correct any errors after the swim. To get better length analysis you need a definite turn and push off with glide in my experience.

    http://swimmingwatchtools.com/
  • this tool can help correct any errors after the swim. To get better length analysis you need a definite turn and push off with glide in my experience.

    http://swimmingwatchtools.com/



    thanks, i know it, and i sometimes use it, but it does get tedious having to use it every time, therefore i ignore small problems.

    the problem with this swim is bigger, not even the tool can be used. here it is, in case anybody wants to try: http://bit.ly/2hYObad
  • Former Member
    0 Former Member over 8 years ago
    Do you have a long glide at each stroke? I had (and wasn't really aware of it), which resulted in lots of extra laps when I started using the watch.
    Apparently it often "recognized" a glide phase as the start of a new length. You might increase your strokerate a bit, it made me a better swimmer as well.
    Now my Garmin only miscounts if I bump into someone, besides that it's inch-perfect.

    Kind regards,

    Nigel
  • Do you have a long glide at each stroke? I had (and wasn't really aware of it), which resulted in lots of extra laps when I started using the watch.
    Apparently it often "recognized" a glide phase as the start of a new length. You might increase your strokerate a bit, it made me a better swimmer as well.
    Now my Garmin only miscounts if I bump into someone, besides that it's inch-perfect.

    Kind regards,

    Nigel


    @Nigel, actually not, and in fact until this swim my lengths were counted more or less fine, I sort of figured out how to cope with the minor problems that already exist. i am presuming that some recent update messed something up
  • My limited experience with 735 is good but I always remember 3 thigs

    1. strong push off at each return
    2. clear glide phase
    3. first stroke with the hand that has the watch on

    This was recommended to me by a friend who tested this extensively with Fenix 3 and is seems to work for me.

    I also avoid using start/stop button, only lap, as in my case this missed one lap and return until the next rest/lap press.
  • freak issue

    thanks all of you for your suggestions and theories, all very helpful

    having swum the same distance in the same manner again today, the watch measured everything perfectly, and there wasn't any software update since last week, as far as i know, so whatever problem i faced last week was some sort of a freak problem