Data Field: vPower - Bike Virtual Power

Welcome to
vPower
Version 1.9.3



The vPower data field app has been developed for those who are not fortunate enough to own an expensive power meter. Firstly, this is not 100% accurate. As you can imagine, there is a lot of variables at play to calculate power on the pedals accurately. This is my best attempt to take all these variables into consideration and developed the app with the following key features:

Configurable
- Now supports the following options to be set to improve calculation accuracy:
o Bike weight
o Tyre rolling resistance coefficient (default set for Michelin ProRace 3)
o Default ride position (Tops, Hoods, Drops or Triathlon)
o Trainer mode (default is off). Set this mode if you want to get training power for the supported trainer.
o Trainer - I only have a few at the moment, but will add as I get my hands on other trainer power curve formulas. If you have this, please send to me and I can add for you.
o Calculation - Display calculation as watt, or w/kg.

General
- Data is saved to FIT file and can be viewed in GC.
- Power is calculated if you are moving (cadence must also be over 40).
- Power consists of adding Vertical Power, Rolling Resistance, Drag & Air Resistance together to give total watts at a specific point in time (all explained below).

User Profile
- The rider weight is used from the User Profile.

Vertical Power
- The effort to elevate total mass (bike + body) up an incline.
- Incline is calculated based on the difference in altitude over a set period (based on the logging intervals).
- Gravity has been factored in at 9.81 kg m/s.

Rolling Resistance
- The force needed to counter rolling drag.
- Used normal road surface.

Drag
- The force needed to counter drag generated by the bike & wheels at specific speed.
- Used a set of Fulcrum R5 wheels to calculate drag.

Air Resistance
- The power needed to propel through the air at a specific speed.
- Rider calculated to be in the triathlon position (on tri bars).
- Air density calculated for sea level at 20 degrees Celsius.

----------------- Planned Updates------------------
- None at this stage, so please leave feedback.

----------------- Version History ------------------
1.0 - Initial release.

1.1 - Correct cadence value check; introduced value smoothing over last 3 results.

1.2 - Stability updates. Increased smoothing to 5 samples. Auto adjust size for different layouts.

1.2.2 - Stability updates. Crash should now be resolved.

1.3 - Updated for 1.1.3 SDK. Improved vertical power accuracy.

1.4 - Configurable options, Trainer support, Remove need for cadence.

1.5 – Calculation updates for improved accuracy.

1.6 - Option to calculate w/kg, updated firmware for better device support.

1.7 - Cadence over 40 for power to calculate. Save field to FIT file. Power max and avg in summary.

1.7.1 - Minor changes to fix FIT save & Strava upload issue (I hope)!

1.7.2 - Minor updates. Acceleration now part of formula.

1.8.0 - Support more devices. Averaging settings. Decimal fix for w/kg. Added a bunch of additional trainer support.

1.8.1 - Update issue with power spikes, and compiled for 2.4.2.

1.8.2 - Will now record power even when no cadence meter attached.

1.8.3 - Small fix to text for negative reading to avoid spike in FIT file (thanks Jan!).

1.9 - Re-look at all calculation to address power spikes.

1.9.1 - Improve power calculations (trying to base on actual power meter results). Added Feedback Omnium Over-Drive trainer support.

1.9.2 - Update for new Edge 830, 530, Forerunner 945 and MARQ.



Happy training!

  • Is it a joke?
    I'm waiting for this on my Edge 510...

    I asked for it a couple of weeks ago through the Garmin support...
    Have they implemented it ?!
    :eek:
  • Is it a joke?
    I'm waiting for this on my Edge 510...

    I asked for it a couple of weeks ago through the Garmin support...
    Have they implemented it ?!
    :eek:


    I wrote this data field for myself as I am using a FR920. Unfortunately this will not run on a 510, would have been nice!
  • I love what maths and some kind of tech can do for us!
    Congrats..
  • Are you using these formulas or similar?
    https://strava.zendesk.com/entries/20959332-Power-Calculations

    Moreover, do you have any suggestion for me to ask to the right people for the same development on edge 510?

    I fully agree with the approach of vPower.
    Maybe it can be sometimes not that accurate, but on uphills on standard conditions (90% of the times) it should be.
    An that's where you need it... if you are more or less doing always the same segments, you can in any case have a reliable reference point.

    I'm trying to use VAM 30s but it's not so easy to use if you are not doing a long uphill with a slope over 4-5%...
    vPower should be much easier to use, especially if the new data field could be also used as zones (1,2,3,4,5...)
  • @Pes75: Connect IQ is not supported on any of Garmin's Edge products right now, so for a feature like this to be added to an Edge, it would need to be implemented by the device team. If you'd like, you could start a thread over in the Cycling forum to discuss this feature, here:

    https://forums.garmin.com/forumdisplay.php?363-Edge-510

    You aren't the first to express interest in seeing Connect IQ on the Edge. :) Many of the people that develop our fitness devices are serious athletes themselves, so share a lot of the same desires as people like you. I'll pass along your comments to help add to the growing support to bring Connect IQ to the Edge. Thanks!
  • It would be nice to do so...
    The more we are, the more chances we can have to see it implemented.
  • Are you using these formulas or similar?
    https://strava.zendesk.com/entries/20959332-Power-Calculations

    Moreover, do you have any suggestion for me to ask to the right people for the same development on edge 510?

    I fully agree with the approach of vPower.
    Maybe it can be sometimes not that accurate, but on uphills on standard conditions (90% of the times) it should be.
    An that's where you need it... if you are more or less doing always the same segments, you can in any case have a reliable reference point.

    I'm trying to use VAM 30s but it's not so easy to use if you are not doing a long uphill with a slope over 4-5%...
    vPower should be much easier to use, especially if the new data field could be also used as zones (1,2,3,4,5...)


    I am not using the exact formula, but have validated that my formula is a lot inline with that of Strava. I used the same approach to calculate the unique elements, but I hav efactored in different variables.
  • I had a few comments about accuracy. The main input to the calculation is the frequency that the information (altitude & speed) is recieved. The more frequent the logging, the more accurate the display will be. So unfortunately I am bound by how often the Garmin device reports the speed and difference in altitude. I do not have direct control over what sensor is used (GPS or barometer), so I am relying on the accuracy on what is provided to me as a developer.

    Happy training!
  • Hi! Thank you for your work. Unfortunatly, im not able to run this app on my fenix3, im using speed/cadence sensor from btwin, hrm run strap. And i get a "iq!" logo. Fenix 3 is runnin 3.1 firmware. Any clubes why is it not working?
    Thank you
  • Thanks for the vpower field great idea, couple of queries.
    The size of text doesnt seem to change depending on how many fields are displayed.
    Is there any way to apply smoothing over 5 or ten seconds?
    Thanks again Joe