ANT Forum

-Good eyes! The lost fields are gone but I didn't get a chance to suppress the temporary worksheets in profile.xls. I will try to compact it for the next release.      

Hi,

Thank you for the fix in the new Rev. 14.20.
You were too fast for me or I am too slow for further comments.
I will not open a new thread, but the following notes apply to the Rev. 14.20


Rev. 14.20 - Profile.xls - Sheet "Messages"


> some rows have in column EXAMPLE the value 1

please check whether you can delete the value 1 in:

row 63 (row under device_settings)
row 64 (first row user_profile)
row 507 (row under record)
rom 668 (row under weight_scale)
rom 670 (first row blood_pressure)


> if a Field Name is "product" follows in the next row "garmin_product"

please check this in:

row 549 (device_info), in the next row "garmin_product" is missing


> most of the fields which have no SCALE, have no value in the column SCALE
but some Fields have SCALE 1 (so this is also no SCALE?!)

please check whether you can delete the value 1

(I did not make a list, you can easily filter the rows with Excel)



Thank you
edge-python      

-The unnecessary flags in the default 'EXAMPLE' configuration will be removed.
-garmin_product will be added to device_info
-Unless otherwise specified, scales are implied to be 1 and offsets 0. The profile inconsistently expressed scale=1 for many fields. This is unnecessary and will be removed.      

The following notes apply to the Rev. 14.20

The FIT SDK contains examples.
Please check the content of the fields 'type' in the messages 'file_id':

Thank you.
edge-python
(sorry, english is not my native language)      

-The file_id.type is incorrect in these examples.
I want to improve these but I won't be able to get to that for a while.

ShaneP      

ShaneP - 21 April 2015 12:07 PM

-The file_id.type is incorrect in these examples.
I want to improve these but I won't be able to get to that for a while.
ShaneP

The following notes apply to the Rev. 14.20

I have modified in the files (see attachment):

Maybe you can use the files for a new Rev. FIT SDK (if you want)

Thank you.
edge-python
(sorry, english is not my native language)      

The following notes apply to the Rev. Fit SDK 20.03 and 20.06

Please do not forget:
Table 4-9. FIT Base Types and Invalid Values
and:
fit_base_type:
- 14: sint64
- 15: uint64
- 16: uint64z


Thank you

Update: 15.07.2016