IMPORTANT! FIT Activity File Message Change

RE: IMPORTANT! FIT Activity File Message Change

Herb — Wed, 13 Dec 2023 11:59:59 GMT

I wonder if there's a reliable way to distinguish the two different variants at the start, before starting to process record messages. The best way I figured out so far is to look at the sequence of messages before the first

Event: FIT_EVENT_TIMER; Type: FIT_EVENT_TYPE_START

message. If there was an activity message followed by a bunch of session messages before that event, then the file apparently is in summary first format, otherwise it is processed as it was before.

Is there a more reliable way to tell?

Regards

Herb

RE: IMPORTANT! FIT Activity File Message Change

aaron — Sat, 11 Nov 2023 20:12:45 GMT

wowee! this is going to be interesting. popcorn.gif

RE: IMPORTANT! FIT Activity File Message Change

gie — Thu, 09 Nov 2023 03:13:07 GMT

Is there a way to

- Configure existing Fit files from summary last to summary first?

- Configure some incoming fit file (before Dec 1st, 2023) to be summary first? (for some user)

My goal is to test if our new implementation can resolve the summary first well enough

RE: IMPORTANT! FIT Activity File Message Change

Frederic — Fri, 27 Oct 2023 01:02:44 GMT

Could you please provide the same example file but coded with the "Summary Last" method in order to ensure that the results are the same for a given platform ?
Thanks