Decoding Pace Band Files

I've tried running the FITToCSV and I've tried running the Decode CPP project on a Pace Band file and neither seems to correctly decode the FIT file (let alone re-encode it). Briefly scanning through the Decode project I suspect the messages in the pace band file (310 and 311?) haven't been coded for. Is the intention that developers would add support for such messages? Or is it that Garnin doesn't want people modifying Pace Band files?

mip over 3 years ago

Nvm, I was initially mislead by a post here that suggested the decode project can decode any valid FIT file. I realize now what that meant. Rolling some custom code specifically for the band files is only a couple dozen lines of code.

Ben FIT over 3 years ago

Pace band files are not intended to be edited or created by a third party. That is why messages 310 and 311 are not accounted for in the SDK.

Using the SDK, you can decode any FIT file. But some of the messages and fields may only be identified by an integer id and not by name. I am guessing that is what the other post was referring to.

With the FIT C++ SDK the Message Broadcaster class supports a generic Mesg Listener interface which will give you access to the anonymous message and field data (ids and raw values) read from the file. It is the subclasses of the Mesg class that provide the names and interpretation of the raw values.