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

[Vincent25]

Hi,

I don't understand why the characteristic FitnessMachine Feature : (0x2ACC) is not decoded as a bit field by nRF Connect

I can read it and i can see the good value shown as binary.

it's written (in nRFConnect) :    Value= Invalid value : (0x) 00-00-00-00

and if i try an other value its the same.

remarque : in the same service , nRF Connect decode correctly the Indoor Bike Data as a bit field.

thank you

Vincent

[Sigurd]

Hi,

Vincent25 said:

I don't understand why the characteristic FitnessMachine Feature : (0x2ACC) is not decoded as a bit field by nRF Connect

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

[Vincent25]

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

[Vincent25]

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