Stryd calibration changed

Has anyone had issues with changes to the calibration factor without doing anything?

I started to use a Stryd in July and configured for speed and distance with auto calibration off, leaving it at 100.0. A couple of days later I noticed that auto calibration was enabled and the calibration factor changed to 100.9. I can't say it was me setting it to auto. I know I removed the FP once and added it again. Perhaps auto calibration is on by default? Anyway, I changed back to 100.0 and disabled auto calibration.

In end of August I decided to do a calibration run. Verified that it still was set to 100.0 and ran 4km (1 km in a straight line times 4). Measured 4036.61m and I changed the calibration to 99.10.

Yesterday I did a run following a course I do from time to time and noticed it measured longer that usual. Went into to settings and discovered that the calibration factor was 100.9 (auto calibration off)! I can't really say when this changed since I've been running a lot of new trails lately and I don't have a clue of their true distance. I know for sure that I didn't change the calibration factor and I know I never changed to auto calibration.

  • I just checked mine.  It has stayed at 100.0/Auto Calibration off.
    I use trail run mostly.  I'm not sure if I have checked after a "Run" activity.

  • I'm using the trail activity most of the time as well. Do you think that the type of activity may have an impact? The sensor setting seems to be generic for all activities? I'm suspecting that it was changed by some other reason. A sync, reset or beta version or something else I did (except changing the calibration factor).

  • There is an xml file in the Garmin directory called GarminDevice.xml.  I deleted it.  It rebuilds it right away and you don't lose anything.  But check around with that before you pull the trigger.  I had one time where I thought it switched it back to auto-calibrate but I can't remember the circumstances at all.  Never since.  Good Luck!

  • Former Member
    +1 Former Member over 4 years ago

     It is set to auto calibrate by default for a foot pod.  So if it was repaired for some reason it would come back in with the defaults.  I've never had it change on me with the 3/5/6 so far without doing a factory reset or deleting the pod off and adding it back.  That's not to say it can't glitch, just that I've never had it happen.   I have it set to off for calibration, always on for pace and distance for all activities. 

    Side note, not to derail but since it was a PITA to figure out: One thing I did run across is that if you do not have the Stryd datafield in an activity and do not have your particular stryd ID set in the datafield or typo the ID then if you walk for 5 minutes or more during an activity the stryd will shut down and then it'll take a little bit to wake back up.   This will cost you distance as the watch switches between GPS for distance and the stryd and it's very not obvious what happened. 

    That's one of the reasons I unpaired and repaired and then rolled my watch back and forward to reset it to defaults trying to figure out why my distance was off.   

    This is a feature, not a bug, technically.  The stryd doesn't need a watch to hold and store data and send it upstream so it needs some way to determine when you 'stopped running' and it does this by, if your pace slows below a certain pace for 5 minutes it assumes you're done. 

    With the datafield active and the stryd's ID programmed into it, it doesn't go to sleep while the activity is still running on the watch. 

  •  It is set to auto calibrate by default for a foot pod.  So if it was repaired for some reason it would come back in with the defaults.

    Thanks, that probably explains why it changed in the first place. I wonder if there is some other event that may change it back to on...

    Just checked the FIT files and the calibration factor is stored along with other info about the FP. I will try to find out when it changed from 99.10 to 100.9.

  • First of all a note to myself; Verify all facts and think out of the box and reflect at least twice before posting otherwise you will have to wear the hat of shame...

    I exported all fit-files to csv since the calibration and to my surprise it has always been 100.9, not 99.10 as I remembered was what I set it to. The only reasonable explanation I have is that I calculated using the formula "(measured distance / true distance) * 100" which is wrong instead of (true distance / measured distance) * 100. The fact that 100.9 was the same as the auto detection got is probably just a coincidence.

  • Hi. How do you know that it measured 4036.61m? I would only see in my Garmin 4.04 or 4.03k, or is there a way to see the distance to the centimeter? It would be really useful for me.

  • You can export the original FIT file to CSV using the FIT SDK: https://developer.garmin.com/fit/download/

    In the CSV you will see the total distance in meters.

    If you don't know how to use the tool I can give you step by step instructions when I'm at my computer tomorrow Smirk

  • Thank you. That helped me a lot. Did you solve your problem with Stryd autocalibrating itself?

  • Any idea where I can find the stryd calibration used in a Fit file? 

    I tried finding it with fit file viewer online but can't seem to find it.