How does TR handle the inclusion/exclusion of zeros in power for outside rides?

I’ll do a 1 minute test file later, drop it into fitfileviewer.com and let you know. Pretty certain that auto-pause is the only thing that impacts what is in fit file.

1 Like

Sweet! Thanks for the time and effort :smiley:

Yes, wahoo at least also uploads to strava with the 0s included. An easy way to check this is with the Sauce browser extension for strava

@WindWarrior
@redlude97

1 Like

Case 1: Auto-Pause “ON”

  • Elapsed 63 seconds (WKO)
  • Duration 38 seconds (WKO)
  • Moving 36 seconds (WKO)
  • with duration of 38 seconds I expect to find 38 records in FIT file

31 + 6 + 1 = 38 records

and you can see the 25 second gap (63-38) in WKO:

This doesn’t answer the question. Its just a simple test case. I can see at least one recorded data without cadence, which I believe is because my Garmin 530 is configured to exclude zero cadence from cadence averaging.

Case 2: Include Zero Power and Exclude Zero Cadence

61 seconds recorded
FitFileViewer shows

  • 38 seconds with full recording of timestamp, location, power, cadence, HR, temp, torque, pedal smoothness, etc.
  • 7 seconds with everything above except torque, smoothness, etc.
  • 16 seconds with everything above except cadence

Ok so setting data recording to exclude zero cadence from averaging results in cadence being omitted while I was stopped for about 16 seconds.

Case 3: Exclude Zero Power and Exclude Zero Cadence

63 seconds total, moving time of 35 seconds

  • 31 seconds with all data (timestamp, location, power, cadence, HR, temp, torque, pedal smoothness, etc.)
  • 1 second without cadence
  • 7 seconds without left/right power balance, torque, smoothness
  • 24 seconds without cadence, left/right power balance, torque, smoothness

You can see part of the 25 seconds without cadence in this WKO screenshot:

1 Like

Sorry I was “showing my work” above. Needed some way to make notes while looking…

The answer, assuming I’m not too tired at the end of a long day, is that on Garmin 530 (and likely all other Garmins):

  • power data, including 0, was present in all recorded timestamped data, regardless of “Include zeros in power averaging” status in Recording Options
  • during auto-pause no data is recorded
  • cadence data is not always included in timestamped data, I’m assuming this is a result of “Include 0 cadence from averaging” Recording Option being disabled

Also, its easier to inspect some things in WKO than it is in FitFileViewer.

3 Likes