read characteristic from peripheral

[PeteKcSum]

I have modified a multi-central 52840 example, and would like to  connect and read the characteristic value from various peripherals.

I looked through posts like the below ones, that describe using the sd_ble_gattc_char_value_by_uuid_read to get the CHAR value.

https://devzone.nordicsemi.com/f/nordic-q-a/7454/read-the-characteristic-value

https://devzone.nordicsemi.com/f/nordic-q-a/52251/read-added-custom-characteristic-value-from-peripheral/210706#210706

But i am still very unclear and confused how it is done. What needs to be done to trigger the event BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP so that the event handler is called ? After that , how are the char values stored ?

I have managed to modify the LBS service for my custom UUID base , service and characteristics, and it seems i have successfully acquired the handles for the corresponding characteristics. Please advise how to proceed with these known handles to acquire the CHAR values from the peripheral, much thanks.

[Simon]

But i am still very unclear and confused how it is done. What needs to be done to trigger the event BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP so that the event handler is called ?

 After calling  sd_ble_gattc_char_value_by_uuid_read(), the event will be received by the BLE event handler ble_evt_handler(). You should modify the switch-case statement to handle the BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP event. Check out the message sequence chart for GATTC Read Characteristic Value by UUID for more information.

After that , how are the char values stored ?

 You can access the values as explained by Edvin in this thread, If you are wondering if the characteristics are stored in flash, that is not the case (unless you are using the Peer Manager).

Best regards,

Simon

[PeteKcSum]

thx, solved it.