This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

What does ble_gatts_char_md_t.char_props.read do?

It suggests that it holds the permission regarding whether a chara. can be read, but isn't that kinda redundant since there are tons of other similar properties out there detailing the same thing?

Also I noticed that, when communication with the MCU using my android app, if I enable it, no matter I set CCCD handle or not, it won't trigger the

sd_ble_evt_handler(), and once I turn it off, the sd_ble_evt_handler() can correctly be triggered.

And by not triggering I mean nothing at all, this is what being triggered look like: I press a button on my app, it enters the handler, if I enable char_props.read, nothing happens, the ble evet handler appears not to be called at all.

Why is that?

Parents
  • Hi Mitch,

    ble_gatts_char_md_t.char_props holds the properties, not the permission. The permission you set with attr_md.read_perm not the char_props.

    but isn't that kinda redundant since there are tons of other similar properties out there detailing the same thing? => Could you tell which?

    What do you do when you press the button on your app ? Would it write something to the GATT server on the device ? Which event did you get in the event handler ?

    Adding read property should not cause problem with the write event.

Reply
  • Hi Mitch,

    ble_gatts_char_md_t.char_props holds the properties, not the permission. The permission you set with attr_md.read_perm not the char_props.

    but isn't that kinda redundant since there are tons of other similar properties out there detailing the same thing? => Could you tell which?

    What do you do when you press the button on your app ? Would it write something to the GATT server on the device ? Which event did you get in the event handler ?

    Adding read property should not cause problem with the write event.

Children
No Data
Related