What are you trying to record or read?
I've tested with dev field 93, and scaling on dev-fields is problematic. The Garmin sdk provides a native field: cadance256, which behaves well and has a two digit precission out of the box. Garmin Connect seems to ignore it for rowing, but FitFileViewer shows it behaves well. Might be used for other sports normally.
See also sanderroosendaal/rowingdata#66 as started by @CrewNerd
Proposed field
Precision actually measured
No response
Who can produce and consume it today?
All monitors
Could this invalidate existing conforming files?
No — purely additive, a new optional field
Your affiliation
OpenRowingMonitor
What are you trying to record or read?
I've tested with dev field 93, and scaling on dev-fields is problematic. The Garmin sdk provides a native field: cadance256, which behaves well and has a two digit precission out of the box. Garmin Connect seems to ignore it for rowing, but FitFileViewer shows it behaves well. Might be used for other sports normally.
See also sanderroosendaal/rowingdata#66 as started by @CrewNerd
Proposed field
Precision actually measured
No response
Who can produce and consume it today?
All monitors
Could this invalidate existing conforming files?
No — purely additive, a new optional field
Your affiliation
OpenRowingMonitor