That’s quite the difference between the apps, this is why I like testing, bit of a cliche, but ‘the best indicator of performance is performance itself’ , I suppose if you find one aligns more closely with how you feel and test where your FTP is, that would be the one to choose, but I think those values show that testing still has a place.
Just in case you weren’t aware, you can set the minimum interval length for eFTP detection in Intervals.icu. If I remember correctly, the default was short.
Yep cheers. I did change the minimum interval length to 480 seconds because I was getting ridiculously high eFTP estimates from shorter intervals.
You’re still going to be estimating from an effort that’s at best about ⅕ the duration of the thing you want to know. Treat with caution.
Yep agreed. Hence why I have shown all the various estimates.
I like the TP one as it also gives an associated TTE (which is 33 minutes in my case).
Hey there,
just done another 20 min field test indoor. The results:
-tested FTP: 247 W
-AI FTP detection today: 268 W
-WKO 5 MFTP from today test: 261 W, from last 90 days of training: 272 W
I perform the FTP test every time, with the same modality, trainer and after a recovery week. But, during the last 2 months i’ve trained and raced many times outside, with a different bike and power meter so the power output can’t be matched perfectly.
Anyway I’ve set my FTP at 247 both in TR and Trainingpeaks, because, from my experience, an inflated FTP is worse than a lower one for training, particularly for subthreshold and over unders.
Hope my reports can be useful to this thread
I suspect TP have integrated the mFTP from WKO5, which I’ve found to be the most accurate, although it does depend on maintaining the PD Curve, and in WKO5 it tells you the durations you need to test, not sure if TP is giving this information out yet, I haven’t spotted it but might not be looking in the right place.
Yes I agree. The mFTP and TTE model is in Analyse 360 > Power
Sorry for such a late reply on this one. It got a bit lost with all of the other AI FTP stuff I’ve been working on.
It sounds like this issue should be mostly resolved with the work the team is currently doing. 
For now, I’d recommend manually lowering your FTP. Hopefully, AI FTP Detection will be back up and running for you shortly.