Welcome Guest,Register Now
Log In

ANT Forum

Welcome guest, please Login or Register

   

Notes on Profile.xlsx and SDK

RankRank

Total Posts: 44

Joined 2013-04-07

PM

Hi,

> please check in Profile.xls Rev. 14.10:

- table “Messages” row 178 and 179 low_alert_elevation and high_alert_elevation
- table “Types” row 293 elevation

For me it looks as if these rows had lost their way.


> The Profile.xls Rev. 14.10 has a memory requirement of 2.662 KB.

Please check:
- open Profile.xls with Excel
- goto Developertools (VBA): Alt + F11
- open Projekt-Explorer: Strg + r
- now you can see Profile.xls has 6 sheets !?
- sheet 1,3,4 and 5 are “very hidden”
- press F4 to change the property “Visible” from “xlSheetVeryHidden” to “xlSheetVisible”
- now you can see the sheets, they are empty (I think you don’t need the sheets ?)
- delete the sheets and save the file

The Profile.xls Rev. 14.10 has now a memory requirement of 585 KB.


Thanks,
edge-python
     
RankRankRank

Total Posts: 91

Joined 2012-10-12

PM

-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.      
RankRank

Total Posts: 44

Joined 2013-04-07

PM

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      
RankRankRank

Total Posts: 91

Joined 2012-10-12

PM

-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.      
RankRank

Total Posts: 44

Joined 2013-04-07

PM

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':
WeightScaleSingleUser.fit             type 14 blood_pressure
WorkoutCustomTargetValues
.fit         type 14 blood_pressure
WorkoutIndividualSteps
.fit            type 14 blood_pressure
WorkoutRepeatGreaterThanStep
.fit      type 14 blood_pressure
WorkoutRepeatSteps
.fit                type 14 blood_pressure 

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

Total Posts: 91

Joined 2012-10-12

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      
RankRank

Total Posts: 44

Joined 2013-04-07

PM

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):
file_id.type:
14 blood pressure -> 9 weight
14 blood_pressure 
-> 5 workout

crc 

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)      

File Attachments

RankRank

Total Posts: 44

Joined 2013-04-07

PM

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
     
RankRank

Total Posts: 44

Joined 2013-04-07

PM

edge-python - 15 June 2016 10:57 AM
The following notes apply to the Rev. Fit SDK 20.03 and 20.06

FIT SDK Rev. 20.08

FIT Protocol Rev. 2.2
Table 4-6. "FIT Base Types and Invalid Values" contains description for
fit_base_type:
- 14: sint64
- 15: uint64
- 16: uint64z

Thank you

(Table number renamed from 4-9 to 4-6 )      
RankRank

Total Posts: 44

Joined 2013-04-07

PM

Could some commas be missing?

Thank you      

File Attachments

RankRank

Total Posts: 44

Joined 2013-04-07

PM

edge-python - 25 March 2017 04:40 AM
Could some commas be missing?

commas missing, no changes in 20.30.00

Thank you      

File Attachments

RankRank

Total Posts: 44

Joined 2013-04-07

PM

edge-python - 25 March 2017 04:40 AM
Could some commas be missing?

the commas are back in 20.33.01

Thank you      

File Attachments

RankRank

Total Posts: 44

Joined 2013-04-07

PM

From SDK 3.10 to SDK 20.18.00, the field swim_stroke (message session) used the field sport as a reference field.
Since SDK 20.21.00 this is canceled?

Thank you      

File Attachments

RankRank

Total Posts: 44

Joined 2013-04-07

PM

It is probably unintentional?
Only those who have downloaded and saved FitSDKRelease_21.00.00beta.zip can read FIT Rev. 2.4

and another point:
in "FIT SDK Release Notes" (https://www.thisisant.com/developer/fit-sdk-release-notes) some text lines are shifted downwards,
it would be good to restore that


Thank you      

File Attachments

RankRankRankRank

Total Posts: 125

Joined 2012-06-27

PM

Re swim_stroke: This was just an unnecessary typo.

The 2.4 revision document will be included in 21.xx releases moving forwards. Thanks for catching this.

Can you clarify what you mean by "shifted downwards"?      

Signature

Ian Haigh

RankRank

Total Posts: 44

Joined 2013-04-07

PM

haighi - 19 August 2019 10:01 AM

Can you clarify what you mean by "shifted downwards"?

Yes sure,
please look in the attached
I do not think that's the right order

Thank you      

File Attachments