• Replies 6 replies
  • Subscribers 14 subscribers
  • Views 1571 views
  • Users 0 members are here
Options
Related

Saving to FIT files

enki42ea
Is it correct to say all data saved using the new functionality to save to FIT files will be saved as a developer data field? So for example muscle oxygen sensors like BSX and Moxy can't use a ConnectIQ app to save the data from the sensors like section 6.3.1 of the "ANT+ Device Profile - Muscle Oxygen"?

Also currently there is no unifying standard to developer data fields so that means there is no easy way for developers to say I'm sorting X data and by X I mean the same data as this other app that stores the same thing. As in the way an Edge 810 and a 920xt both save power meter data to FIT files in the same way so anyone looking at the files doesn't have to care who generated the file but that they want the power data.
  • At the moment, you're correct. During the beta period, this feature has allowed writing completely custom data to the FIT file that does not replace existing profiles, but I believe this is being changed for the full release to custom FIT data can be written to standard FIT profiles.
  • So all connect iq devices will support all of the FIT file spec including for parts that the device doesn't support? So for example seems like the fr 630 is the only watch that supports muscle oxygen so would the 920xt not support those fields because it doesn't support that sensor type or will it have supoprt because it can do anything a fit file can do.
  • Former Member
    Former Member
    The previous comment from us is a bit misleading. The current design that is expected to release with the 2.1/1.3 VM allows dev data to be tagged with the field ID of the native data that is being written to this field. The data will still be written using the extended dev data protocol seen in the preview SDK.

    My understanding is that there will be additional features added to the decoding tools that will allow extended dev data to be merged with the native data by the consuming app if desired.
  • The previous comment from us is a bit misleading. The current design that is expected to release with the 2.1/1.3 VM allows dev data to be tagged with the field ID of the native data that is being written to this field. The data will still be written using the extended dev data protocol seen in the preview SDK.

    My understanding is that there will be additional features added to the decoding tools that will allow extended dev data to be merged with the native data by the consuming app if desired.


    the official date for write back into fit files was Q1/2016

    is there an update on timescales for this facility to support MOXY for 735xt and/or 920xt. thank you
  • Support Muscle Oxygen/ Power sensors in firmware older Forerunner models

    I have a Forerunner 620. I have seen there is a beta release firmware for Forerunner 630 supporting the Muscle Oxygen sensors. http://www8.garmin.com/support/download_details.jsp?id=9923

    Are there any plans to support older devices like Forerunner 620 / 220 with this possibility to connect the BSX sensor or the Stryd Power sensor?
  • Might be better to post in the forums for those devices and not under connect IQ
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries