This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin / DI2 - The data is there because Sram's AXS app reads it - why not in Garmin's App???

Totally bizarre - and I know this subject has been raised over the past.

I recently read that SRAMs AXS app can be connected to DI2 via Garmin Connect. 

Tried it.

Yep.

I can look at my rides and all my gear changes, power per gear, etc. etc. via SRAM (ie not Shimano).

So Garmin collects the data on / via the web....so why not show it in your apps?

Makes. No. Sense.

  • So Garmin collects the data on / via the web....so why not show it in your apps?

    Could you post a link to one of your activities using the gear device? Please make the activity visibile to Everyone, before posting the link (see the padlock symbol on the activity page). I'll look whether the data is accessible in the background. If it is, it would be theoretically possible making them visible on the Activity page with the help of local overrides.

  • This is the activity on garmin https://connect.garmin.com/modern/activity/4933876763

    The only connection between my AXS account ( axs.sram.com ) and my bike is via Garmin Connect....here is a screenshot of the gear use from the same ride.

  • Well, I do not see directly the gear info in the background data, but perhpas the AXS server uses some of the other available fields for their stats. For example, I guess the gear changes could be perhaps calculated with the help of the ratio of the values directFractionalCadence and directBikeCadence. Not having any powermeter or gear device, I am not very familar with the terms and hence am not quite sure how they are used, but I suppose the ratio between the two values should change according to the gear change. I just do not see how the front and rear gear change could be distinguished.

    Below, there are the values available in the data:

    1. metricsIndex: 0, key: "sumElapsedDuration", unit: {id: 40, key: "second", factor: 1000}
    2. metricsIndex: 1, key: "sumDistance", unit: {id: 1, key: "meter", factor: 100}
    3. metricsIndex: 2, key: "directPower", unit: {id: 10, key: "watt", factor: 1}
    4. metricsIndex: 3, key: "directAirTemperature", unit: {id: 227, key: "celcius", factor: 1}
    5. metricsIndex: 4, key: "directTimestamp", unit: {id: 120, key: "gmt", factor: 0}
    6. metricsIndex: 5, key: "sumDuration", unit: {id: 40, key: "second", factor: 1000}
    7. metricsIndex: 6, key: "directCorrectedElevation", unit: {id: 1, key: "meter", factor: 100}
    8. metricsIndex: 7, key: "directHeartRate", unit: {id: 100, key: "bpm", factor: 1}
    9. metricsIndex: 8, key: "directUncorrectedElevation", unit: {id: 1, key: "meter", factor: 100}
    10. metricsIndex: 9, key: "directSpeed", unit: {id: 20, key: "mps", factor: 0.1}
    11. metricsIndex: 10, key: "directElevation", unit: {id: 1, key: "meter", factor: 100}
    12. metricsIndex: 11, key: "sumMovingDuration", unit: {id: 40, key: "second", factor: 1000}
    13. metricsIndex: 12, key: "directLongitude", unit: {id: 60, key: "dd", factor: 1}
    14. metricsIndex: 13, key: "directFractionalCadence", unit: {id: 92, key: "stepsPerMinute", factor: 1}
    15. metricsIndex: 14, key: "directLatitude", unit: {id: 60, key: "dd", factor: 1}
    16. metricsIndex: 15, key: "directBikeCadence", unit: {id: 103, key: "rpm", factor: 1}
    17. metricsIndex: 16, key: "directVerticalSpeed", unit: {id: 20, key: "mps", factor: 0.1}
    18. metricsIndex: 17, key: "directRightPedalSmoothness", unit: {id: 6, key: "dimensionless", factor: 1}
    19. metricsIndex: 18, key: "sumAccumulatedPower", unit: {id: 10, key: "watt", factor: 1}
    20. metricsIndex: 19, key: "directRightBalance", unit: {id: 6, key: "dimensionless", factor: 1}
    21. metricsIndex: 20, key: "directLeftTorqueEffectiveness",…
    22. metricsIndex: 21, key: "directRightTorqueEffectiveness",…
    23. metricsIndex: 22, key: "directLeftPedalSmoothness", unit: {id: 6, key: "dimensionless", factor: 1}
    24. metricsIndex: 23, key: "directPerformanceCondition", unit: {id: 6, key: "dimensionless", factor: 1}
  • Did either of you find a solution to this one year later?  I am now too in this boat but it is annoying having bits of the data visible in different places.  Would be good to have the gear stats in garmin connect.  I find trailforks works best with jump data, then axs for gears and strava for segments.  It would be awesome if Garmin Connect did it all better so it was more concise. 4 places to look is enough, surely i can get my axs gear data in one of the other 3 platforms (garmin connect being the most likely).

    I have sram GX AXS mech so not sure if the data is recorded differently to robertc17's shimano di2. 

    connect.garmin.com/.../7387587735