nRFConnect (android) don't decode the characteristic FitnessMachine Feature : (2ACC)

RE: nRFConnect (android) don't decode the characteristic FitnessMachine Feature : (2ACC)

Vincent25 — Sat, 11 Jan 2020 18:10:59 GMT

Hi Sigurd,

I found the mistake!

In fact it's not a 4 bytes long but 8 bytes long!!!!

it's not a 32 bits /4octets but a 64bits/8octets.

they should probably change de array p19/78 in the specification !!!

the firts colum "fitness machine features" (be carreful with the "s") it's not the caracteristic but one part of it . Only!!!

and the second part is in the second colum.

So 4+4 =8 bytes!!!

now it's well decoded by nRFConnect

Thank you!!!

Vincent

RE: nRFConnect (android) don't decode the characteristic FitnessMachine Feature : (2ACC)

Vincent25 — Fri, 10 Jan 2020 20:19:40 GMT

Hi Sigurd,

Thank you for your reply.

I agree with you Fitness Machine Feature (2ACC) is a field 4 bytes lenght.

but this 4 bytes should be decoded as bit field. It's written in the specification. The first 2 bytes are Fitness machine features (describe which features are included in the machine) and the 2 other bytes describes the target setting features (which parameters could be targetted by the client).

So in my mind nRFconnect could show this differents fileds

Vincent

RE: nRFConnect (android) don't decode the characteristic FitnessMachine Feature : (2ACC)

Sigurd — Fri, 10 Jan 2020 14:23:24 GMT

Hi,

[quote userid="86455" url="~/f/nordic-q-a/56389/nrfconnect-android-don-t-decode-the-characteristic-fitnessmachine-feature-2acc"]I don't understand why the characteristic FitnessMachine Feature : (0x2ACC) is not decoded as a bit field by nRF Connect[/quote]

Looking at the Fitness Machine Service Specification, the Fitness Machine Feature is 32bit /4 octets. It should therefore not be decoded as a bit field.

/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/4265.Fitness-Machine-Feature.PNG