What is the reason that when you upload 310xt data to Garmin it says one thing and when you then upload the file into TP it is very different? What is going on here? A bit confused and I am thinking this is the forum to ask. For example Garmin says 157 ave watts and about 1600ft of climbing and TP says 141 ave watts and 500ft of climbing. (watts are exact difference and elevation is approximate difference)
For the power difference, maybe your Garmin has non zero averaging switched on. i.e. times when you are not pedalling or not included in the calculation of the average.
I will look into the non-zeroing. I had read about that when I did a search on the subject.
I don’t understand how the elevation can be reading different.
Anyone else have an idea??
Can’t believe that everyone wouldn’t be experiencing this.
I don’t pay much attention ot elevation, but the power is b/c the 310xt only records averages with no zeros. TP automatically converts the NZAP(non-zero avg power) to AP. This is the one deal breaker for me using the 310 as a head unit with my SRM.
Elevation may be different if TP is applying elevation correction. Because the 310XT uses GPS-based altimeter (as opposed to barometric based), the elevations can occasionally be a bit suspect. As a result, many online (and even offline) applications now automatically correct elevation based on NASA data that has known elevation data points for just about everywhere. I don’t know offhand if TP is doing elevation correction though…but that would explain it.
Thanks for the input.
Applenut- Can you expand on why the non-zero ap makes the 310xt not useful as the head unit? I’m assuming that it is because it is in a way “cheating”?