Cycling Power Estimator

mickywickyftw

I think I’ve worked it out - it was a typo! Please try the latest build.
It meant that terminal velocity was ignored when going downhill without a sensor - resulting in those high power readings.
Let me know, as I cannot test this for a couple of weeks now.

bubuche

@mickywickyftw said:

I think I’ve worked it out - it was a typo!

Ok, I’ll try in a few days

bubuche

@mickywickyftw said:

I think I’ve worked it out - it was a typo!

Changing a + to à - helped a lot
This is far better in descents.

In a previous post, you requested the avg speed and power on a section. How? I can only get this for segments of 1/5/10 km.

mickywickyftw

@bubuche I would use Runalyze or another external platform for that.
Now I‘ve been using the latest updates for a bit, I think we‘re there.
I thought about using predicted wind from the weather app, but you end up losing accuracy as soon as buildings are involved.
I will look at using the accelerometer perhaps, but felt it was overkill when I started with this app. It might solve the grade latency issue though. I‘ll play around with it at some point.

phck9b

Hello,
Does this app work on Suunto 9 baro?
I tried but I only get a black screen and back to the main menu after a while.

mickywickyftw

@phck9b It works in the simulator, but I don’t have a S9 Baro device to test. It may be crashing due to low memory, I refactored it once to make it fit in the Vertical 1’s runtime, so that’s likely.
If you have VS Code, maybe you can share the watch’s log file.

Ecki D.

@phck9b I had a freeze on 9PP at the first time I tried to enable it with live-tracking in parallel. After restarting the watch both do work now. So maybe just use one app and restart the watch before.

phck9b

@Ecki-D. Thank you very much! I’ll try next time

phck9b

@mickywickyftw
Thank you, but I haven’t VS Code. I wiil try the solution given by Ecki d (next post).

mickywickyftw

New version pushed with one change to use a median of 3 rule on the acceleration - ignores single-sample spikes and should smooth out the power readings.
I’ve also added text in the description to say that so far I only know of 9PP and above watches being able to run it.
@phck9b let me know how you get on with your S9B.

SergioB

Finally I was able to test this wonderful app with a cadence sensor. The app is GREAT, thank you a lot!
Just a minor thing: even if I didn’t have any speed sensor connected to the watch (only a cadence one), above the speed indicator appeared “POD” instead of “GPS”. Nevertheless, the app was working properly (showing GPS speed)

mickywickyftw

@SergioB thanks for the feedback, glad you like it! It’s my primary screen when I cycle known routes. I‘ll look into that POD/GPS label display, and also that when stopped speed is „—„ instead of zero. For the next minor release.

pilleus

Works fine, but I cannot choose anything of the power options in a custom sport mode on the main screen. It’s always “—”.

The additional screen of the app is showing the power (according to the choosen interval).

Is it because the power is a calculated value and not broadcasted via ble from the cadence sensor?

pilleus

I tested the app with my fatbike in comparison to my mountain bike with power meter.

Identical route, 53 km, 860 meters of climbing, avg speed 20 km/h, avg heart rate 112 bpm, 21 °C.

The only difference is the avg power. Mountain bike 160 W, fatbike with the app (cadence meter connected, speed from GPS) 155 W.

That’s quite good.

One thing to think about is the white marker on the outer ring with the power zones. On the white screen it’s hard to see. Maybe a black marker would be better?

Thanks for your work, I appreciate it. ‍️

pilleus

Another idea. I would prefer that the actual heart rate is shown on the screen, as outer circle instead of the power zones or at the bottom of the screen instead of the duration. Maybe as options to choose in the app?

mickywickyftw

@pilleus Hey, that’s really cool you doing the comparison, thanks! 5 W avg (3.2%) off, given the number of variables that won’t be 100% correct (weight, for a start), this is really good.
I noticed the same thing with the white outer marker around 3 weeks ago, I’ll fix it in the next build.
Adding an option for a HR gauge rather than Power might be more difficult, but I’ll look into it.

pilleus

@mickywickyftw

Thanks for looking into it. I think a gauge is not necessary if you change the duration at the bottom of the screen to the actual heart rate (may be as option to choose).

And the app works more accurate with a speed sensor than with the GPS speed, which is always behind the actual speed.

mickywickyftw

@pilleus I couldn’t figure out a way to tell what theme is enabled on the watch, so the indicator is now 2-tone, that should work with both light and dark themes.