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

Forerunner 245: Wrong stride length for outdoor run when paired with RD Pod

Bob
over 2 years ago

Hi all.  Lurker looking for some possible answers or fixes to why my RD Pod metrics, mainly the stride length and avg vert osc, is totally bonkers with the 9.00 and 9.56beta software.  I've had absolutely no issues with any metrics from the Pod until those updates.  My stride length is completely wrong.  Which then affects the avg vert oscillation, showing me in the high 30s+.  Um, no. 

I've changed the Pod battery, deleted it from watch, resync'd it, etc.  Reset watch...nothing worked.  Rolling back to 8.60 ver software totally fixes the issues.  I've submitted .fit files to the Garmin beta crew (both 9.00 and 9.56 files) hoping they can find something in the data. 

Anyone else seeing any weird Pod #s with the latest software?

Cheers. 

  • 0 over 2 years ago in reply to thin

    I do not see a Forerunner 245 series watch on the account associated with the Garmin Connect account which shares an email with your forums username.  Please post from the account to where you have the Forerunner 245 series watch.

  • 0 over 2 years ago

    with the latest beta update, it is working

  • 0 over 2 years ago in reply to 1035215092

    It has been better, but I still see issues.  If you walk or pause/resume, during the run, the stride length is horrible for sometime after you begin running again, same goes for Vert Osc.  This is with the current 11.60 update as well.  All previous Betas have also shown the same.

    Each one of the stride drops (blue) below is me testing this.  First large drop is after a walk and second is me trying to see if a quick pause/resume brings things back into normal range.  The red is the Vert Osc Ratio.

    I have a few fellow club runners who get totally diff metrics from the Pod vs the HR version.  Way off.  Not even close.  So which is correct in that scenario? 

  • 0 over 2 years ago in reply to Bob

    Now at s/w version 11.60.  Usual unpair, reboot watch, re-pair RD Pod and same erratic results as before e.g. abnormally low reading for several minutes, then maybe rights itself for a while. On another run it had one reading at the start, then no data at all until 58 minutes. And another, running intervals, wildly incorrect and inverse trending i.e. longer stride reported at slower speeds and in the recovery section between the intervals, then suddenly seemed to report the correct data from around 40 minutes onwards.

    Actually, it is worse as now in the "Laps" section in Connect, the "Stride Length" contains the rubbish figures from the RD Pod, whereas in the past it reported the correct figures based on the cadence/pace for each kilometer.

  • 0 over 2 years ago

    Is Garmin working on this problem? There is really a lack of communication... When will this issue be fixed?

  • 0 over 2 years ago in reply to 1035215092

    We do not currently have any new information on this report just yet but hope to have something to address this in a future software update.  At this time, we do not have a timeline for the release of this future software update. Thank you for your patience with us while we work to investigate this issue.

  • 0 over 2 years ago in reply to SteveCudd

    As an interim fix, have the software compute distance/cadence (which seems to still work); if that differs by a large margin from the stride length reported by RD, then substitute distance/cadence in place of RD stride length.

  • 0 over 1 year ago in reply to Bob

    Cześć, masz może jeszcze tą wersję 8.60 do FR 245, mam ten sam problem, da się ją wgrać ręcznie, mam obecnie wersję 11.60

  • 0 over 1 year ago

    So I've noticed something interesting when looking at run data in Connect vs a website called, Runalyze. 

    Here's this past Sat's easy run:

    Connect: