Thanks in Advance.
I am testing a new Suunto Run 3. I wore my HR monitor and targeted 125 HR bouncing between 115 - 135 HR. I went on a mid-distance run and stopped at 1,000 kcal according to my watch. My export for a tcx file format, when re-imported into TrainingPeaks showed 1,440 kcal, while the fit file format export showed 1,000 kcal when re-imported into Training Peaks. The two files appeared to agree with each other on distance, time elapsed, and heart rate. When I used several online calculators, they average around 1,380 kcal.
I checked the settings in MovesCount, and everything seems accurate. Does anyone know what would cause the watch metric during the run and the fit file format to be 44% different from the tcx format?
By the way, I will change the auto-lap from .5 miles to .1 miles in case large sampling rates are aggravating an underlying calculation problem.
Kind Regards,
Mark
I am testing a new Suunto Run 3. I wore my HR monitor and targeted 125 HR bouncing between 115 - 135 HR. I went on a mid-distance run and stopped at 1,000 kcal according to my watch. My export for a tcx file format, when re-imported into TrainingPeaks showed 1,440 kcal, while the fit file format export showed 1,000 kcal when re-imported into Training Peaks. The two files appeared to agree with each other on distance, time elapsed, and heart rate. When I used several online calculators, they average around 1,380 kcal.
I checked the settings in MovesCount, and everything seems accurate. Does anyone know what would cause the watch metric during the run and the fit file format to be 44% different from the tcx format?
By the way, I will change the auto-lap from .5 miles to .1 miles in case large sampling rates are aggravating an underlying calculation problem.
Kind Regards,
Mark