var powerField = createField("Power", fieldId, FitContributor.DATA_TYPE_UINT16,
{:mesgType => Fit.MESG_TYPE_RECORD, :units => "W", :nativeNum => 7});
FlowState,
I am using following options when I call createSession {..., :sport=>ActivityRecording.SPORT_TRAINING,
:subSport=>ActivityRecording.SUB_SPORT_STRENGTH_TRAINING}
I presume that in this case the laps are actually sets and that I should look at
set fields - Subsection: set for nativeNums
even though the createField call uses :mesgType=>FC.MESG_TYPE_LAP
I am thinking of the duration field (=0) and the weight field (=4)
Does that sound right to you?
Some third party sites:
Interpret some nativeNum developer fields as "native", which is what developers would prefer (obviously).
It’s a great news, but whether there is any direct tool or an indirect solution (import and export) which can finally place the developer’s power field into the native power field?
So from one with NativeNum to ID=7?
So far I found no solution and therefore cannot make any ex-post calculations with running power in the sw I use, which is the rusty Sporttracks 3.0 (PC version).
I wondered whether all these calculations should be done within a ciq datafield, but a “peak power over 60 minutes” et al being calculated realtime would kill any Garmin watch. :-)
So I am looking for a solution - even if it is a sort of manual one, but a fast one - to squeeze Styrd power into native power.