I'd like to create a standard for how Muscle Oxygen data is encoded when using ConnectIQ Apps and Data Fields.
The Muscle Oxygen FIT Profile uses the device_info messages to support multiple sensors in the FIT file. However, ConnectIQ only supports Record, Lap, and Session messages. It doesn't support device_info messages. Further, many data display software packages are not designed to use device_info data to keep track of data from multiple sensors of the same type.
The attached document shows a draft of how I'm proposing to support multiple MO2 sensor data in the FIT files generated by ConnectIQ within the constraints of the current functionality.
Please let me know if anyone has feedback on this methodology.
I'm the CEO at Moxy, but I'd welcome other Muscle Oxygen device manufacturers to use this same formatting to help enable more broad support for Muscle Oxygen data.
