Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

all: support for FIT protocol 2.x #20

Open
beyoung opened this issue Sep 22, 2016 · 5 comments
Open

all: support for FIT protocol 2.x #20

beyoung opened this issue Sep 22, 2016 · 5 comments
Milestone
Unplanned

Comments

@beyoung
Copy link

beyoung commented Sep 22, 2016 

error decoding header: not supported: protocol version 2.x not supported by sdk protocol version 1.0

Would be great thx if fit supports version 2.x. _.
@tormoder
Copy link
Owner

Yes, this is on my todo-list.

@djk121
Copy link

djk121 commented Jan 18, 2017

Got a sense of what it'd take? I might have a go at it, but I'm not familiar with the differences between 1 and 2.

@tormoder
Copy link
Owner

Thanks for your interest.

Yes, I think so.

I believe it is mainly support for some new base types + developer data support.
I plan to support 2.0 without support for developer data first, and implement that later.

I've actually done most of it, and have a bunch of commits I plan to push soon.

@tormoder tormoder mentioned this issue Jan 18, 2017
Open
@djk121
Copy link

djk121 commented Jan 20, 2017

OK, I'll sit tight for a few days. Thanks!

tormoder added a commit that referenced this issue Apr 2, 2017
@tormoder
internal/types: add sint64,uint64,uint64z base types
c223975 
Introduced in FIT 2.0.

For #20.
tormoder added a commit that referenced this issue Apr 2, 2017
@tormoder
internal/types: add entry to BaseTypeFromString map due to typo in SDK
f567cda 
For #20.
tormoder added a commit that referenced this issue Apr 2, 2017
@tormoder
testdata: add DeveloperData.fit from official SDK (20.14)
7ef218b 
Preperation for implementation of developer data from Fit 2.0.
Not added to test files yet.

For #20.
tormoder added a commit that referenced this issue Apr 2, 2017
@tormoder
internal/types: add sint64,uint64,uint64z base types
03663e3 
Introduced in FIT 2.0.

For #20.
tormoder added a commit that referenced this issue Apr 2, 2017
@tormoder
internal/types: add entry to BaseTypeFromString map due to typo in SDK
c94fbc4 
For #20.
tormoder added a commit that referenced this issue Apr 2, 2017
@tormoder
header, consts: support decoding FIT protocol version 2
36947b6 
Updates #20.
tormoder added a commit that referenced this issue Apr 2, 2017
@tormoder
README.md: update
2a9e1b2 
Updates #16 and #20.
@tormoder
Copy link
Owner

tormoder commented Apr 3, 2017

It should be possible to decode protocol version 2 files as long as they don't use Developer data fields.

@tormoder tormoder added this to the fit release 0.3.0 milestone Apr 3, 2017
@tormoder tormoder changed the title Not support 2.x all: no support for FIT protocol 2.x Apr 3, 2017
@tormoder tormoder removed this from the fit release 0.3.0 milestone May 10, 2019
@tormoder tormoder changed the title all: no support for FIT protocol 2.x all: support for FIT protocol 2.x May 10, 2019
@tormoder tormoder added this to the Unplanned milestone May 10, 2019
@tormoder tormoder mentioned this issue Jan 10, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
3 participants
@djk121 @tormoder @beyoung