Identify characteristic when processing BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP event

[Florin]

Hi,

I'm using S130 with SDK 9.0.0 and as central, I'd like to read values for more than one characteristic on a peripheral. I do so in BLE_GATTC_EVT_CHAR_DISC_RSP by firing multiple sd_ble_gattc_char_value_by_uuid_read calls, one for each p_ble_evt->evt.gattc_evt.params.char_disc_rsp.chars[x].uuid.uuid that matches a list of characteristic UUID I'm interested in. I am then processing the BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP event to get to the characteristic values using the p_ble_evt->evt.gattc_evt.params.char_val_by_uuid_read_rsp call. The issue I'm facing is that I don't know which characteristic each value belongs to. Inspecting the event structure at runtime when the BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP event is in, didn't enlighten me either. Please help.

florin

[Petter Myhre]

Can I ask why you are using sd_ble_gattc_char_value_by_uuid_read()? sd_ble_gattc_read() is what you normally use after you have done service discovery, since then you know what attribute handle to use.

[Florin]

Actually it works using sd_ble_gattc_read. My solution is to save p_ble_evt->evt.gattc_evt.params.char_disc_rsp.chars[i].handle_value for each matching characteristic UUID then in BLE_GATTC_EVT_READ_RSP match them against p_ble_evt->evt.gattc_evt.params.read_rsp.handle. Is this the correct approach?

[Petter Myhre]

You approach is correct.