• State Not Answered
  • Replies 4 replies
  • Subscribers 11 subscribers
  • Views 1389 views
  • Users 0 members are here
Options
Related

Compressed timestamp header still being used?

BESSELING.FRANK

HI all,

I am developing my own parser, and have doubts if timestamp headers are still being used in modern devices. 

I see the same question asked a couple of years ago (https://forums.garmin.com/developer/fit-sdk/f/discussion/259314/compressed-timestamp-header), but none of the reactions contains the real answer.

Who knows?

Frank

  • 0

    I have been told that compressed timestamps are not used in FIT Activity files created by Garmin wearables and bike computers. There might be an older device that does; I am not 100% sure though as that would have been a while ago.  I doubt any other manufacturers that use the FIT SDK use compressed timestamps. There are a few popular open-sources SDKs that have not implemented support for compressed timestamps, so support for compressed timestamps is probably something that can put that in the backlog until there is a solid need for it.

  • 0

    Hey guys, I have encountered an issue with parsing two fit files with a compressed timestamp header with garmin-fit-sdk:

    "Compressed timestamp messages are not currently supported".

    The fit files originated from a Garmin Vivofit 4 which is a very old device (2017 if I'm not mistaken). Are there any plans to implement support for compressed timestamps? 

     

  • 0 in reply to 1227650

    The error message is a red-herring. There is a corrupt byte, or missing byte, that is the actual cause. The previous message was read, and the decoder is looking at the header for the next message and that byte is not actually a message header. That byte has the bit set that tells the decoder that it is a compressed message header, but it is really just a random byte. 

    Try parsing the file with the FIT CSV Tool and see if the entire file parses. I am guessing that it will not decode the entire file.