Is there a way to detect the byte-order for developer fields? I have FIT files with Stryd power sensor data that have reversed byte order in developer fields with the base type FIT_FIT_BASE_TYPE_UINT16. Other FIT activities recorded with the same hardware (actually the same device, just a different type of workout) contain developer fields with the correct byte order.
I suspect the recording device's firmware is writing the data incorrectly, but somehow these mangled field values show up correctly in the Garmin Connect web interface. So Garmin must detect the reversed byte order when importing the FIT data.
Thanks for any pointers
Herb