Can not get characteristic UUID

RE: Can not get characteristic UUID

run_ar — Mon, 18 Dec 2017 12:16:44 GMT

Ok, I have not seen your code. But from what I can see from the picture above you are only adding one vendorspecific UUID. While the picture from nRF_connect shows that you have 6 different UUID's in the peripheral. One for the custom service, and 5 for the custom characteristics. I didn't notice that since the first bytes is identical (so these UUID's is not correctly generated).

RE: Can not get characteristic UUID

forrestDun — Tue, 24 Oct 2017 01:31:43 GMT

Hi run_ar, As I said in my question.I followed the example of ble_central\ble_app_hrs_c to discover the UUID of each characteristics.As illustrate in my question image, it can't get the UUID of characteristics,when the program ran to this function--void ble_bas_on_db_disc_evt(ble_bas_c_t * p_ble_bas_c, const ble_db_discovery_evt_t * p_evt).

RE: Can not get characteristic UUID

run_ar — Mon, 23 Oct 2017 07:35:22 GMT

Are you sure you are trying to discover the correct UUIDs? It's possible to use sd_ble_gattc_attr_info_discover to get a BLE_GATTC_EVT_ATTR_INFO_DISC_RSP. Unfortunately this is not part of the discovery module. But that is the function used by nRF connect to discover unknown UUIDs.

RE: Can not get characteristic UUID

forrestDun — Fri, 06 Oct 2017 07:48:36 GMT

Hi run_ar, I have done the experiment as your indication. The result is same with description of my previous question. ble_uuid128_t tx_base_uuid = {{0x18, 0x03, 0xa6, 0x28, 0x5e, 0xd8, 0xec, 0x91, 0x1c, 0x48, 0xA3, 0xac, 0x00, 0x00, 0x53, 0x49}}; err_code = sd_ble_uuid_vs_add(&tx_base_uuid, &ble_uuid.type); VERIFY_SUCCESS(err_code);

ble_uuid.uuid = 0x5343;

RE: Can not get characteristic UUID

run_ar — Mon, 02 Oct 2017 08:10:09 GMT

I'm sorry this slipped through the cracks, did you solve it? Since it looks like your peripheral only have vendor specific UUID's it might be better if you use our nus client example. Start by just replacing the nus UUID's and check if you can discover a couple of characteristics, then add the rest. If you need both HR and custom, add the nus client to your project and leave the hrs client as is.

RE: Can not get characteristic UUID

forrestDun — Mon, 28 Aug 2017 00:32:16 GMT

Hi run_ar, I have update my question, please read it again. Thank you.

RE: Can not get characteristic UUID

run_ar — Fri, 25 Aug 2017 09:09:06 GMT

Not easy to know exactly what you are doing. Did you modify the example in any way? Note that the Heart rate client only discovers uuid's that are registered with the discovery module. Check for ble_db_discovery_evt_register in your code.