Welcome Guest,Register Now
Log In

ANT Forum

Welcome guest, please Login or Register

   

Profiles, woukout scheduling and other SDK omissions

RankRankRankRank

Total Posts: 523

Joined 2012-11-15

PM

Hello,
I'm trying to integrate FIT support to my application. Basically I need to support everything "Fitness" related, namely workouts & profiles. I have the workouts which are well documented so everything went fine there.
However, there are some things lacking in the SDK. I cannot, for instance, schedule workouts. I see absolutely no reference to workout scheduling in the SDK. When reading a workout, I can see a field wih id 7 (UInt16) that is undocumented, could this be it?
Also, the user profiles and bike profiles are completely undocumented apart from message id in the source code. I have no idea where I should put speed/HR and power zones. Should they go in a settings file or in a sport file? What field are required?
Maybe I'm missing something?

Thanks      
RankRankRankRank

Total Posts: 116

Joined 2008-11-21

PM

support and documentation for scheduling, bike/SDM profiles and sports settings file (for defining your zones) will be included in the next release of the SDK (early next month)      
RankRankRankRank

Total Posts: 523

Joined 2012-11-15

PM

Great, thanks!      
RankRankRankRank

Total Posts: 523

Joined 2012-11-15

PM

I got a sport & settings file from a user and I can figure out pretty much everything I need except the bike profiles. Here is what I parsed in the file. Care to give me a bit of insight to help me move on before the official release of the SDK??? I included the values I found in the only bike profile setup with some suppositions on what the data represents.

Thanks!

Fields:
00 = name
03 = 0x2DCEC900 = 768526592 = ANT device ID???
04 = 2 bytes = 0x0000 = uint16z (invalid)
05 = 2 bytes = 0x0000 = uint16z (invalid)
06 = 2 bytes = 0xFE3A = 65082 = odometer meters?
07 = 2 bytes = 0x4702 = 18178 = weight lbs?
08 = 2 bytes = 0x0830 = 2096 = wheel circumference default?
09 = 2 bytes = 0x0834 = 2100 = wheel circumference?
10 = 2 bytes = 0x005F = 95 = min power?
11 = 2 bytes = 0x01F4 = 500 = max power?
12 = 1 byte = 0x00 = cadence/power sensor?/auto wheel size?
13 = 1 byte = 0x01 = cadence/power sensor?/auto wheel size?
14 = 1 byte = 0x00 = cadence/power sensor?/auto wheel size?
15 = 1 byte = 0x00 = ??? uint8
16 = 1 byte = 0x00 = cadence/power sensor?/auto wheel size?
17 = 1 byte = 0x01 = cadence/power sensor?/auto wheel size?
18 = 1 byte = 0x01 = cadence/power sensor?/auto wheel size?
254 = index      
RankRankRankRank

Total Posts: 116

Joined 2008-11-21

PM

Details of bike profiles will be covered in the next release.
Trying to guess field contents will lead to errors in your development. Please wait for the SDK release.      
RankRankRankRank

Total Posts: 523

Joined 2012-11-15

PM

Is there a public roadmap for the next release? When exactly is "early" november?      
RankRankRankRank

Total Posts: 116

Joined 2008-11-21

PM

There is no public roadmap. we are working towards getting out an update as soon as possible.      
RankRankRankRank

Total Posts: 523

Joined 2012-11-15

PM

Yes, I had other features I could add in the mean time but now it's pretty close to completion apart from user, activity & bike profiles so I might drop an e-mail soon enough.

Thanks