Acknowledged
10 months ago

No values on Activity.WorkoutStep.targetValueHigh and Low under certain conditions

The SDK (v7.x.x) delivers no values (0, zero) for workout targetValueHigh and targetValueLow:
-if you chose HR target as %maxHR
-if you chose Power target as %FTP
-if you chose WorkoutStepTargetType 18 - Power Curve

And another question: is it a bug or „by design“, that:
-HR targets are delivered with 100 points too high (targetValueHigh - ot Low deliver 230 for 130 bpm)
-Power targets are delivered with 1000 points too high (targetValueHigh - or Low deliver 1200 for 200 watts)

mcinner1
Parents
  • 5 months ago

    Hello

    Sorry for the delay in getting this looked at. I tried to reproduce this issue but with no luck.
    I created this workout


    And loading that into our workout sample test app, I did seem to get the correct values for targetValueHigh and targetValueLow

    When comparing it to a .csv of the same workout:




    This was all done with SDK version 7.4.0

    Do you have an example .fit file I could use to test to try and reproduce this issue?
    Also not seeing any HR or Power targets with 100 or 1000 points too high respectively 

Comment
  • 5 months ago

    Hello

    Sorry for the delay in getting this looked at. I tried to reproduce this issue but with no luck.
    I created this workout


    And loading that into our workout sample test app, I did seem to get the correct values for targetValueHigh and targetValueLow

    When comparing it to a .csv of the same workout:




    This was all done with SDK version 7.4.0

    Do you have an example .fit file I could use to test to try and reproduce this issue?
    Also not seeing any HR or Power targets with 100 or 1000 points too high respectively 

Children
No Data