Please add cadence targets (COMPLETED)

Feature Requests Completed
#32

Yeah, this works. For the target RPM range shown, it could be based on the +/- 5% or some configurable percentage from the target RPM.

For the target Power, I noticed today that if I tap on it, it tells me a percentage.
If that is the percentage from target, maybe tapping on RPM toggles between RPM and target values or percentages?
But I admit that this latter thing is a nice to have, with the widget as described so far, it would be great already.

TD is minimalistic on details for a completed workout, but I have been looking for a platform that can show the following for workout once completed (graph and text summary), for the total workout and per distinct interval.
I think that with TD knowing what the workout intervals and targets where, it’s in a position to come up with this data in a text summary or with some visual aid.

avg cadence for entire workout: nnn RPM
avg power for entire workout: nnn W
avg Heart Rate for entire workout: nnn RPM

interval 1:
avg Heart Rate for interval: nnn BPM
avg Power for interval: nnn W
target Power for interval: nnn W
avg Cadence for interval: nnn RPM
target Cadence for interval: nnn RPM

interval 2:
avg Heart Rate for interval: nnn BPM
avg Power for interval: nnn W
target Power for interval: nnn W
avg Cadence for interval: nnn RPM
target Cadence for interval: nnn RPM

interval n:
avg Heart Rate for interval: nnn BPM
avg Power for interval: nnn W
target Power for interval: nnn W
avg Cadence for interval: nnn RPM
target Cadence for interval: nnn RPM

What do you think?

#33

RPM Range is something the user specifies in our editor here
image

You should remove this second part from this and create a seperate feature request. I will respond to that there :slight_smile:

#34

Showing target this way is great, showing average watt of the interval next to watt target would be very useful also.

#36

The problem is next watt interval is a permanent number and I don’t really want to add a permanent number to the screen although I am aware from many people seeing next target would be very nice. This one above would only show up in rare cases (actually has a target cadence and you are not on target is when it would show). I am open to ideas.

#37

I think he wants Avg watt for the current interval next to target watt, not for next interval.

2 Likes
#38

A post was split to a new topic: Please create the ability to see my average power for the current interval

#39

Apologies for the cross-posting on my part:

Some workouts specify 2 target RPMs for a single interval, so that together with target Power, it makes a “working” and a “rest” or “recovery interval.”

Example: 40/20’s (numbers totally made up)

Warm Up
10 mins @ ramp up power starting at 25% of FTP and gradually increasing to 50%, free (no) RPM target.

Work/Rest repeat intervals.
5 reps of:
40 secs at 150% FTP @ 85 RPM target
20 secs at 50% FTP @ 100 RPM target.

Cool down
10 mins of ramp down power starting at 50% FTP and down to 35% FTP @ 85 RPM

Might be for another Feature Request, but are Ramp Ups and Ramp Downs of power supported over a single interval?

Likewise for the work/rest intervals, what I’ve seen seems to build them as standalone intervals, for both ramp ups/downs and work/rest intervals. Might help keep things simple?

#40

This is exactly how our editor works now (with zwo files), and this is exactly how the app will work.

Meaning the editor supports

  1. Ramps up and down with or without rpm targets
  2. RPM targets for each interval (or in your terms 1/2 interval) in this case maybe the term segment is better, so 2 segments make up an interval and each segment can have a seperate RPM target.

And the app will support this too.

1 Like
#41

when will an update for the cadence target appear?

#42

It’s done and ready to go but had a lot of other changes that caused other bugs. Hopefully beta version tomorrow and production version early next week. Going much slower than we expected.

#43

Sorry these bugs in our DEVELOPMENT VERSION are killing us. We are getting closer but looks like it’s more likely to be in beta early next week.

#44

Ok, finally we are hopefully down to the last 2 small bugs and we will release beta tomorrow. I feel like a broken record.

1 Like
#45

I finally used the app for a serious workout ride last Sunday after a multimonth hiatus and got to see the fix for the timeline issue, and that for some work intervals the app now nudges me to stay within the intended cadence as described in this thread.
Bravo.

1 Like
#46

I know I’m late to the cadence target party but today was the first time I’ve tried them and I have some comments regarding these targets:

  1. When I set the target to a fixed value, the app creates a range. That’s fine for me.
  2. When I set a range (e.g. 100 - 120), the app creates an additional range (eg. 98 - 122). I think this additional range is not necessary, when I’ve already set a range.
  3. When the last interval of the workout has a cadence target and the app goes into auto extension, the extension keeps the cadence target of the last interval. I think, that auto extension should never have any cadence targets.
#47

Oh interesting on #2 yes that is a design bug. #3 makes sense to me. I guess that is personal option but I consider you the auto extend expert :slight_smile: we will do this.

1 Like
#48

Thanks for fixing #2 and #3 with version 2.4.7. Now it’s working as expected. Or at least as I expect it :smiley:

#49

Interesting #2 does not say it is done in our tracking tool :slight_smile: You are welcome assuming it is actually done :slight_smile:

#50

Salut Alex
Je ne vois pas la cible de cadence dans l’application.
C’est pourtant important dans les entraînements alliant force et vélocité.
Merci
Yvon

#51

Si il y a une cible spécifié, elle s’indique en-dessous de la cadence et la cadence même change de couleur quand tu est en dehors de la cible.
As-tu la dernière version de l’app?

1 Like
#52

J’ai la version 2.5.7 . J’ai spécifié une cible de cadence pour chaque intervalle. mais je n’ai aucune indication de cible RPM à l’écran. Yvon