Chart containing Developer fields from FIT files

@david it would be great if we could show any developer field included in a fit file for custom charts.
Similar to using @variable_name in WKO

I do have that on the todo list. Is it something of general interest?


Hi ! As a GArmin IQ developer this would be very interesting at least for me, but also for users of devices like BodyRocket, etc…

1 Like

That’s the point for this request. It will open intervals support to any developer field according to all users needs.

1 Like

I am just about to release a new version of my Windows app fitnesshrv that can save data in FIT files and it relies on and uses developer fields extensively.

More specifically, it can capture data from multiple ANT+ or BLE sensors (HRM, PM, FEC, Sauce4Zwift, MO2) and save it to FIT files. Where the second device (e.g. second Moxy, second Power Meter etc) has its data added as a developer field. E.g. “power sensor 1234”.

This is intended to make (for example) dual-recording for power trivial.

Being able to display developer fields will make comparison easier.

DFA Alpha1 and Artifacts are generated if you record an HRM sensor (developer fields Alpha1, Corrections and Artifacts.) That would be a good chart to add.

And if you have a Polar H10, you can (optionally) capture ECG data (developer field uVolts), which is 130 samples per second.


DFA-a1 is already in Intervals and @david reads it in the fit generated by the Garmin IQ field alphaHRV, just like respiratory rate coming from the same IQ field.
If you will be using a different name for the field where you are saving it in the fit, it should simply be a matter of having a mapper. But some might be interested in keeping both a1 traces from your app and from the IQ field. So not sure how that should be handled.
There are already two ‘resprate’ fields in the FIT when you use the alphaHRV IQ. There is one in a Garmin ‘special field’ that can only be written by Garmin and a second one from alphaHRV in a dev field. Intervals gets only the one from alphaHRV which is a good thing because the Garmin resprate field prooved to be much less accurate.
There are more dev fields already in Intervals:

It’s probably best if you contact david directly and provide him the specs of the special fields you will be using. I’m sure you guys can work out a perfect solution to handle these ‘double’ fields.
To give you an idea where it stands at in Intervals, here’s a screenshot from one of my runs where I merged the run data from my Coros watch with the resprate and a1 from my Garmin Edge running simultaneuosly.