HMs DIY #1-6

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.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!)
-----------------------------------------------------------------------
3.4.2
* switched to new SDK 4.1.5
* added devices: Edge Explore 2, Venu Sq 2, Venu Sq 2 Music Edition
-----------------------------------------------------------------------
3.4.1
* switched to new SDK 4.1.3
* added devices: Instinct 2S / Solar / Dual Power, D2 Air X10, D2 Mach 1, Descent G1 / G1 Solar,
Edge 1040 / 1040 Solar, Forerunner 255, Forerunner 255 Music, Forerunner 255s, Forerunner 255s Music, Forerunner 955 / Solar, Instinct 2 / Solar / Dual Power / dezl Edition
* fixed crash when windspeed was not available from device
-----------------------------------------------------------------------
3.3.1
* switched to new SDK 4.0.9
* added devices: D2 Air, Descent MK2/MK2i, Descent Mk2S, Enduro, epix Gen2, Fenix 7, Fenix 7S, Fenix 7X, Forerunner 55, Forerunner 945 LTE, Venu2, Venu2 Plus,
Venus 2S, Venu Sq, Venu Sq Music,

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

Top Replies

All Replies

hundsmiachn over 2 years ago in reply to DANY_DANI

Pacer setting must either be in the format T2:05:00 or P5:30

T means target time (here 2 hours 5 mins)

P means target pace (here 5:30 min/km)

DANY_DANI over 2 years ago

Hello, I send my XML as requested.

<?xml version="1.0" encoding="UTF-8"?>

</DIYLayout>

hundsmiachn over 2 years ago in reply to DANY_DANI

Whats your pacer config string?

Should be:

Pacer setting must either be in the format T2:05:00 or P5:30

T means target time (here 2 hours 5 mins)

P means target pace (here 5:30 min/km)

DANY_DANI over 2 years ago in reply to hundsmiachn

Now I don't have the clock and I'm working, but what do you want me to tell you about the application settings?

mcinner1 over 2 years ago in reply to DANY_DANI

DANY_DANI said:
but what do you want me to tell you about the application settings?

Please read page 33 of the Guidance.pdf (on top of this thread).

DANY_DANI over 2 years ago in reply to mcinner1

Solved !!!. It put P03: 50 and it had to put P3: 50.

Thanks at 2 !!!.

Right now I delete my comment and give it 5 stars for this great data field.

DANY_DANI over 2 years ago

Hello, adv. Cadence is not working well on my fr645 music watch, I have done tests with the native that Garmin brings and it marks half its field than the native Garmin.

Garmin = 180

DIY = 90

hotdogpartysausage over 2 years ago in reply to DANY_DANI

Which cadence sensor are you using? It sounds like you are referring to running cadence, so as the DIY value is half the Garmin value I'm wondering if there's something peculiar about running cadence that means the native garmin datafield displays it correctly but DIY doesn't

DANY_DANI over 2 years ago in reply to hotdogpartysausage

I don't use any cadence sensor, I only use the one for the clock, That is why I did the test of your application with the field that the clock has and it caught my attention that the data of your application is just half that of the Garmin data field. With the current cadence field it does not pass, that if you mark it correctly.

Thanks.

hotdogpartysausage over 2 years ago in reply to DANY_DANI

Just for the record it isn't my application. I'm just a user like yourself that is trying to help.

Only the app developer would be able to give you a definitive answer though I have a feeling that the watch accelerometer data used by the watch to determine cadence is different to what is presented to the CIQ application or the watch is manipulating the data to determine the cadence, which means that the cadence on DIY is reading half what the garmin datafield is reporting