I have a forerunner 235 and the "Avg Stride Length" stat used to be presented under "Running Dynamics". This stat has disappeared in my latest run (run yesterday on 5/4). Is this a one-time blip or is this now a thing?
My Forerunner 235 firmware was updated to 7.30 this morning and I ran just after but I still don't see any stride length. The last time I had stride length recorded was May 2. On May 5 it had disappeared already.
I just find it really weird that Avg Stride Length is still there for those of us that use FR630 watches, even when not in conjunction with an external sensor but only relying on the internal accelerometer. After all, the FR630 essentially shares the same firmware with the FR230 and FR235, and quite a few FR235 users have reported no longer seeing Avg Stride Length.
If the issue is with the Garmin Connect back-end and not the wearable devices' firmware, it has to be a really oddball decision to selectively remove Avg Stride Length for activities recorded on the FR235, FR610 and FR620 but not FR630.
I haven't run on the treadmill for a couple months, but prior to that my FR 235 had gotten pretty close to the correct distance (without a foot pod) based upon my typical stride - typically .05-.10 miles per mile difference. Today the Garmin was almost .25 mile per mile ahead of the treadmill pace. So did my actual outside stride (on very hilly terrain) change dramatically and "teach" my FR 235 a different stride length, did it start using the manually entered stride length in my app (which I don't think was ever used before), or is this connected to the recent issues with no longer calculating stride length? Anyone else see this lately?
This has got to be a problem with Garmin Connect, but I'm not sure why it's taking them so long to fix it. As long as your device is recording time, distance, and average cadence, then Average Stride Length can be calculated using these other measure. I've created an Excel sheet that does the calculation, but I don't believe I'm allowed to upload an Excel file. Here's the formula, which assumes distance is in miles, and time is in hours:minutes: seconds:
This has got to be a problem with Garmin Connect, but I'm not sure why it's taking them so long to fix it. As long as your device is recording time, distance, and average cadence, then Average Stride Length can be calculated using these other measure. I've created an Excel sheet that does the calculation, but I don't believe I'm allowed to upload an Excel file. Here's the formula, which assumes distance is in miles, and time is in hours:minutes: seconds:
Thank you for the formula. My maths is not too good. What is the formula if I use km as unit? What will be the average stride if I run 400m in 1.40 and my ave cadence is 185? Thank you!
Thank you for the formula. My maths is not too good. What is the formula if I use km as unit? What will be the average stride if I run 400m in 1.40 and my ave cadence is 185? Thank you!
I hope Garmin can fix the stride issue ASAP.
Average Stride Length = Distance in Meters / (Average Cadence X Time in minutes)
Now if you have km to get meters from that you multiply your distance by 1000 ie 2.76km is 2760 m
If you have time in hours min and seconds you'll need to multiply the hours by 60, keep the minutes the same, and divide the seconds my 60, then add them all up.
example
2h 26min 13s would be (2x60)+(26)+(13/60)
=120 + 26 + (.216667) keep at least 3 decimal places
=146.216667
So all you'll need is your average cadence then you are all set
Huge race tomorrow, trained all winter and now my watch is messing up....
The largest 25K in the country is tomorrow, it's the 40th year for the Fifth Third Riverbank Run in Grand Rapids Michigan. Been training since January 7th (1st official group run) and every weekend since, including some 12 mile plus runs in single digit weather.
Average stride length was definitely a metric that I used, and tried to improve on. Now "nothing".
