Related
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

FR 745 + Running Dynamics Pod, error in metrics

emfeande
over 2 years ago

the same activity shows correct "Vertical ratio" data on runalyze and wrong data on garmin connect, it happens often, has anyone else noticed?

This is a bug?

Thanks to all

  • 0 over 2 years ago

    I've had the 745 since it was released and I noticed that sometime earlier this year with one of the 745 firmware updates, the running pod data got wonky.  For me it started with stride length where there was no data for maybe the first 5 minutes of the run.  But now randomly just about every metric has the potential for "weirdness" similar to what you observed; missing data from the early part of the run.  I think the only data I haven't seen corrupted is cadence.  And I have tried new batteries thinking it was low-battery related plus I ensure the pod is "awake" before I press start on the watch.

    I sort of just eyeball rolled since there was also the elevation bug (long thread on this forum) that was also introduced in a firmware update so I've just accepted the quirks of firmware updates.

    At this point I don't even bother running with the pod and am just "happy" that the critical metrics I really need (pace and heart rate strap readings) haven't been corrupted (yet).

  • 0 over 2 years ago in reply to gmoriguchi

    yes, mine is affected by the elevation bug too,
    the weird thing is that the pod data on runalyze is correct so I assume it's just a connect application software bug

  • 0 over 2 years ago in reply to emfeande

    No, the elevation drops are also visible on the watch itself, before any sync with Connect has taken place.

  • 0 over 1 year ago

    Same here, I've first experienced this in may. Sometimes it works correctly, sometimes it's missing data. See forums.garmin.com/.../bugreport-incomplete-or-missing-steplength-vertical-ratio-since-may-22

  • 0 over 1 year ago

    I've had this problem since March when the watch updated and was on version 7.00, ANT/BLE/BT 6.15 and Sensor Hub 14.05. I'm now on version11.60, ANT/BLE/BT 6.15 and Sensor Hun 20.06. It's still happening. I got in touch with Garmin support when it first happened. They sent out a new dynamics pod, but that made no differemce. After a few more emails back and forwards, a product suppose case was raised. I was asked to send a few files over, then got a reply saying 'we'll be in touch when we have an update'. Heard nothing since.

  • 0 over 1 year ago

    As mentioned in my previous posting, I've stopped using the running pod but I'm tempted to do an experiment.  It's clear the issue is firmware related but I do wonder if the firmware somehow messed up how the 745 receives data from two (or more) external sensors; perhaps when using a HR strap and the running pod, the 745 runs into issues processing data it's receiving from both?  I'm not thinking of interference but literally the watch having issues recording/receiving "too much data". It doesn't make sense but who knows? 

    Before I ditch my heart rate strap (and just use the watch HR sensor) to see if my hypothesis is correct, are any of you running with ONLY the running pod as an external sensor and yet still getting drop outs?

  • 0 over 1 year ago in reply to gmoriguchi

    Yes, only using the running pod (and a BT headphone). See the link in my previous post (three above this one).