Enabling Notify on 2 Characteristics

RE: Enabling Notify on 2 Characteristics

MartinBL — Wed, 25 Apr 2018 07:56:23 GMT

If you really need to do this I suppose adding a ble_evt variable to your service event handler function header could be the easiest route. Note however, that some functions that call the event handler don't have any ble_evt variable to pass into the event handler (like ble_nus_c_on_db_disc_evt()). A simple if(ble_evt == NULL) check might fix this though.

RE: Enabling Notify on 2 Characteristics

nick7 — Tue, 24 Apr 2018 12:35:13 GMT

Thanks for the reply Martin.

Ok, I will have a look at this. So far, I've solved my issue by simply writing to the cccd handle without response. But that is probably not an optimal solution.

I could have worded my question above a bit more generally:

How can I access softdevice events (e.g BLE_GATTC_EVT_WRITE_RSP) inside an application event handler (ble_cus_c_evt_handler)?

Because if I want to wait for a BLE_GATTC_EVT_WRITE_RSP event, as described in the infocenter , I would like to access this softdevice event from the same function as I enable notifications.

Best,

Nick

RE: Enabling Notify on 2 Characteristics

MartinBL — Tue, 24 Apr 2018 12:09:44 GMT

Hi,

I'm not sure if I quite understand your question. But if you take a look at the ble_app_rscs_c example, you can see how to implement a queue of read and write operations. Take a look at the functions cccd_configure() and tx_buffer_process() in ble_rscs_c.c. I suppose you can expand upon these functions and queue up your writes to the CCCD handles.