I have been developing a custom data field to display a value derived using muscle oxygen consumption. I've got it working fine and it will display as a custom data field. To do this I basically extended the example code in the ConnectIQ SDK for MoxyDisplay. The issue is that the watch has native capabilities to connect to the moxy sensor, and there seems to be a race condition where either the custom data field connects, or the native field connects. This results in only one of the fields being able to be displayed. With the limitation on how many custom fields I can create I'd like to take advantage of the native fields. Thoughts on what I should do?
+1 for adding support for muscle oxygen data in Activity.info.
The watch can only connect to 1 sensor using 1 ANT channel. The native connection uses 1 channel and a CIQ data field with a Generic ANT channel uses 1 channel so they can't connect to the same sensor at the same time. Making the MO2 data available in Activity.info would be a nice solution.
I talked with the ANT team about this today, and they explained that if an ANT sensor is already connected natively you cannot open a generic channel to that same device by design. I don't really have any more detail about why this decision was made. I think the approach we'd want to take is make native data available to CIQ apps, since it's already got a channel to the device through the native interface (which MoxyRoger has already asked for).
I talked with the ANT team about this today, and they explained that if an ANT sensor is already connected natively you cannot open a generic channel to that same device by design. I don't really have any more detail about why this decision was made. I think the approach we'd want to take is make native data available to CIQ apps, since it's already got a channel to the device through the native interface (which MoxyRoger has already asked for).
I figured this was the case. This also makes sense to me as the logical solution. Hopefully we won't have to wait too long for a patch =)
