ok issue is fixed. updating coming likely tuesday.
1 Like
Would I need to raise AND lower the HR+ target to cause the HR+ target to engage?
I ask because in the test workout I did this afternoon, I did raise the power with the up arrow (from 127 to 142) during the HR+ section, but nothing changed.
Fix coming Tuesday and fixed the password, sorry about your workout.
This is not fixed for me.
I upgraded to iOS version 8.3.8 of the app and started out on my usual custom workout. It has a 5 minute ERG warmup, then switches to HR+ with a target of 127
As you can see, immediately after the switch from ERG to HR+, the power just dropped and HR followed.
I pressed the down and up buttons a few times, but there was no change.
I quit the workout and went into a Quick Start workout with the same HR+ target, 127.
This reminded me why I thought it was important to have that ERG warmup before switching to HR+ mode: so that the increase in HR during the warmup does not interfere so much with the algorithm later on.
As you see from the quick start workout with the HR+ 127 target, the actual average was only 124bpm, despite me doing a fairly reasonable job of keeping the cadence steady.
Keep in mind that I was already a little warmed up from the original workout that I aborted. Without that, would the average have been even further away from the target?
Sorry about that, strange your bike should be FTMS and work the same as all our devices but I do see for FEC (used by Neo and a few others) a possible cause. If you wanted to do this ble testing BLE Device Testing Tool and email it to me then it would help confirm why this might happen to your trainer. You could also try click erg mode pressing up right after it switches to hr+ and then switch back.
Our previous hr+ had a second issue that it might have been targeting a bit higher than originally designed, in that 127 is what we try to keep as a maximum and we target -2% to 0%, so you might have to raise your target if you want to average 127. Maybe most people expect that to be an average so maybe I should raise it a bit.
Once you send me the test, I can confirm if the thing I just improved might fix it. If your bike is fully FTMS I am very confused at to how this could happen. Online says it is FTMS, but it could be FTMS+more…
I tried your workout with all our devices. Looks like below on emulators but I did do an improvement that is likely your issue.
I have no device to run the BLE device testing tool on, just an ipad.
I will try the erg button (and the slope one) and back to HR+ to see if that has any affect.
All I know is that it worked as recently as 31 Oct and now it doesn’t.
On the target being a maximum rather than an average, I can work with that by nudging my setting up a touch. Thanks for clarifying.
Could you also clarify how far back the algorithm looks when choosing what to do with power please. Does it, for instance, still include the first minute of a 60 minute workout in minute 59 of that workout?
Presuming the same HR target was set throughout, how, if at all, might the results vary between a workout that was 1x 60 minute interval, compared to a workout that was 3x 20 minute intervals, or 6x 10 minute intervals?
1 Like
It looks back the last 10 second average of power and last 10 seconds of hr to determine next target.
1 Like
I found it and fixed it next release in next 2 days
1 Like
Thanks, I will give it a whirl and report back
1 Like
Fixed now, I am 95% sure 
This is not fixed for me.
I upgraded to iOS version 8.3.9 of the app and started out on my usual custom workout. It has a 5 minute ERG warmup, then switches to HR+ with a target of 128
As you can see, immediately after the switch from ERG to HR+, the power just dropped and HR followed.
I pressed the down and up buttons a few times, but there was no change. Same with switching from HR+ to ERG and back.
But when I switched to slope, something did change: the target became 128% of something and then when I switched back over to HR+ the target was 128% of HR. I touched the HR tile and the target changed to 128 bpm, but the power did not reduce to bring HR down towards the target.
This is the workout Trainer Day
No need to have this take up a lot of your time on my behalf. I am happy with Quick Start workouts now I know that the algorithm looks at only 10 seconds history and I can auto-extend easily
I really love HR+ so I really want it to work right. This is so strange. I will keep looking.
2 Likes
Hi everyone,
I wanted to check if anyone has seen something similar with mixed ERG + HR mode intervals.
I created a 3x8 workout with 4 min rest between sets. Each 8-minute interval is structured like this:
- 1 min @ 80% FTP (ERG mode)
- 7 min @ 135 bpm (HR mode)
The idea is to “prime” the effort with a consistent power start, then let HR mode take over and stabilize at 135 bpm for the remaining 7 minutes.
I did this workout twice:
- Nov 2: Worked perfectly. The first minute held 80% FTP as expected, and when the 7 min HR section began, power settled smoothly at the level needed to maintain ~135 bpm.
- Nov 8: Same workout, same setup, same trainer, same HR strap… but the HR mode portion behaved differently. After the initial 1 min @ 80% FTP, when the 7-min HR interval started, the power started much lower than expected. It looked like the system was “basing” the starting power on the rest interval before, rather than the 1-min ERG section that immediately preceded it.
So instead of smoothly continuing from the 80% FTP power, it dropped power and took a long time to ramp back up to maintain 135 bpm. The feel of the interval was totally different.
Question:
Has anything changed recently in how TrainerDay determines the starting watt level for HR mode segments? Or is there a setting I might be missing? I expected HR mode to take the current watts into account, not the watts from the prior rest.
Any advice appreciated!
Thanks!
We can’t duplicate this but one other user reported this (above). Seems like a bug that affects some trainers. What trainer do you have?
I have a new idea how to fix this so it should be the same on all devices. It really should be anyway but hopefully this fixes it for once and all. Early next week.
2 Likes
I have a Tacx Neo. Just one change I can think of. I also connected my HRM to my fenix.
If it helps you pinpoint it, whatever the version was that was current on iOS on 31 Oct worked perfectly well for me.
In both 8.3.8 and 8.3.9, it has not worked.
1 Like
I will test neo with this thanks