• Replies 2192 replies
  • Subscribers 81 subscribers
  • Views 322991 views
  • Users 0 members are here
Options
Related

HMs DIY #1-6

hundsmiachn
over 5 years ago

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
=======================================================================

 

  • over 4 years ago in reply to mcinner1

    The fact that Cadence does not show as connected is:
    On my eBike I connect POWER only and get power and cadence.

    But there are no Power ANTs in HM...

    Battery obviosly is not transmitted...

  • over 4 years ago in reply to mcinner1

    Hi

    Thanks for testing! There is a BikePowerDevice which I haven't added yet, but when I know that the basic ant stuff works I will add the rest (9 different types in total). Do you get the battery status in other datafields?

    Each device can only connect to one group (either Cad, SpeedCad ord speed not to all of them!). So we will have to try and make a list which device sends which data to which group:

    Available groups in the next release:

    BikeSpeed
    BikeCadence
    BikeSpeedCadence
    BikePower
    FitnessEquipment
    RunningDynamics
    Shifting

    BikeRadar, and LightNetwork I will add later maybe.

  • over 4 years ago in reply to hundsmiachn
    hundsmiachn said:
    Do you get the battery status in other datafields?

    No, no datafield available for that.

    Only can be checked at "Sensor-Info" under "Sensors"

  • over 4 years ago in reply to hundsmiachn

    One thing we will have to try. Because each device only sends data to one group, I think it is also important which group comes first in the layout. For example if a BikeSpeed field comes first, the device sends the data to this group, so you cant get any other data because its registered as BikeSpeed. If a BikeSpeedCadence field comes first, this group registers this device and you will get speed and cadence. But I am not sure if this is the case.

  • over 4 years ago in reply to hundsmiachn

    Unfortunately I don't understand Monkey-C programming, but from time to time I have a look at the Toybox:AntPlus listing to see if AntPlus for eBike.Battery and eBike.SupportLevel was released (I'm really waiting for that!), and I found with POWER:

    var calculatedPower = bikePower.getCalculatedCadence();
var calculatedPower = bikePower.getCalculatedPower();

    So it seems to me that the power-sensor can transmit power and cadence.
    (Of course no extra/other cadence-sensor will be connected or is necessary)

  • over 4 years ago in reply to mcinner1

    Now I'm going out to test the new avg. VAM datafield!

  • over 4 years ago in reply to mcinner1

    The BikePower will be in the next version, as well as RunningDynamics and FitnessEquipment.

  • over 4 years ago in reply to mcinner1
    mcinner1 said:
    Now I'm going out to test the new avg. VAM datafield!

    The new VAM avg. unfortunately is not realy working...
    Right after the start - the first value - is way off. I did several starts - on climb section, on flat section - the first shown value always is about 3000 to 4000 and then it keeps wrong at those high values...

    Positive: VAM-calculation stops at downhill now!

  • over 4 years ago in reply to mcinner1

    I have no idea what I could change. I do not divide by timerTime but by time in which the totalAscent was greater than in the second before that. 

  • over 4 years ago in reply to hundsmiachn

    So, I would suggest to leave it as it was before (elevationgain*3600/timertime) because it was perfect for real climb-training (without downhill).