Cannot detect the primary service using pc-ble-driver with 128 bit UUID

[dayizhang]

Hi.

I programmed the firmware in "https://github.com/NordicSemiconductor/pc-ble-driver" share folder to a nrf52840 dongle. 

NRF_SD_BLE_API=6

I took the example heart rate code and modify to talk to a nrf52840 eval boards running NUS.

I changed the last parameter in sd_ble_gattc_primary_services_discover to NULL.

err_code = sd_ble_gattc_primary_services_discover(m_adapter, m_connection_handle, start_handle, NULL);

I would expect I should see 2 BLE services + a NUS service (128 bit UUID).  But I can only get 2 detected services in on_service_discovery_response(). (p_ble_gattc_evt->params.prim_srvc_disc_rsp.count = 2).

I tried another another board running 2 BLE services + a 16 bit UUID service. The system returned 3 services.

Thus, I think the problem is related to the UUID length.

Could you help me find out the issue?

Thanks.

[tesc]

Hi,

Have you solved the issue, or can you still not correctly find NUS on the device?

When handling 128 bit UUIDs (vendor specific UUIDs) you may have to register the UUID using sd_ble_uuid_vs_add(), for use in parts of the API that use the ble_uuid_t structure for UUIDs.

Regards,
Terje

[dayizhang]

I still cant find NUS. I registered UUID using sd_ble_uuid_vs_add(), but still not working.

At the moment I manually write handler ID to start the notification. But I dont think its a proper way for doing this.

[tesc]

Hi,

There is an example of using pc-ble-driver for a NUS client in this thread: Can't find 128-bit UUID and service name. It seems to do exactly what you are looking for.

Regards,
Terje

[dayizhang]

Hi, I saw this thread. I can even get the unknown service. The maximum handler returned on my side is 0x0A, whereas the expected maximum is 0x11+. So the NUS characteristic seems like is ignored.  

[tesc]

Hi,

What PCA number and version of the board are you running a NUS example on, and what version of the NUS example (what SDK and version, and are you using the precompiled version or have you compiled it yourself.)

Also, have you checked that the NUS example works as expected, e.g. by connecting to it using nRF Connect?

Regards,
Terje

[dayizhang]

PCA10056 V2.0.0 SDK16.0.0 and softdevice 7.0.1

[dayizhang]

Yes.nRF connect on Android and iOS are working properly.