Cycling Power Estimator
-
Thank you so much for this wonderful S-plus app. I tried it today on my weekly riding. Everything was excellent except for the cadence indicator; it didn’t show the RPM on my Suunto Race watch (latest update). It just showed a (–) symbol, but it was functioning perfectly.
-
Hi. I tried your app today and the same thing happened to me twice (in two sessions) with the cadence. I even re-entered the circumference in mm of my MTB wheel, which is what I used for the rides. It’s a good app for estimating power without a power meter installed, and good for measuring load.
Thank you for your work
-
Yep - the cadence display issue is a recent regression, I had it working for months until recently.
This morning’s update should have fixed it but I have not tested it on-device yet. -
@mickywickyftw Thank you for your time, I will give it a try when I get home and keep you informed.
-
@mickywickyftw Excellent, it’s working perfectly now, and the cadence RPM is showing correctly as it should. Great job!
-
I’ve introduced a new setting for user weight. While reading from the watch user weight value appeared to work, it was causing issues when starting the SuuntoPlus app with any non-default rider position.
-
@mickywickyftw thank for the app! I’m kinda new to cycling, I’ll test next ride
I have a question: the FTP value requested as input in the Suunto App is used for the power calculation or it necessary for other scopes?
Haven’t dove any FTP test yet, so if needed for the power calculation I would set a guessed (aka random) FTP
Suunto Race 1 and SuuntoApp on Android 13.
-
I noticed that there is something wrong in descents. The power is sometimes overestimated. In the screenshot below, I reached 450W ; speed is high, but I was not forcing at all. Note that I have no cadence sensor. I never observed such errors in ascents.
-
@SergioB Not, it’s only used for the power zone gauge.
So if you have no idea of your FTP it doesn’t affect the estimates. -
@bubuche There is a grade lag at the start of a descent due to smoothing. So the calculation uses the previous flat section (0% grade) until the smoothing catches up. And even then you might be at -8% but the calculation uses for ex. -2%. At this speed, you are going above the assumed terminal velocity (which is too low), and get high power spikes,
Without a cadence sensor, I could zero the power when going downhill and avoid these short spikes.
So replace a false positive (what you see) with a false negative.
I guess the false positive is the worse issue since it impacts NP, averages, etc.So this needs fixing, but without breaking other cases. I’ll have a think.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login