HMs DIY Wings for life World Run Edition

This i a port of my original DIY datafield: https://apps.garmin.com/de-DE/apps/b0346b71-bf01-4070-96d6-3de66dcc8233 Please read the important notes below! To create a layout, download the windows executable here: http://public.stattegg.info/WFL_HM_DIYD_2.3.0.zip (examples for multiple devices are included) It has special values for the WINGS FOR LIFE WORLD RUN * Ahead time for a given target distance/time * Predicted target distance/time * Distance to catcher car * Distance correction. By pressing the lap button distance is rounded to the nearest kilometer (4.8 to 5.0km; 6.1 to 6.0km). When correction is active it is indicated by the "WFL offset indicator" (little yellow circle (not available on low memory devices)) When lap button is pressed within 30 seconds again, the offset is reset. The values are calculated by elapsed distance/time and average pace over the last XX (adjustable) seconds (300 for 5mins). Ahead time and predicted distance are written into the fit file (except low memory devices). You can create your own layout by creating a configuration string. ----------------IMPORTANT-------------------- Low memory devices (FR235, FR630, F3, 920XT, ...) can only add these values and the limit is about 15 elements and no dynamic colors are available! * WFL Average pace * WFL ahead time * WFL pred distance * WFL pred time * WFL distance to Catcher Car * Clock time * Timer time * Elapsed Distance * Current pace * Average pace All other devices have all above and these additional values available: * Maximum pace * Total ascent * Total descent * Curr. heartrate * Curr. heartrate %HFmax * Average heartrate * Maximum heartrate One element with a value type "WFL Average pace" has to exists (it doesnt need to be visible, it can be in the background), because the calculations base on this value. The field in element "WFL Average pace" -- "Nr of values" in the designer represents average over seconds, default is 5min (300s). One more important thing is when pressing lap button for setting the exact distance at a kilometer marker: You have the option to clear the offset if you press the lap button again within 30s. BUT you will have to press the lap button again at the next kilometer marker if you have autolap enabled!! The reason for that: Because I cannot differentiate between a lap button press and an autolap event, you would get an autolap event 1km after you have reset the distance and then the offset would be set again. ------------------------------------------------------- Because of memory limitations and the complex calculations for the prediction I had to remove some available values from the original version. Forum thread for this version: https://forums.garmin.com/developer/connect-iq/f/showcase/207993/hms-diy-wings-for-life-world-run-edition Original forum thread: https://forums.garmin.com/developer/connect-iq/f/showcase/206277/hms-diy-1

======================================================================= RELEASE NOTES ----------------------------------------------------------------------- 2.3.1 * added new devices: fr55, fr255, fr255m, fr255s, fr255sm, fr955, fr265, fr265s, fr965, fr945lte, fr745, fenix7, fenix7s, fenix7x ----------------------------------------------------------------------- 2.2.1 (datafield only) * fixed crash when avg speed was zero ----------------------------------------------------------------------- 2.2.0 * bringing datafield to latest version of DIY designer ----------------------------------------------------------------------- 2.1.1 * added default layouts for all devices. Still all layouts can be changed in the designer! * added support for imperial units (code only, layouts have to be adapted for miles manually) ----------------------------------------------------------------------- 2.1.0 (datafield only) * fixed playing sound/vibration in some cases ----------------------------------------------------------------------- 2.0.8 * added sound and vibration when target distance reached and/or catched by car (sound at 200m, 150m, 100m, 50m and 0m) ----------------------------------------------------------------------- 2.0.7 * target distance calculation is now slightly more precise ----------------------------------------------------------------------- 2.0.6 * memory optimization * fonts.txt adjusted for Fenix6X Pro * added max element check for all devices, to avoid running out of memory. Current max elements: low mem devices: 15 medium/high mem devices: 60 ----------------------------------------------------------------------- 2.0.5 * bugfix for average speed calculation ----------------------------------------------------------------------- 2.0.3 * small bugfix for the WFL distance offset indicator ----------------------------------------------------------------------- 2.0.2 * fit file writing starts now at 1 min to avoid wrong accumulating data at start * some minor optimizations ----------------------------------------------------------------------- 2.0.1 * complete rework of the config string parsing, thus the string must be created again with new designer version! * low memory devices are now supported, but with some limitations: no dynamic colors, only a handful additional values (see description) * WFL average speed uses now also seconds from "nr of values" for averaging, like all the other fields (this was minutes in the old versions)!! * added example layouts for several devices in the designer zip. ----------------------------------------------------------------------- 1.3.1 * removed accidently activated trial mode * memory optimizations ----------------------------------------------------------------------- 1.3.0 * corrected wrong conversion when using "adapt" button in the designer * minor bugfixes for WFL values ----------------------------------------------------------------------- 1.2.9 * correct minor deviation of average speed calculation * switched WFL average pace to WFL average speed ----------------------------------------------------------------------- 1.2.8 * removed support for CQ1 devices like the FR230, FR235 ... they have simply too less memory to run the dynamic datafield ----------------------------------------------------------------------- 1.2.7 * memory optimizations * WFL fields values corrected after car distance reaches 0 ... =======================================================================