CIQ error DataFields RunScribePlus & StrydPower

forum is teasing me not uploading my pics :cool:

have a look at this .... overview developer fields

FlowState, your wasting space line does not match the FIT layout

for your information
space for the field names is always reserved in every fit file containing developer data ;)

FlowState, your words, "That field name you're looking at in whatever tool that is seems to be based on the field number, anyway."

have a look at this ... fit file content viewed with hex viewer

Why don't you try fittocsv in the Fit SDK It makes the fit file much easier to understand.

I'll just post some examples of field names that Dozen Run writes:
eE
rE
pwr
tpRE
FellrnrRE

I'll just say they are clearly not meant to be displayed. And if any of them corresponds to a built-in field, they better use a native field number so 3rd party sites will know.

Sorry for my previous, now-deleted remarks. I guess it's frustrating when trying to explain something to someone and you're not believed. But my responses were inappropriate.

Yes, it is possible that 3rd party sites could look at a known field name for a popular app, especially if it's a non-native field like "beers consumed" or something. But a best practice for a native field like Power would be to use the native field number.

I would also suggest using fittocsv. I think you will find that most, if not all, 3rd-party apps that write power will use the native_field_num. With a value equal to 7, 19, 20 or 21, depending on whether it's a record, lap or summary, and what kind of power it is: current, average, min, max.

If not, then I apologize for spreading misinformation. It wouldn't be the first time.

Thank you FlowState for sharing your knowledge in a civilized manner.

Solved : third parties know what to do with the data according to the FIT specifications


Now going back to the main part of the original post.

Using two datafields at the same time, one from runscribe light and one from stryd power in the same workout.
Developer field names for runscribe light are empty.
Developer field names for stryd power are populated.

Using those datafields on their own in a single workouts.
Developer field names for runscibe light are populated.
Developer field names for stryd power are populated.

:)

thank you again FlowState for cleaning up and I appreciate your commitment with my grey cells

When you look at the previous posted screenshot from the FFRT tool,
you will see that all the info you talk about is there in that screenshot.

Being the field names and their corresponding numbers.

My main concern was the lack of populated field names from this combined FIT file (runscribe and stryd).

I see. I apologize for missing the primary point of your post (I had a feeling that I did). Didn't really get any sleep last night. It's great that you're doing all of this testing. That's a lot of commitment, effort and attention to detail that most people wouldn't go through.

I suppose I focused too closely on your comment about internal names versus GC names versus how 3rd party sites interpret the data. In any case, that doesn't excuse my previous reaction, and none of that stuff is important, anyway.

If those fields are blank, my educated guess is it has to do with the crash you described earlier.

Hopefully Garmin, Stryd and Runscribe appreciate what you are doing.

Stryd asked info and is investigating.
No news from RunScribe.

Thank you OnlyTwo & FlowState for the great work you are doing. I am also trying to make Stryd & RunScribe work together on the same Fenix 5x, for now without success.
I did several tests and evaluated the tables generated on golden Cheetah.

I have a question to ask, if I use Stryd & runscribe light, what data I'll see on WKO4 +.
Thanks.