FitToCSV.bat

In a .FIT file all string fields are treated as arrays with the null terminator, ‘\0’, acting as the separator. Some devices allocate a fixed amount of memory for a string, and the unused bytes can end up being filled with non-zero values. This makes the field look like it is an array of strings. For example, a device may allocate 16 bytes for a string but only use 8 bytes for the actual string followed by a \0. The other 7 bytes can end up being set to whatever values occupied that space in the device’s memory. If there are multiple random \0 values then the FIT CSV Tool will output an array of strings. The FIT CSV Tool uses the pipe character, ‘|’, as a separator. This is what you are seeing.

Right now there is no way to distinguish between good and bad arrays of strings when using the FIT CSV Tool. But you can safeully assume that the first value is the string that you are looking for.

This does not cause an issue when using the SDK to parse files, since most methods used to Get() a string value will return the value at index zero and ignore the other random strings. The FIT CSV Tool treats fields in a more generic fashion and if there is an array of values then all of the values will be written to the CSV file.