App Icon

Sensible VAM


This datafield shows live climbing rate / vertical speed / VAM (velocita ascensionale media, ital.). </p><p>It does this much better than the stock vertical speed data fields,</p><p>which seems to rely on GPS data, which is the worst sensor for the job.</p><p></p><p>A gradient field is also available.</p><p></p><p>Details:</p><p></p><p>- Uses the best available data: barometric altitude, GPS as a fallback.</p>

What’s New

1.1.2:</p><p>- Support Edge 530/830, rebuild with new SDK.</p><p>1.1.1:</p><p>- Further layout improvement.</p><p>1.1:</p><p>- Adjust font size to field size.

Additional Information

  • Edge® 1000 Edge® 1000
  • Edge® 1030 Edge® 1030
  • Edge® 1030, Bontrager Edge® 1030, Bontrager
  • Edge® 130 Edge® 130
  • Edge® 520 Edge® 520
  • Edge® 520 Plus Edge® 520 Plus
  • Edge® 530 Edge® 530
  • Edge® 820 Edge® 820
  • Edge® 830 Edge® 830
  • Edge® Explore Edge® Explore
  • Edge® Explore 1000 Edge® Explore 1000
  • Edge® Explore 820 Edge® Explore 820
Average Rating: (2 Ratings)

Kornelius Krieger
April 21, 2019 | Version 1.1.1

Very useful tool! This is the second best method after powermeter for pacing on hill climbs and also to train using power on hill climbs. On my bikes without powermeter I use this APP to estimate my power output on the hill climbs. I use it for grades bigger than 5%, then my speed is below 15km/h, means wind resistance can be neglected. I made a chart based on my weight + bike weight and used tools on the internet (bikecalculator) to correlate VAM to power out put.

Niko Checkow
March 30, 2019 | Version 1.1.1

Useless! Neededs is something that shows VAM as a 3s or 10s average. This one takes a long time to settle on a average value. Perhaps on long climbs acceptable but useless on shorter ascents. Also starts with a value that is not zero, like it should be. It reads -300 or something like that.

Developer Reply
April 1, 2019, flyingflo

Thanks for your poorly researched feedback. I'll try to explain your issues. - The intended audience for this datafield are riders, who are unsatisfied with the stock vertical speed datafield of Garmin devices. If you find it useless, please use the stock datafield. - Averaging time can be chosen in the App-Settings. Try to set the filter length value to 1. This will result in a three seconds averaging (given the three seconds sample reate), as you wish. However, VAM as a performance metric doesn't make much sense on short climbs, thus the default value applies more smoothing and higher accuracy. - The settle time depends solely on the averaging filter length. The altitude sensor resolution is limited, thus accuracy requires longer filters. Everybody is free to configure it in the settings. - If you see a non-zero reading while stationary, please watch the altitude value and you will see that it changes as well. This is most likely the result of the automatic GPS-based calibration of the barometric altitude sensor after the initial GPS fix. The datafield correctly processes the changing altitude. I've never seen this after the calibration is done. The datafield can't distinguish if you're riding and elevator or if the sensor calibration is running, it just processes altitude changes over time.

Sorry, no statistics available yet.