Data Field choices

[Barend de Arend]

• Current Power (with a little smoothing)
• Interval Power or Work Done or IF or TSS
• Interval Time

 

Things that Garmin can't do in a meaningful way, that I miss:

• Recording is busy
• Interval is busy
• Last Interval Power & Time

[Spinnekop]

I always thought TSS wasn't really needed during a ride but more for statistics and monitoring your Stress after rides?

Nifty data if and when you are aiming for a say 200 TSS ride.  Then you don't worry about time or distance or nothing.  Just get 200 in. 

Sometimes you need to do a 500 TSS weekend......

Or you want to see if you can do 100 TSS per hour's training. (Proper steady state interval ride)

 

Stuff like that.....

[Spinnekop]

I am a bit of a data junky.

 

Screen 1- Used on interval training 

3s power

Lap time

Lap power

Time of day

Lap count

HR

 

Screen 2 - General data

Temp

NP

Ave power

Total time

TSS

IF

Avg speed

Avg HR

 

Screen 3 - Race day

3s Power

Time

HR

Distance

 

Screen 4 - Altitude

Altitude graph

Meters ascent

Elevation

 

Screen 5 - Maps for riding courses and Strava sections

[Today's Plan]

 

It all come's down to personal preference and goals of that ride along if you using Power or just Heart Rate monitor. 

 

Screen 1: 3sec PWR (as but the time you glance down you will see you effort) ; current HR (to see how you reacting to the efffort) ; Riding time; TSS for Power users and AVG HR for non pwr; Cadence for the road bike / MTB not as NB ; NP and Zones (for pwr users);  Average speed only really for roadies unless it a MTB loop you do regularly and can compare. 

 

Screen 2: If you doing intervals and hit the lap button - go wild and insert lap times, pwr, HR, Current Pwr and HR Zones and 3sec Pwr at top etc

[HappyMartin]

HR

Distance

Elapsed time

 

I keep it simple. More fields than that and the risk I will ride off something, over something or into something go up exponentially.