BikeMighty: Ride Fuel & Physiology Know what your effort is costing and when to fuel. This isn't a simple calculator. It's a whole runtime engine that is dynamically adjusting true burn based on your effort, physiology and a little math and exercise science mixed in for good measure. BikeMighty is an app that estimates how your ride uses carbohydrates and fat, tracks your modeled glycogen reserve, and shows when your current effort may outlast your fuel. It uses live power and heart-rate data to help you pace long rides and follow a fueling plan. BikeMighty updates its estimates as your effort and fatigue change. A color-coded status gauge gives you a quick read; detailed screens show the numbers behind it. How the estimate works: Think of fat as a large, slower energy source and glycogen as a smaller reserve your body can use quickly. BikeMighty estimates your starting glycogen from weight and training status, or from a custom value. FTP and VT1 anchor the intensity model; power and heart rate shape its estimate of the carb/fat mix. Harder efforts raise estimated carb burn. A smoothed burn trend and remaining reserve drive the time-to-exhaustion estimate. Heart rate also establishes a heart-rate-to-power baseline, so the app can track later drift. As fatigue and drift build, the model raises its estimate of the energy cost of riding. On your ride: - Fuel reserve and status: See modeled glycogen remaining and color-coded warnings as your reserve or predicted time-to-exhaustion falls. - Burn and trend: Track estimated carbohydrate burn now and its recent trend. - Fuel prompt: See an estimated amount to take based on your current deficit and near-term demand. - Ride totals: Review carbohydrate, fat, and calorie estimates, plus your fuel-plan intake and carb deficit. - Choose your view: Use the graphical one-field display for a quick read, or turn it off to see more engine metrics at once. Set up your profile: In Garmin Connect, enter your weight, training status, FTP, maximum heart rate, and planned carbohydrate intake. Add resting heart rate, VT1 (aerobic threshold), and lactate-threshold heart rate for a more complete profile; BikeMighty estimates threshold defaults when VT1 or LTHR is blank. You can also set a custom glycogen reserve or lower your starting fuel level for a fasted or unusually low-fuel start. If one sensor drops, the app can estimate from the other, but both a calibrated power meter and heart-rate monitor give the best results. For data-focused riders: Advanced fields expose the model's working values: Burn is the current carb rate; EWMA is the smoothed rate used in projections; Deficit compares estimated carbs burned with assumed intake. FuelMix shows the modeled carb share. Strain combines power, heart rate, fatigue, and drift. BodyEff is modeled gross metabolic efficiency; Ftg tracks accumulated fatigue; Drft tracks changes in the heart-rate-to-power ratio. VT1 and LTHR show threshold anchors, with tags indicating whether you entered them or BikeMighty estimated them. The fueling rate is counted as assumed intake when estimating your carb deficit; it does not confirm what you actually ate or refill the modeled glycogen reserve. All fuel, reserve, and exhaustion values are estimates, not direct measurements. Use your real-world experience and sensor data to judge them.

v1.1.6 - bug fix removed carb burn and trending from 1-field graphical dispaly because it was wildly difficult to get it to work properly on the different Edge 10x0 devices without causing performance problems. It may return at a future date. v1.1.5 - bugfix carb burn/trend graph accidentially enabled on low resolution devices. - UI updates to font sizes to maximize how large they can be for readbility - UI centered Graph and Stats text on the button to toggle between 1-field modes. - Clamped graph samples due to being to close to limits. v1.1.3 - Feature on touch capable devices added toggle button on 1-field screens to change between graphical and engine run-time metrics views. The toggle button is on the status pill at the bottom of the screen. Known formatting issues on some devices will be fixed later. - Feature on high resolution devices Carbs card which now shows current and trend values but also includes a rolling window graph of current and trend. Window grows up to 20 minutes lookback. I only have two Garmin devices so I can't verify it looks correct on some devices. - UI fixes: lots of cleanup to make fonts, spacing and formatting allign. Multiple fixes for readability across device types that have different screen sizes. There are too many little display issues to list but I think I got most of them. v1.0.10 - bugfix possible crash saving values as non-integers - feature increased font size and space on 1-field display on smaller Edge devices v1.0.9 - bugfix app may fail to load with uncaught errors on Edge 530/830 v1.0.8 - feature improve readability on Edge 1050 - Added hopes and dreams mode when you run out of fuel v1.0.7 - feature made carb fuel tank more intiutive - bugfix Thermal Drift added before ceiling check could allow penalty to slightly go above limit v.1.0.6b - feature minor update to graphical design v1.0.6a - feature enabled graphical 1 field as default, can view text version in settings - feature now displays both Kcal and KJ. - no bug fixes, yay!! v1.0.5 - update asymetric lactate clearance to several minutes for substrate crossover - exposed detetected HR to power ratio in UI - exposed fuel plan in use. - feature Include miles/km estimate on status pill - Include both carb and fat current percentages from runtime v1.0.4 -feature Asymetric Weighted Moving Average for the time to depletion -update a few labels for clarity v1.0.3 -bugfix Low carb burn floor locked after 120 minutes if no power meter used -bugfix Gross Metabolic Efficiency (GME) accidentally tied to moving average instead of heat and fatigue -bugfix Coasting and coffee stops triggered superhuman recovery sometimes -bugfix Display fix on certain Edge 850 layouts -bugfix Inputting 0 carbs in fueling plan disabled the 5min target -bugfix App started calculating on load instead of on ride start.