RE: Central scanning for 128 bit uuid service

Andrew Livick — Thu, 25 Sep 2014 21:08:23 GMT

I am having a similar issue, as I am pretty much doing exactly what you have said by altering the S120 ble_app_hrs_c example app. When I find that the 128 bit UUID is a match for the advertised one I do the following: sd_ble_gap_connect(&p_gap_evt->params.adv_report.
peer_addr, &m_scan_param, &m_connection_param); But it seems to still be using the 16 bit UUID for the heart rate service. I am not sure how to change this as I don't want to be altering the code that is in the SDK, but rather the code in this project.

RE: Central scanning for 128 bit uuid service

Ole Morten — Thu, 27 Mar 2014 16:37:03 GMT

There is currently no example of doing this, but it shouldn't be very tricky to do on your own. Summarized, you'd have to do this:

Start scanning, making sure to use active scanning if the target device has the UUID in the scan response.
Receive a BLE_GAP_EVT_ADV_REPORT, containing the advertising data.
Look through the advertising data for the field BLE_GAP_AD_TYPE_128BIT_SERVICE_UUID_MORE_AVAILABLE or BLE_GAP_AD_TYPE_128BIT_SERVICE_UUID_COMPLETE.
Look at the data of this field, and compare it with whichever value you were looking for.
If the comparison succeeds, do a connect with this device.