HMs DIY #1-6

Store Link

Because I want to keep this datafield and the app free for use I would be very grateful about a small donation to PayPal

A detailed description of how to use it can be found here: 

HMs_DIY_GUIDANCE.pdf
HMs_DIY_ANLEITUNG.pdf

Thanks very much to mcinner1 for putting so much time into this documentation!

Designer download

You can contribute on my github page.
You can upload your layout so others can use it as well.
Also any changes to the fonts.txt can be updated there as well.

Garmin_HMsDIY

=======================================================================
RELEASE NOTES
=======================================================================
-----------------------------------------------------------------------
3.6.2
* switched to new SDK 7.2.1
* added devices: Approach S7 42mm, Descent Mk3 43mm /Mk3i 43mm, Descent Mk3i 51mm, Edge 1050, epix Pro Gen2 42mm, epix Pro Gen2 47mm / quatix 7 pro, epix Pro Gen2 51mm / D2 mach 1 pro / tactix 7
Fenix 7 Pro, Fenix 7 Pro Solar, Fenix 7S Pro, Fenix 7X Pro, Fenix 7xPro Solar, Forerunner 165, Forerunner 165M, Venu 3, Venu 3S, Vivoactive 5
-----------------------------------------------------------------------
3.5.1
* switched to new SDK 4.2.4
* added devices: FR265, FR265S, FR965, GPSMAP 67/67i, Marq (Gen 2), Marq (Gen 2) Aviator, EDGE 540, EDGE 840, Instinct 2x Solar
* added two new font types GLANCE, GLANCENR (only available if device supports it!)

for full releasenotes see: releasenotes.txt
=======================================================================

 

  • that would be great... thank you!

  • Version 2.4.3 is now available on clone #4.

    Sorry for the long time with no updates, didn't have really much time for the project lately.

    PLEASE COPY/PASTE THE LAYOUT STRING AGAIN with new designer version, the bit structure of dynamic colors has changed!

    Designer:

    http://public.stattegg.info/HM_DIYD_2.4.3.zip

    2.4.3
    * it is now possible to set a dynamic color value to be hidden. Instead of setting the color for this element when it is in the value range, the element will be hidden.
    * maximum value for dynamic color value is now 262144
    * normalized power starts to be calculated 30s after activity start.
    * made the sample text for the elements in the designer changable
    * XML File is now saved with BOM for better UTF8 compatibility
    * it is now possible to add different layouts for black and white background color.
    be aware because of memory issues the check for background color is only done when
    datafield is opened, it is not changed dynamically at the moment.
    * fixed "Time to next p. (avg. sp)" showing wrong value
    * fixed wrong arc degrees when pressing "Scale for device" button in designer
    * added fontmapping for vivoactive4

    I would appreciate any feedback, specially with normalized power. Wasn't able to test it completely.

    regards

    Erich

  • Version 2.4.3 is now available on clone #4.

    Sorry for the long time with no updates, didn't have really much time for the project lately.

    PLEASE COPY/PASTE THE LAYOUT STRING AGAIN with new designer version, the bit structure of dynamic colors has changed!

    Sorry for my (maybe stupid) question:

    Does that mean, we have to be careful to use the new designer-version only on clone #4 ?
    (Since clones #1-3 were not updated yet - they will crash with strings from the new designer version?)

  • Hi

    No, it will not crash. It should be no problem to use new designer with old datafield. 

    Regards 

    Erich 

  • I would appreciate any feedback, specially with normalized power. Wasn't able to test it completely.

    Here is my test for NP and hidden elements:

    1) Hidden Elements:
    I set a Exclamation mark - big and red - to appear only if HR > 140.  Works as it should!

    2) Normalized Power
    Now works as it should from the beginning as long as the activity is running - no pause:

    On pictures below:
    Upper left: NP Power according IQ-data field APP BUILDER
    Upper right: NP Power according Garmin's original data field
    Middle section: HMs data fields: w/zero: taking 0 Watt into account, below: without calculating 0 W.

    NOTE:
    According to my device settings on the Edge, power zero values should not be included.
    That's what "avg. Power" is done correctly.
    But with Garmins NP the zero values are taken into account.

    HM's NP-values are fine up to this point!

    Next section: a pause (Autopause):

    As you can see - HM's NP calculation is apparently not interrupted by a pause but continues.
    While Garmin's NP remains constant, HM's NP decreases during the pause.

    That's the only thing that's probably not okay.

  • So, if I read it correctly I should not add any values when activity is paused, is that correct? Is that the only thing that is wrong?

    Is the NP including zero values also needed then ?

    regards

    Erich

  • - yes: no calculation during pause - and yes: I found nothing else to be wrong.

    - and second answer seems to be a No. Not needed...

  • Ok thanks.

    Already fixed the NP for pausing...

    I will leave the NP with zeros in because maybe someone still  needs it, and it doesn't hurt I think.

    I will wait one ore two days till the next release if something else comes up.

    regards

    Erich

  • New version 2.4.4 is available on all clones.

    Latest designer version is also 2.4.4:

    http://public.stattegg.info/HM_DIYD_2.4.4.zip