Why do we need to encode data in Heart Rate Measurement profile?

RE: Why do we need to encode data in Heart Rate Measurement profile?

ndarkness — Thu, 16 Nov 2017 07:45:03 GMT

@max Thanks!

RE: Why do we need to encode data in Heart Rate Measurement profile?

ndarkness — Thu, 16 Nov 2017 07:44:41 GMT

@endnode thanks, I thought it's was related to all profiles. If you ask why is it so then I'm afraid you need to call to BT SIG and challenge them;) hahah it sounds challenging ;)

RE: Why do we need to encode data in Heart Rate Measurement profile?

max — Wed, 15 Nov 2017 15:51:52 GMT

If you use a standart HRS you need to encode your data acording to spec

for your own characteristic you can use Developer Studio & plugins

RE: Why do we need to encode data in Heart Rate Measurement profile?

endnode — Wed, 15 Nov 2017 15:49:15 GMT

Heart Rate Monitor has standard HTP Profile and HTS Service defined by BT SIG, you can download the spec free of charge. As such they define not only GAP and GATT roles and GATT Service/Characteristic count/UUIDs/privileges etc. but also protocol on top of Characteristics' Values. So if you want to use it and be interoperable you need to encode information according to the specification. If you ask why is it so then I'm afraid you need to call to BT SIG and challenge them;)

If you do your proprietary GAP Profile and GATT Service specification/app then you azre free to define your protocol on top of GATT. If you then use some SDK example as "template" then indeed you need to change such encoding functions unless you keep the protocol exactly as defined for HRS by BT SIG.