ANT Forum

Hi Mitac,

I had a look at your files and it looks like you have found a bug in the java encoder. For some reason it is having trouble building a correct definition message for the device_info messages which contain unknown fields eventhough the CSV tool can decode these messages correctly. I will log the issue so it gets investigated.

Regards
ShaneP

     

Hi ShaneP,

Thank you for assistance. Please let me know when you get more information.


     

Hi ShaneP,

are there any updates ? Is there any way to track progress on the issue ?
Thanks.      

Hi Mitac,

I've just checked the system and this appears to still be an open issue. I will try to find out more information for you. Is this a priority issue for you?

In the meantime this is the best place to check for updates, or as a member you are welcome to email us directly (PM me if you don't have the email address).

Thanks,

Kat      

Hi Kat,

This is very important for me. Please notify me when the issue is resolved or you have any updates.
Thanks.      

Hi Mitac,

OK, thanks for letting me know. I'll have more information for you early next week.

Kat      

Have sent you a private message with an update. The fix is planned for August.      

Hello Kat,

Is the fix available and if so what is the FIT SDK version #? Thanks!      

I downloaded FIT SDK 8.0 and I do not see this fix in the release notes. Can you confirm whether or not this issue is resolved in 8.0? Thanks!

FIT SDK External Release Notes

8.00
-Add check that mesg_index is valid in Fit_GetFileMesgOffset()
-Profile Changes


7.10
-Profile Changes

7.01
-Fixed truncation issue with some scaled fields in Java/C++
-Removed record.cadence reference to cadence256

7.00
-Added missing monitoring fields described in File Types Doc
-Other profile changes
-Accumulated fields improvements (Java):
Multiple compression fields can now accumulate into the same destination field
Explicitly logging the accumulated field updates the accumulated value
-Fixed FitGen crash if custom types/mesgs files are locked
-Add FIT ProtocolVersion compatability check to C# decoder

6.20
-Profile Changes
-Fixed discrepancy between binary and ascii in example activity file


6.10
-Profile Changes
-Fix Encoding of ProtocolVersion under C#
-Rearranged Java mesg templates to avoid 64k static size boundary
-Fixed issue where software and slave_device messages were incorrectly merged


6.00
-Documentation Update
-Profile Changes      

This is still planned for 8.10, however we won't be able to release it Aug30th as planned. This release will slip to ~Sept6.      

-I just added FIT SDK version 8.10 to the downloads page. This fixes an issue where the type of unknown fields was not being preserved by the Java decoder. This should resolve the issue you were having above.