S120 central discover service fail

RE: S120 central discover service fail

Petter Myhre — Fri, 27 Nov 2015 14:26:37 GMT

You can check the event in on_ble_evt(). Then you can print out:

p_ble_evt->evt.gattc_evt.params.prim_srvc_disc_rsp.services[0].uuid.uuid - This should match the short UUID of service

and

p_ble_evt->evt.gattc_evt.params.prim_srvc_disc_rsp.services[0].uuid.type -This should match the type of the base UUID returned from sd_ble_uuid_vs_add(&base_uuid, &m_base_uuid_type);

You will get the BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP event as an response to calling sd_ble_gattc_primary_services_discover(), the example should already be calling this.

RE: S120 central discover service fail

sowmya — Fri, 27 Nov 2015 13:39:18 GMT

Ok thank you. I am checking this event in on_ble_evt() function. Is this correct? And there is no discovered uuid field? Where exactly I have to use the event?

RE: S120 central discover service fail

Petter Myhre — Fri, 27 Nov 2015 13:34:16 GMT

Right. You can try to sniff the connection to find out what is happening, or you could handle the BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP event, and check what UUIDs that is discovered by for example printing them out.

RE: S120 central discover service fail

sowmya — Fri, 27 Nov 2015 13:18:46 GMT

I have modified ble_app_multilink_central example and commented scan_start() in device_manager_event_handler, so there should not be any problem even if light blue peripheral is advertising right?

RE: S120 central discover service fail

Petter Myhre — Fri, 27 Nov 2015 13:15:10 GMT

Are you modigying the ble_app_multilink_central example? If you are, there could be a problem with lightblue peripheral, because even though you connect to it, it will continue to advertise. And the ble_app_multilink_central example will continue to scan. See scan_start() in device_manager_event_handler(). I'm not sure if that is causing the problem though. Are you able to sniff the connection with nRF Sniffer?

RE: S120 central discover service fail

sowmya — Fri, 27 Nov 2015 13:03:11 GMT

Yes it is the same.

RE: S120 central discover service fail

Petter Myhre — Fri, 27 Nov 2015 13:01:58 GMT

Yes, but BLE_DB_DISCOVERY_SRV_NOT_FOUND means that it can't find the service, i.e. the UUID of the service that you are searching for. So does the service UUID that is discovered by Master Control Panel match the UUID you are asking the central device to search for?

RE: S120 central discover service fail

sowmya — Fri, 27 Nov 2015 12:53:50 GMT

Yes. With Master control Panel it is working. But in nRF51822 central device, it is not.

RE: S120 central discover service fail

Petter Myhre — Fri, 27 Nov 2015 12:46:02 GMT

The UUID that appears in Master Control Panel, is it equal to the UUID used in central?

RE: S120 central discover service fail

sowmya — Fri, 27 Nov 2015 12:37:36 GMT

Yes it is working with nRF51822 board but not with iOS.

RE: S120 central discover service fail

Petter Myhre — Fri, 27 Nov 2015 11:52:08 GMT

I'm not following. Is it working now with Nordic as central and peripheral? But not with iOS?

RE: S120 central discover service fail

sowmya — Fri, 27 Nov 2015 11:22:52 GMT

Hello Petter, yes that was the I had done. Now it is able to connect to the peripheral and I am testing the same central application with light blue app on iPad and again I am getting BLE_DB_DISCOVERY_SRV_NOT_FOUND event. Can I know how to set notify or nus service in light blue? The same application on iPad is able to connect and send notification with master control panel.

RE: S120 central discover service fail

Petter Myhre — Fri, 27 Nov 2015 10:15:10 GMT

In the central you have BLE_UUID_DEVICE_INFORMATION_SERVICE while in peripheral you have BLE_UUID_NUS_SERVICE. Are these equal? Also, are you aware of this example?