HMs DIY #1-6

Thanks for reporting. Too bad it's not working right. Unfortunately I don't have an 830 to test - and I don't know anybody who has one.

SteveRodkey maybe you could have a look at other (compass) datafields and look if they work at your device - if one works (and the source code is available), hundsmiachn could have a look what's different to his code...

EDIT:
  Have a look at this one: Compass Orientation Course by Alexis Alexis Lecanu
  If this works - the source code of that datafield is available: https://gitlab.com/ravenfeld/Connect-IQ-Widget-Compass

Hi There

I could finally do some proper testing of the shifting fields for both DI2 and ANT (SRAM)

On DI2, all fine the 3 fields Index, Max and Size were giving good values

On ANT, the 3 fields Index, Max and Size retrieve a value, Max and Size ok, but Index is wrong, there is a (-1) Index variance vs real index (cog), so for cog 1 you get a 0 and for cog 12 you get an 11. this should be an easy fix using a calculated field, so you just show in the app ($V+1) instead of ($V), is that possible?

Finally, a more difficult one, no system is retrieving data for Battery (there is no battery field available for DI2, I tried all possible battery options to see if any was giving a value at all...., no success )

Thanks!

See picture for an example: Gear index value (11) should be equal to GearMax in the last cog (12)

Bodenseematze said:

BTW, I have something similar with data from another element: the "training effect" - it shows some value which also increments during a ride - e.g. at the end it shows 3.1
When I then stop the action and look at Garmin's overview pages, their training effect is always much lower (e.g. 2.2) - although they also say it's the "aerob training effect"...
So I assume they do some other calculation for that afterwards...?!

Really strange, because for me the DIY-TE (aerobic) on my Edge 1030 always matches the value displayed by Garmin at the end of the tour.

Maybe there is a different behaviour if one uses a powermeter - I do - and you?

Loukas said:

Finally, a more difficult one, no system is retrieving data for Battery (there is no battery field available for DI2, I tried all possible battery options to see if any was giving a value at all...., no success )

Agree: no battery even for Garmin sensors!

But: I get battery-data from my Stages powermeter!

So, it is not a general failure of the ANT-battery status.

To conclude the latest posts:

*Training Effect -> I get this value straigt from the SDK, so if it is wrong, I cant do anything about it. As I understand it, it is a combination of Aerobic and Anaerobic TE.

*ANT derailleur index starts at 0. So its always off by 1. Will change that in the next release, no problem.

*ANT battery: I use the same function for all ANT values to read out the battery value. Because it does give the correct value in some cases it is not completely wrong. I will investigate a little bit, if I can find something about this problem.

*So, the direction elements do work fine on the 1030 and 1000 edges, is that correct (north, start coord and coord) when standing still and when moving!?

They do not work correctly on the 830 when moving. When standing still the do work correctly.

Could anyone else with a different device confirm if the direction elements do or dont work there, maybe a F6 or a FR945!

The compass orientation widget only uses the compass heading, so it does not take into account in which direction I am heading when moving. It takes the Sensor.heading info, so if there is no compass I do not get a value there!

I will add the values I use for calculation to be displayed (current longitude, current latitude, current heading), maybe when can see better where the problem is.

regards

Erich

mcinner1 said:

Maybe there is a different behaviour if one uses a powermeter - I do - and you?

I do not - I only use a heartrate wristband - I've no idea, how this is calculated at all?!

I'll have a deeper look at the exact values (and differences) when I ride back home from work this evening...

hundsmiachn said:

So, the direction elements do work fine on the 1030 and 1000 edges, is that correct (north, start coord and coord) when standing still and when moving!?

Yes, at my 1030 the direction arrow (pointing to north) seems to work fine - at least it does not jump around and the shown direction matches my knowledge about the direction
Didn't test the other possibilities - I'll do and report...